GETMethod GET/partner-portal/interventions

You receive the history of the lifecycle events your account authored: repair, maintenance, reconditioning, after-sales service, recycling, end of life, destruction and return. In practice, these are the interventions you recorded from the partner portal. Each entry carries the product concerned, the proof level retained at the time of recording, and the date. The list is paginated and sorted from the most recent to the oldest.

Full address:

GET https://api.sealtrust.io/v1/partner-portal/interventions

The same endpoint also answers without the /v1 prefix, at https://api.sealtrust.io/partner-portal/interventions. Both addresses call the same code. Use the /v1 form for a new integration.

#Authorization

A partner account session, of the repairer or recycler type. You present the session token obtained at login (POST /auth/login) in either of two ways:

• the Authorization: Bearer <session token> header, for a call from your own code;
• the access_token session cookie, which a browser sends on its own when you call from the partner portal.

The partner API key does not open this endpoint. It serves the machine-to-machine surface /v1/partner/*, which is a separate surface.

An account whose role is neither repairer nor recycler receives a 403.

#Rate limit

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

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

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

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

This endpoint consumes no product quota and no daily quota.

#Path and query parameters

This endpoint has no path parameter.

There is no other parameter. The list cannot be filtered by product, by brand, by intervention type, or by date. Do that filtering in your own code from the fields returned.

#Headers

A server-to-server call that carries the Authorization header is accepted without an Origin or Referer header. A browser call that carries the session cookie must come from an authorized SealTrust domain, otherwise the response is 403.

#Request body

This endpoint has no request body. All the information you send fits in the two query parameters above.

#Example request

The first page, twenty interventions at most.

curl -i -X GET "https://api.sealtrust.io/v1/partner-portal/interventions?skip=0&limit=20" \
  -H "Authorization: Bearer JETON-DE-SESSION-DE-DEMONSTRATION"

const reponse = await fetch(
  "https://api.sealtrust.io/v1/partner-portal/interventions?skip=0&limit=20",
  {
    method: "GET",
    headers: {
      Authorization: "Bearer JETON-DE-SESSION-DE-DEMONSTRATION",
    },
  },
);

const page = await reponse.json();

console.log(reponse.status, page.total);
for (const intervention of page.items) {
  console.log(
    intervention.id,
    intervention.event_type,
    intervention.proof_level,
    intervention.product_name,
    intervention.occurred_at,
  );
}

import requests

response = requests.get(
    "https://api.sealtrust.io/v1/partner-portal/interventions",
    headers={
        "Authorization": "Bearer JETON-DE-SESSION-DE-DEMONSTRATION",
    },
    params={"skip": 0, "limit": 20},
    timeout=30,
)

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

To read the next page, increase skip by the value of limit: skip=20 with limit=20, then skip=40, and so on. The total field gives you the number of interventions to go through.

#Example response

HTTP code 200.

{
  "total": 2,
  "count": 2,
  "skip": 0,
  "limit": 20,
  "items": [
    {
      "id": 812,
      "product_id": 4471,
      "brand_id": 12,
      "event_type": "repair",
      "proof_level": "customer_code",
      "title": "Remplacement du joint d'étanchéité",
      "description": "Joint remplacé, étanchéité contrôlée à 5 ATM.",
      "event_metadata": {
        "partner_type": "repairer",
        "replaced_parts": "joint torique",
        "cost_eur": 48,
        "notes": "Pièce d'origine"
      },
      "performed_by": "Atelier Exemple (réparateur accrédité)",
      "product_name": "Lampe d'atelier Exemple",
      "occurred_at": "2026-08-19T14:32:07.481920Z",
      "created_at": "2026-08-19T14:32:07.481920Z"
    },
    {
      "id": 796,
      "product_id": 4318,
      "brand_id": 12,
      "event_type": "maintenance",
      "proof_level": "declared",
      "title": "Révision annuelle",
      "description": null,
      "event_metadata": {
        "partner_type": "repairer"
      },
      "performed_by": "Atelier Exemple (réparateur accrédité)",
      "product_name": "Lampe d'atelier Exemple",
      "occurred_at": "2026-08-11T09:05:44.220118Z",
      "created_at": "2026-08-11T09:05:44.220118Z"
    }
  ]
}

The response has five fields.

Each entry in items has twelve fields.

event_type takes one of the eight values a partner account can record. Four belong to repair: repair, maintenance, reconditioning, after_sale_service. Four belong to end of life: recycling, end_of_life, destruction, return. A single entry carries only one of these values.

proof_level takes one of these values.

The service writes proof_level at creation and never changes it afterward.

event_metadata carries the partner_type key, which reads repairer or recycler, on the interventions recorded from the partner portal. The field can read null, and an older entry may not carry this key. Test for its presence before reading it.

The other keys are the ones you sent. The partner portal writes replaced_parts and cost_eur there for a repair, recovered_materials and method for an end-of-life treatment, and notes in both cases.

#Errors

The body of an error response carries a detail field. Depending on the case, this field contains a sentence or a list.

This endpoint never returns 404 for an empty history. A partner account that has recorded nothing yet receives a 200 with items empty and total at 0.

#See also

• POST /partner-portal/interventions, record an intervention on a product.
• GET /partner-portal/products/{identifier}, find a product of a brand that accredited you.
• GET /partner-portal/me, read your partner profile and the brands that accredited you.