Drücken Sie Enter, um das Ergebnis zu sehen oder Esc um abzubrechen.

Ankündigung Prisync API V2. 0!

Für die paar Wochen, Wir haben hart gearbeitet, auf die Schaffung einer besseren Prisync-API. Ich bin jetzt gespannt, laden zum ausprobieren Prisync API V2. 0!


Was gibt es neues?
Wir haben uns bemüht, erstellen Sie eine neue API als schlank und einfach zu bedienen wie möglich. Einige der Features, die wir auf die neue Version hinzugefügt:

  • A real RESTful API: Developers now can interact with the API using HTTP GET and POST methods.
  • SmartPrice Suggestions: We now suggest you SmartPrices per product on the API in a more meaningful way.
  • Expanded API Coverage: Now you can access all kind of resources (Produkte, URLs, Marken, categories etc.) on Prisync using the new API.
  • Pagination: Results are paginated where applicable, making it easier to access large collections such as product or URLs.
  • Accessible: You can access any single item (a product in a category or a URL in a product) with simple API endpoints.


You can find the complete documentation by clicking here:

Read the documentation


You can use your old API email and key which you already use on the old version. You can find API email and key on your Prisync account under Settings.


As a person with a technical background, I myself know that integrating a new API is not easy. Andererseits, the API v2.0 is way better than the 1st version, so that integrating v2.0 provides you a more expanded control of your account on Prisync and is beneficial. Außerdem, it is very easy to implement in any programming language such as Java, PHP, Python, Ruby, Go etc., much faster and less server resource consuming.


Future Plans: Considering the API integration period, we are going to continue to run the old API till April, 14Th 2018. Until we will shut down the old version, old version and API v2.0 will be both served. Starting with April, 15Th, old version won’t provide you fresh price data, Stattdessen, it’ll continue to serve the last price data we collected one more month, to prevent any service breakage on your side.


Please do not hesitate asking questions about the API v2.0 on the comments section.