POSTMethod POST/partner/sellout

You declare that a product has left the shelf and has been handed over to the end customer, naming the point of sale that sold it.

The full address is https://api.sealtrust.io/v1/partner/sellout. The same route exists without the /v1 prefix, and the /v1 form is the one recommended for a new integration.

This call can be replayed. A product that is already activated returns the existing activation with status set to already_activated, and fills in only the information that was missing: the attachment to the point of sale, the country, the city. Nothing is overwritten. The Idempotency-Key header is not read by this endpoint.

#Authorization

API key in the Authorization header, in Bearer format, with the sellout:write scope.

Authorization: Bearer votre_clef

A key without that scope receives a 403 whose message names the missing scope.

Your brand's plan must also include API access. Otherwise you receive a 403 whose detail field carries the code FEATURE_NOT_AVAILABLE.

#Rate limit

Two distinct limits apply.

The rate counter starts again from zero at each new 60 second window. The daily quota starts again from zero at midnight universal time.

Every response that passes the rate limit carries the headers X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and X-RateLimit-Scope. X-RateLimit-Reset gives the instant of the reset, in seconds since January 1, 1970 in universal time. X-RateLimit-Scope equals key or brand, and designates the more constraining of the two counters. Creating extra keys does not increase the total rate allowed to your brand.

#Path and query parameters

This endpoint has no path or query parameter. Everything goes through the request body.

#Request body

Format application/json. Any field absent from this table causes the request to be refused with 422.

#The four accepted forms for identifier

We try them in this order, and we always restrict the lookup to your brand.

The serial number tolerates the common reading confusions. We read the letters I and L as the digit 1, the letter O as the digit 0, and we ignore case. We never resolve a product that has been destroyed or withdrawn.

#What country and city are worth when you omit them

If you do not send country, the country recorded is the one of the point of sale. Same rule for city. Fill in these two fields when the sale did not take place at the usual address of the point of sale.

#Example request

curl -i -X POST https://api.sealtrust.io/v1/partner/sellout \
  -H "Authorization: Bearer st_test_0000000000000000000000000000000000000000000000" \
  -H "Content-Type: application/json" \
  -d '{
    "identifier": "000000000000",
    "retailer_code": "BTQ-EXEMPLE-01",
    "country": "FR",
    "city": "Lyon"
  }'

const response = await fetch(
  "https://api.sealtrust.io/v1/partner/sellout",
  {
    method: "POST",
    headers: {
      Authorization:
        "Bearer st_test_0000000000000000000000000000000000000000000000",
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      identifier: "000000000000",
      retailer_code: "BTQ-EXEMPLE-01",
      country: "FR",
      city: "Lyon",
    }),
  },
);

console.log(response.status);
console.log(response.headers.get("X-RateLimit-Scope"));
console.log(await response.json());

import requests

response = requests.post(
    "https://api.sealtrust.io/v1/partner/sellout",
    headers={
        "Authorization": "Bearer st_test_0000000000000000000000000000000000000000000000",
        "Content-Type": "application/json",
    },
    json={
        "identifier": "000000000000",
        "retailer_code": "BTQ-EXEMPLE-01",
        "country": "FR",
        "city": "Lyon",
    },
    timeout=30,
)

print(response.status_code)
print(response.headers["X-RateLimit-Scope"])
print(response.json())

#Example response

HTTP code 200, first declaration for this product.

{
  "status": "activated",
  "activation_id": 1024,
  "product_id": 4096,
  "product_name": "Sac de voyage Exemple SAS",
  "retailer_code": "BTQ-EXEMPLE-01",
  "source": "sellout_declared",
  "activated_at": "2026-08-20T14:32:07.512430+00:00"
}

HTTP code 200 as well if the product had already been activated, for example by a scan from the end customer before your declaration.

{
  "status": "already_activated",
  "activation_id": 1024,
  "product_id": 4096,
  "product_name": "Sac de voyage Exemple SAS",
  "retailer_code": "BTQ-EXEMPLE-01",
  "source": "qr",
  "activated_at": "2026-08-19T09:14:55.201884+00:00"
}

The seven fields of the response.

#Errors

#The order of the checks, and what it changes for your quota

The checks run in this order: rate limit, brand's plan, existence of the point of sale, daily quota of the key, then resolution of the product.

One useful consequence: an unknown retailer_code does not consume your daily quota, whereas an identifier that cannot be found does consume it, because we resolve the product after the deduction. If you reconcile sales in batches, validate your point of sale codes once and for all, and expect unknown identifiers to cost one unit each.

#See also

• GET /certificate/{identifier}, read the certificate of authenticity of an item.
• Getting started with the console, the tour of the brand-side screens, in the order in which you use them.
• Partner API, overview, base address, keys, scopes, rate limits and pagination.
• API errors, recognize an error code and decide whether to fix or replay.