Spec

130 views
Skip to first unread message

MatthieuP

unread,
May 9, 2018, 7:23:58 PM5/9/18
to Octopart API

Hello,

I just do one script with your API for saving all specification.  For some component, it’s ok but for most of them this one doesn’t work.

 

Example:

 

2N7000 (No problem) : https://octopart.com/api/v3/parts/match?queries=[{sku:2N7000}]&apikey=6faa0cf9&pretty_print=true&include[]=specs

 

BSS806NEH6327XTSA1 (No information)

 

https://octopart.com/api/v3/parts/match?queries=[{“sku”:”BSS806NEH6327XTSA1”}]&apikey=6faa0cf9&pretty_print=true&include[]=specs

 

Inside Octopart , I can find this information https://octopart.com/bss806neh6327xtsa1-infineon-30580025?r=sp&s=QazvazCUQxOBgeHyB_ASdg , could you check if it’s possible to have their data by the API.

 

Thanks you in advance for your help,

Matthieu

ji...@octopart.com

unread,
May 9, 2018, 7:40:02 PM5/9/18
to Octopart API
Hi MatthieuP,
It looks like you can improve reliability of each of those requests by using ASCII quotes in your JSON string.

For example:

https://octopart.com/api/v3/parts/match?queries=[{"sku":"2N7000"}]&apikey=6faa0cf9&pretty_print=true&include[]=specs

https://octopart.com/api/v3/parts/match?queries=[{"sku":"BSS806NEH6327XTSA1"}]&apikey=6faa0cf9&pretty_print=true&include[]=specs

Both of the above requests result in proper behavior for me in Firefox.

Note that in your example ("BSS806NEH6327XTSA1") you are using “ which is different from " and I suspect that is what is causing the error.

Jimmy
Reply all
Reply to author
Forward
0 new messages