Build faster with Source Parts CLI
Install, authenticate, and automate your entire sourcing workflow with our component-focused command line toolkit.
Install the CLI for your environment
Use one command to install on macOS, Linux, or Windows and authenticate with Source Parts.
$ curl -fsSL https://source.parts/cli/install.sh | shcopyNeed a different platform? Visit the GitHub repository for container images and build instructions.
Authenticate in minutes
Enforce the same security standards used across the Source Parts platform.
$ parts auth logincopyGenerate scoped API keys
Issue keys per environment with role-based permissions and automatic expiration.
Assign least-privileged scopes
Map CLI profiles to Source Parts roles to control read, write, and approval access.
Automate key rotation
Rotate credentials on a schedule using built-in renewal commands and policy reminders.
Don't have an API key? Create one in your dashboard
Command reference
Explore the core command families that power sourcing, quoting, and fulfillment workflows.
Search & intelligence
Query millions of components, analyze lifecycle risk, and export pricing snapshots.
components search
Search the Source Parts catalog with filters for stock, manufacturer, compliance, and lifecycle status.
$ parts components search --query "stm32f4" --in-stockcopyinventory availability
Return regional inventory, lead times, and allocation windows in real time.
$ parts inventory availability --sku 100-443-ESP32 --region uscopycomponents lifecycle
Inspect lifecycle events, alternates, and risk signals for critical components.
$ parts components lifecycle --mpn ESP32-C3copyQuotes & commerce
Automate quoting, BOM uploads, and purchase order workflows.
quotes create
Upload BOM files, apply pricing tiers, and generate shareable quotes.
$ parts quotes create --file ./bom.csv --customer-id 98213copyorders submit
Convert approved quotes to orders with payment terms and shipment preferences.
$ parts orders submit --quote Q-14233 --method net-30copyfulfillment track
Monitor fulfillment milestones, logistics updates, and delivery ETA.
$ parts fulfillment track --order SO-55821copyAutomation & integrations
Connect the CLI to CI pipelines, schedulers, and downstream systems.
automation workflows run
Execute saved workflows that bundle multiple commands with approvals and notifications.
$ parts automation workflows run nightly-replenishmentcopyintegrations sync
Synchronize Source Parts data with ERP, PLM, or data warehouses.
$ parts integrations sync --target erpcopyaudit log export
Export command history with user, timestamp, and result metadata for compliance review.
$ parts audit log export --since 7d --format csvcopyAutomation recipes
Kickstart your workflows with ready-to-run examples you can adapt to your environment.
Sync BOM alternates
Update engineering alternates nightly and persist results to your PLM.
parts quotes bom-sync --project ${PROJECT_ID} | plmctl import --workspace hardwarecopyMonitor lifecycle risk
Schedule a job that flags lifecycle changes and sends alerts to Slack.
parts components lifecycle --mpn $1 --json | jq '.alerts[]' | slackctl send --channel sourcing-alertscopy
Gate releases in CI
Fail builds when BOM risk exceeds tolerance before merging to main.
parts automation evaluate --workflow ci-bom-check || exit 1copy
Configure once, reuse everywhere
Profiles let teams share connections while keeping secrets secure.
output.format
Control the default response format across commands (json, table, csv).
{"output": { "format": "table" }}copyprofile
Named profile used to scope credentials and default workspace settings.
{"default": "production"}copyworkspaceId
Source Parts workspace identifier used to fetch quotes, orders, and analytics.
{"workspaceId": "org-sp-enterprise"}copyFrequently asked questions
Answers for rollout, security, and day-to-day operations.
How quickly can we adopt the CLI?
Most teams install, configure profiles, and automate their first workflow within a single sprint.
Can we manage multiple environments?
Yes. Profiles isolate credentials for sandbox, staging, and production environments with a single config file.
Do CLI commands count against API rate limits?
CLI traffic honors the same rate limits as direct API usage and surfaces headers for monitoring.
Where do we get help if something fails?
Use the support portal for tickets or escalate via Slack channels included with paid plans.
