Octopart API

Name: Octopart API API
Brand: Octopart API
Availability: InStock

✓ Official Vendor SpecE CommerceInventoryapiKey7 EndpointsREST

For Agents

Search electronic parts, retrieve pricing and stock from authorised distributors, and look up datasheets and categories.

Quickstart

Get started with Octopart API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"match a manufacturer part number to distributor pricing"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Octopart API API.

Search electronic parts by manufacturer part number, keyword, or specification

Retrieve a part by ID with datasheets, distributor pricing, and stock signals

Match an MPN string against the Octopart catalogue for BOM resolution

Browse the Octopart category tree for component classification

GET STARTED

Start building with Octopart API API

Explore with Jentic

View OpenAPI Document

Octopart is the electronic component search engine used by hardware engineers and procurement teams to find parts, datasheets, distributor pricing, and stock. The v4 API exposes search and lookup over Octopart's parts catalogue, plus access to categories, sellers, and brands. The integration is typically paired with BOM tools and ERP systems to automate sourcing decisions, surface authorised distributors, and track availability across electronic component supply chains.

Use Cases

Patterns agents use Octopart API API for, with concrete tasks.

★ BOM Sourcing and Resolution

Resolve a bill of materials by matching every manufacturer part number to an Octopart record using /rest/v1/parts/match, then fetching distributor pricing and stock for each matched part. This produces a sourcing-ready BOM with authorised seller links for procurement. Hardware teams typically run this nightly so the engineering BOM and the procurement BOM stay aligned.

Call /rest/v1/parts/match with 50 MPNs and return matched part IDs with their distributor stock and price.

Component Availability Monitoring

Monitor key components for stock-outs by polling /rest/v1/parts/{id} on a schedule and alerting when stock drops below a threshold across authorised distributors. Useful for hardware operations teams managing long-lead-time parts where a sudden distributor stock-out can stall a production run. Combine with engineering BOM tagging for prioritised alerting.

Call /rest/v1/parts/{id} for a watched part and alert if the sum of distributor stock falls below 100 units.

Engineering Part Selection

Help an engineer pick a part by searching /rest/v1/parts/search with technical filters (package, voltage, temperature range) and returning the top candidates with datasheets and seller availability. The API surfaces enough metadata to shortlist parts before deeper review, reducing hours spent across distributor websites. Common in custom EDA tools and internal part-selection apps.

Call /rest/v1/parts/search for 'LM358 SOIC-8' and return the top five parts with datasheet URLs.

AI Agent Procurement Concierge

An AI agent embedded in a hardware ops chatbot can answer questions like 'is the STM32F411 in stock at any authorised distributor' by calling Octopart through Jentic. The agent finds the right operation by intent, executes the call, and replies with a natural-language summary of distributor stock. Credentials remain in the Jentic vault, and the agent never sees the raw API key.

Use Jentic to call /rest/v1/parts/match for an MPN and reply with stock and price across distributors.

Key Endpoints

7 endpoints — octopart is the electronic component search engine used by hardware engineers and procurement teams to find parts, datasheets, distributor pricing, and stock.

METHOD

PATH

DESCRIPTION

GET

/rest/v1/parts/search

Search parts by keyword or filter

GET

/rest/v1/parts/{id}

Retrieve a part with pricing and stock

POST

/rest/v1/parts/match

Match MPNs against the catalogue

GET

/rest/v1/categories

Browse the category tree

GET

/rest/v1/sellers

List authorised sellers

GET

/rest/v1/brands

Look up brand metadata

POST

/endpoint

GraphQL endpoint for advanced queries

GET

/rest/v1/parts/search

Search parts by keyword or filter

GET

/rest/v1/parts/{id}

Retrieve a part with pricing and stock

POST

/rest/v1/parts/match

Match MPNs against the catalogue

GET

/rest/v1/categories

Browse the category tree

GET

/rest/v1/sellers

List authorised sellers

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Octopart API keys are stored encrypted in the Jentic vault. Agents receive scoped access — the apikey query parameter or Authorization header is injected at execution time and never enters the agent's prompt.

Intent-based discovery

Agents search by intent (e.g. 'match a manufacturer part number to a catalogue') and Jentic returns the matching Octopart operation with its input schema, so the agent calls the right endpoint without browsing docs.

Time to first call

Direct Octopart integration: 1-2 days for auth, BOM matching logic, and pagination. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Digi-Key API

Authorised distributor API with parts, stock, and ordering

Choose Digi-Key when the agent needs to place an order or pull canonical Digi-Key stock; Octopart aggregates across many distributors for sourcing comparison.

Complementary

Stripe API

Payment processing for online businesses

Pair Stripe with Octopart when the workflow needs to collect payment for parts surfaced via Octopart search inside a custom storefront.

Complementary

Shodan API

Internet-wide host and device intelligence

Use Shodan alongside Octopart when an IoT supply-chain workflow needs both component sourcing and field-deployment visibility on devices already in production.

FAQs

Specific to using Octopart API API through Jentic.

What authentication does the Octopart API use?

An API key, accepted either in the apikey query parameter or in the Authorization header. Jentic stores the key encrypted in its vault and injects it at execution time so the raw secret never enters the agent's prompt.

Can I match a list of MPNs against Octopart in one call?

Yes. POST a list of manufacturer part numbers to /rest/v1/parts/match and Octopart returns the best matches with pricing and stock signals. This is the primary entry point for BOM resolution workflows.

What are the rate limits for the Octopart API?

Octopart's API plans set per-key request quotas — confirm your tier in the Nexar/Octopart account dashboard. Batch where possible (especially via /parts/match) and respect 429 responses with exponential backoff to stay within limits.

How do I search for a part through Jentic?

Search Jentic for 'search Octopart parts by keyword', load the schema for /rest/v1/parts/search, then execute with the search term. With pip install jentic the call is await client.search(...), await client.load(...), await client.execute(...) inside an asyncio.run wrapper.

Does the API return datasheet URLs?

Yes — /rest/v1/parts/{id} returns datasheet URLs alongside distributor pricing and stock when the manufacturer or distributor has supplied them.

Is the Octopart API free?

Octopart offers tiered API plans through Nexar with different request quotas and feature access. There is typically a developer tier for evaluation; production volume requires a paid plan.

Can I use GraphQL with Octopart?

Yes — the v4 API also exposes a GraphQL endpoint at /endpoint for advanced queries. The REST endpoints in this spec cover the most common search and lookup paths without requiring a GraphQL client.