Нажмите ENTER, чтобы посмотреть результаты или нажмите ESC для отмены.

Объявление Prisync API v2.0!

За пару недель, Мы упорно трудились над созданием лучшего Prisync API. Сейчас я рад предложить вам попробовать Prisync API v2.0!


Что нового?
Мы стремился создать новый API как рациональный и простой в использовании, насколько это возможно. Некоторые из особенностей, которые мы добавили в новой версии:

  • 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 (Продукция, URL-адреса, Бренды, 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. С другой стороны, 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. К тому же, 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 Апрель, 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, Вместо этого, 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.