Buerklin Information Provider

[mkne]

Bürklin also offers an API. (Apply here: https://www.buerklin.com/de/services/eprocurement/)
I have already started to implement an Information Provider (https://github.com/mkne/Part-DB-server/tree/Buerklin-provider) but I have hardly any PHP experience.
Authorization works via Bearer Token that is requested via a POST-action to https://www.buerklin.com/authorizationserver/oauth/token/ and the following parameters:
client_id:cws-client
client_secret:{{PROVIDER_BUERKLIN_SECRET}}
grant_type:password
username:{{PROVIDER_BUERKLIN_USERNAME}}
password:{{PROVIDER_BUERKLIN_PASSWORD}}

There are only two GET-actions available:

• Product search (example with the part number 66S447): https://www.buerklin.com/buerklinws/v2/buerklin/products/66S447/?curr=EUR&language=de
• Free text search (example with the query string 'Resistor'): https://www.buerklin.com/buerklinws/v2/buerklin/products/search/?curr=EUR&language=en&pageSize=50&currentPage=0&query=Resistor&sort=relevance

I would set the parameters curr and language via PROVIDER_BUERKLIN_CURRENCY and PROVIDER_BUERKLIN_LANGUAGE.

I tried to implement it based on the LCSC Info Provider but realized that this was not the right choice as it doesn't use Authentication.
I also have difficulties to map the JSON-Results of the get requests to the appropriate DTOs.
Which information provider would be the best one to use as a template for this kind of API? Is someone willing to help with the implementation? I haven't found any description of the JSON response schema and also the API description is very limited, There's not much more information in it as explained above. However Bürklin supplies a postman collection which can be used to test the API.

[jbtronics]

That authentication looks like a classic OAuth flow. The Octopart provider uses something similar. Digikey (there you even have the more complex flow, where the user has to login at the digikey homepage to get the token).

The token storage logic is already there and most of the oauth authentication flow, so that the provider can focus mostly on using the bearer token, not so much retrieving it.