Introduction
This document contains the resources necessary for a seller to integrate into the Seller Center platform. Using these resources, a seller can add the products they want to sell and the corresponding offer information to the marketplace.
Backward Compatibility
The Akinon Seller Center API undergoes continuous delivery updates to introduce fresh features, implement security enhancements, and address any bugs. Each newly deployed version is designed to be backward compatible, ensuring the resilience of your integration following an update. However, it's crucial that your integration adheres to the following guidelines:
Accommodate the addition of new fields in API responses. Periodically, we introduce new fields as part of feature enhancements.
Avoid relying on a fixed field order in API calls, as this order can change when new fields are added to APIs.
Design your integration to handle the inclusion of new values in enumeration fields. We may append new values to enumeration fields to support emerging features. It is recommended to use strings for deserializing enumeration fields, or configure your deserializer to accept unknown enumeration values.
HTTPS Only
All requests must use the HTTPS protocol.
Data Encoding
Text data is encoded in UTF-8.
Date Formats
API can use different date formats which are compliant with ISO8601:
date-time with the pattern
YYYY-MM-DDThh:mm:ss±hh:mm
The offset
+00:00
can be replaced byZ
(the zero UTC offset)All APIs provide date-times in UTC, with the trailing
Z
date-time-without-timezone with the pattern
YYYY-MM-DDThh:mm:ss
. The timezone does not appeartime with the pattern
hh:mm[:ss]±hh:mm
. Time only, with timezoneThe offset
+00:00
can be replaced byZ
(the zero UTC offset)Seconds may be omitted if equals to
:00
In the patterns:
YYYY
: years (four-digit)MM
: months, 01-12 (two-digit)DD
: days, 01-31 (two-digit)T
is a delimiter between the date and timehh
: hours, 00-23 (two-digit)mm
: minutes, 00-59 (two-digit)ss
: seconds, 00-60 (two-digit)±hh:mm
: refers to an offset from UTC
Localization
The marketplace might support multiple languages to localize content. If you would like to use specific localized data, specify the Accept-Language
header.
The Accept-Language
format is <ISO-639>-<ISO-3166>
(e.g. en-us
).
The API only accept languages that are equivalent to the languages activated in the back-office. The activated languages can be retrieved via LNG001
.
If there is no Accept-Language
header provided, the API always uses the default language.
Pagination
The API supports page and limit-based pagination. To navigate through the dataset, use the page
parameter to specify the page you want to view, and the limit
parameter to control how many items are displayed on each page. For example, setting the page
to 2
and the limit
to 10
would show items 11-20
in a series of 10
results per page.
Undocumented Attributes & Resources
Some resources may return more data than indicated in the documentation. Do not rely on this undocumented data, there is no guarantee about it.
Bulk Operation Limitations
The API limits the number of items processed in a single request. Unless otherwise specified, the maximum number of items that can be processed in a single request is 1000
. If you need to process more than 1000
items, you must split the request into multiple requests.
Rate Limiting
The API enforces rate limits on all endpoints. Exceeding these limits will result in 429 Too Many Requests
errors. The rate limits are as follows:
i1/languages
Unlimited
i2/categories
30
i2/products
10
i2/packages
20
i2/claims
20
Was this helpful?