POSTMethod POST/partner-portal/interventions

You record an intervention that you have just carried out on a product: a repair, a servicing, a reconditioning, a recycling. The intervention is added to the history of the product, carries your name and states what you proved at the moment of recording it.

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

The partner portal is a different surface from the key-authenticated API. It authenticates with the session of a partner account, and an API key gives no access to it.

This call is not replayable. Two identical calls create two interventions. No idempotency header is read by this endpoint.

#Authorization

Session of a partner account, of repairer or recycler type. The session token is the one returned by POST /v1/auth/login, in the access_token field.

Authorization: Bearer <votre jeton de session>

The access_token session cookie is accepted as well. It is the form that the browser uses. It triggers the origin and anti-forgery token checks described below.

Call this endpoint from your server, with the Authorization header. A call issued by a browser page goes through additional origin and request forgery checks, which return a 403 when they are not satisfied.

Four conditions must be met for an intervention to be recorded.

1. The account is of repairer or recycler type. Otherwise the response is a 403.
2. The account has at least one active accreditation. Otherwise the response is a 403 carrying the message Aucune accréditation active.
3. The product belongs to a brand that has accredited this account. Otherwise the response is a 403 or a 404.
4. The intervention type is covered by your accreditations on the brand of this product. Otherwise the response is a 422 that lists the allowed types.

Accreditations are granted by the brand, brand by brand. One same account can hold both types on one same brand, and the allowed intervention types are then the union of the two sets.

The GET /v1/partner-portal/products/{identifier} endpoint returns the allowed_event_types list computed for the product concerned, which saves you from guessing.

#Call limit

A call limit applies to this endpoint. It is set for the normal use of the portal, where you look for a product then record an intervention.

Beyond it, the API replies 429. The refusal carries a Retry-After header that gives the number of seconds to wait. Wait that delay, then call again.

The limit covers the whole partner portal. Alternating between the endpoints therefore gives you no margin back. Space out your calls instead of sending them in bursts.

The value of the limit is not a commitment and can change without notice. Do not hard-code any threshold in your code, rely on Retry-After.

There is neither a daily quota nor a per brand counter here: these two mechanisms are attached to API keys, and the partner portal uses none.

#Path and query parameters

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

#Request body

application/json format. Any field absent from this table gets the request refused with a 422.

#The four accepted forms for identifier

They are tried in this order, and the search is bounded to the brands that have accredited you.

The token identifier has 77 to 78 digits. It is stored and returned as a string of characters. Declare it as a string in your integration, and size the field accordingly.

The serial number tolerates the common reading confusions: the letters I and L are read as the digit 1, the letter O as the digit 0, and case does not matter. It is the form to favor when you have the object in hand, because it is the only one printed on it. A destroyed or withdrawn product is never resolved.

#The proof level, and how to raise it

An accreditation says that you have the right to work on the products of a brand. It does not say that this precise product passed through your hands, and the identifier is printed on the object. The proof_level field of the response therefore records what you actually proved.

The end customer generates their handover code from their account, through POST /v1/custody/repair-codes. The code is 8 characters long and is displayed only once. It is valid for a single product, is used only once, and expires after 30 days by default, a duration that the issuer can set between 1 and 365 days. The work order is issued by the brand from its console, and it names both the product and your account.

A refused code cancels the whole call, and nothing is recorded. If the code does not go through, check it with the customer, or record the intervention without proof_code, at the declared level.

#Example request

curl -i -X POST https://api.sealtrust.io/v1/partner-portal/interventions \
  -H "Authorization: Bearer VOTRE_JETON_DE_SESSION" \
  -H "Content-Type: application/json" \
  -d '{
    "identifier": "000000000000",
    "event_type": "repair",
    "title": "Remplacement de la fermeture éclair",
    "description": "Ancienne fermeture remplacée par une pièce du fabricant.",
    "metadata": {
      "duree_minutes": 45,
      "pieces": ["fermeture éclair"]
    },
    "proof_code": "23456789"
  }'

const response = await fetch(
  "https://api.sealtrust.io/v1/partner-portal/interventions",
  {
    method: "POST",
    headers: {
      Authorization: "Bearer VOTRE_JETON_DE_SESSION",
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      identifier: "000000000000",
      event_type: "repair",
      title: "Remplacement de la fermeture éclair",
      description: "Ancienne fermeture remplacée par une pièce du fabricant.",
      metadata: {
        duree_minutes: 45,
        pieces: ["fermeture éclair"],
      },
      proof_code: "23456789",
    }),
  },
);

console.log(response.status);
console.log(await response.json());

import requests

response = requests.post(
    "https://api.sealtrust.io/v1/partner-portal/interventions",
    headers={
        "Authorization": "Bearer VOTRE_JETON_DE_SESSION",
        "Content-Type": "application/json",
    },
    json={
        "identifier": "000000000000",
        "event_type": "repair",
        "title": "Remplacement de la fermeture éclair",
        "description": "Ancienne fermeture remplacée par une pièce du fabricant.",
        "metadata": {
            "duree_minutes": 45,
            "pieces": ["fermeture éclair"],
        },
        "proof_code": "23456789",
    },
    timeout=30,
)

print(response.status_code)
print(response.json())

#Example response

HTTP code 201.

{
  "id": 8123,
  "product_id": 4096,
  "brand_id": 12,
  "event_type": "repair",
  "proof_level": "customer_code",
  "title": "Remplacement de la fermeture éclair",
  "description": "Ancienne fermeture remplacée par une pièce du fabricant.",
  "event_metadata": {
    "duree_minutes": 45,
    "pieces": ["fermeture éclair"],
    "partner_type": "repairer"
  },
  "performed_by": "Atelier Exemple (réparateur accrédité)",
  "product_name": "Sac de voyage Exemple SAS",
  "occurred_at": "2026-08-20T14:32:07.512430+00:00",
  "created_at": "2026-08-20T14:32:07.512430+00:00"
}

The twelve fields of the response.

#What performed_by contains

This field is built from your account, followed by the capacity in which you intervened, for example réparateur accrédité. The value retained is your first name and your last name, failing that the name of your company, failing that the email address of the account. Fill in your name or your company in your profile if you do not want your email address to appear in the history of the products.

#What partner_type contains

The partner_type key is added to metadata when you do not provide it. It is repairer for the four repair intervention types, and recycler for the four end-of-life types. If you send this key yourself, your value is kept.

#Errors

#See also

• GET /partner-portal/interventions, list the interventions that your account has recorded.
• GET /partner-portal/products/{identifier}, find a product of a brand that has accredited you.
• GET /partner-portal/me, read your partner profile and the brands that have accredited you.