Skip to content

Add TrustedParts.com (ECIA) info provider - #1519

Open
killecaptron wants to merge 1 commit into
Part-DB:masterfrom
killecaptron:add-trustedparts-provider
Open

Add TrustedParts.com (ECIA) info provider#1519
killecaptron wants to merge 1 commit into
Part-DB:masterfrom
killecaptron:add-trustedparts-provider

Conversation

@killecaptron

@killecaptron killecaptron commented Sep 3, 2026

Copy link
Copy Markdown

TrustedParts.com is a part search engine operated by the Electronic Components Industry Association, which aggregates stock, prices and specifications of authorized distributors. Its Inventory API is free to use, but requires an approved account (company ID + API key).

The API has no part IDs, parts are always identified by their part number, so the provider IDs are built as "manufacturer|mpn". A single search already returns all offers and specifications, therefore the results are cached and reused for the detail view.

As the API can search up to 50 part numbers in a single request, the provider also implements BatchInfoProviderInterface for the bulk import.

Requests are sent with a user agent identifying Part-DB and the current user ID, as required by the API terms of use for non-website applications.

The datasheet links of this provider are redirect URLs without a file extension, which uncovered a separate problem in Attachment::isPicture() (broken preview images). That is fixed in #1520, independently of this PR.

TrustedParts.com is a part search engine operated by the Electronic
Components Industry Association, which aggregates stock, prices and
specifications of authorized distributors. Its Inventory API is free to
use, but requires an approved account (company ID + API key).

The API has no part IDs, parts are always identified by their part
number, so the provider IDs are built as "manufacturer|mpn". A single
search already returns all offers and specifications, therefore the
results are cached and reused for the detail view.

As the API can search up to 50 part numbers in a single request, the
provider also implements BatchInfoProviderInterface for the bulk import.

Requests are sent with a user agent identifying Part-DB and the current
user ID, as required by the API terms of use for non-website
applications.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant