Why configure the API?

It is very important to enable the API, because it is like an "automatic assistant" for your catalog on the Enex marketplace. Instead of manually updating prices and specifying how many items are left, the API does it for you automatically.

When prices and balances are updated immediately and without errors, your products are always displayed correctly: customers see which products are in stock and which will have to wait; and customers are confident in the correctness of prices. This helps you avoid losing customers, because no one wants to order something that doesn't exist or face refunds.

Automatic updates via the API speed up and simplify your work: you save time and effort, and your sales become more stable. If information about balances and prices is always up to date, this increases customer trust and improves your brand's reputation on the platform, which also attracts more customers.

As a result, the API helps to sell more and work more efficiently, avoiding loss of orders and errors due to outdated data. It's like a reliable assistant who always keeps your assortment in order and helps you earn more.

The API configuration process

To update information about the inventory of goods and their prices, the API functionality is implemented on the platform, which you can use.

First, get an access key (API Token). It can be created in your Personal Account on the website https://enex.market/account/api /(log in with your username to view the information).
All information on using the API, as well as examples of requests in JSON format, can be found in the documentation at https://enex.market/api/v1/schema .
To update, send data via curl requests, making sure to specify your API Token in the Authorization field in the request headers.
The query format and data structure are described in detail in the documentation to simplify integration and minimize errors.

If you have any questions during the setup process, we have collected answers to the most common ones below.

Frequently Asked Questions

General questions

I can't log into my Personal Account to generate an API access key. Where can I find my username and password?

When registering, you received an automatic email with all your credentials. If the email is lost, use the password reset form or contact your manager.

Can I transfer prices and balances before creating my catalog on the website?

No, first you need to fill out a template for creating a catalog on the site (independently or as part of promotion services). After that, it is possible to update the data either through a file or using the API.

What should I do if we don't have a developer and only have a price list in xlsx?

You can hire an outsourced developer or a contractor's web studio. Setting up data transfer takes a short time and will not be expensive. You can also periodically update prices, balances, and other data through your Personal Account using quick update functionality.

Can Enex specialists connect to our API or any links/services containing information about our products themselves?

An API is a programming interface that sends us data. Our server itself does not request anything, but only accepts data. We did not implement your API. We will be glad if you can send the data yourself according to the scheme above.Please schedule your developer's time. It usually takes a short time to set up according to the instructions.

Is the XML format accepted?

The XML format is currently not accepted.

Is there a ready-made processing for data exchange with 1C?

Unfortunately, not yet.

Commercial issues

What prices should I send? What if we have non-final prices in our system, for example, without VAT?

It is necessary to transfer the final sale prices, including all taxes and commission to Enex. If the prices in your system are non-final, then you need to perform the appropriate mathematical calculations during the transfer.

We do not want to transfer the leftovers, as this is confidential information. What should I do?

Some suppliers report inaccurate quantities in stock. For example, if 0, then 0 is transmitted; if from 1 to 4, then 1 is transmitted; if from 5 to 19, then 5 is transmitted; if more than 20, then 20 is transmitted. Or if the supplier always has everything in stock, then average balances can be transferred, for example, all at 20.

We have several warehouses. Which warehouse should I specify the leftovers for?

If it is possible to transfer the amount of balances from all warehouses, then it is better to do so. If this is not possible, then transfer the leftovers from the main warehouse.

How often should I send the data?

Usually, once a day is enough, but you can send data more often at your discretion. It should not be sent more than once an hour.

Technical issues

Are there examples in different languages in the documentation?

Description of available methods, examples of queries and possible ones (depending on the input data)The answers can be found in the API Methods reference at https://enex.market/api/v1/schema/swagger . Examples of requests via bash are also available there.

To see examples in different programming languages, you need to visit the https://enex.market/api/v1/schema/elements #/, go to any of the methods of interest and in the Request Sample section (just below on the right) and select the required programming language. The window will display an example script for the selected method and language.

Error 401 and the message Wrong user type

This means that the user uses the wrong link for their group, for example, a Manufacturer who is trying to upload products using a link intended for a trading company (TC).
The manufacturer must use the api/v1/products/update/manufacturer link,
and the TC api/v1/products/update/trade_company

Error 404 when accessing the API schema

Try clearing the cache.

Error 500 when requesting a token

Repeat the token request. If an error occurs again, contact your manager.

What are limit and offset in the request for catalog / trade offer data?

The entire list can be downloaded from the specified link.limit- the number of products returned in the request when 0 or a value greater than 5,000 is specified (the maximum value of 5,000 items is substituted).tuted).offset - the shift in the list. That is, if you have 9,000 items, for example, then you will need to send two requests: the first one will return the first 5,000 items https://enex.market/api/v1/products/limit/0/offset/0 , the second one will return the remaining 4000 https://enex.market/api/v1/products/limit/0/offset/5000

Is it possible to update only the prices or only the balances? What should I send for this, zeros or just don't send anything?

When transmitting data to the API, it is allowed to transmit the price and balances, or only one of these parameters. For example, to update only the balances, you can pass the "quantity" field and omit the "price" field{
"article": "125111",
"quantity": 7,
}

Which service can we use to set up automatic transmission?

Postman; other solutions are not available from Russia directly.

Is there a limit to the amount of information transmitted?

As there is no such restriction, but in order for the request not to fall, it is recommended to transfer no more than 20 thousand positions per request.

If we upload 3000 items, which is better, in the request body or in a file? If it's in a file, where should I place it?

Binary data transfer via a POST request is available. You transfer and store the file yourself.

Can we provide other data besides prices and balances?

At the moment, such functionality is not provided.

I DID NOT FIND THE ANSWER TO MY QUESTION

Automatic price updates on Enex