GETMethod GET/partner/webhooks

By the end of this page, you will know how to list the notification subscriptions recorded in your brand's name and to walk through that list page by page.

Full address:

GET https://api.sealtrust.io/v1/partner/webhooks

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

#Authorization

API key in the Authorization header, in Bearer format, carrying the webhooks:read right. A key that does not carry that right receives a 403 whose message names the missing right.

A key belongs to a single brand. This list therefore contains only the subscriptions of the key's brand, and no other.

This read stays open whatever your plan. If your plan no longer includes notifications, you keep seeing which reception points are recorded in your name. It is creation and modification that require the plan.

#Call limit

Throughput is measured over a fixed 60 second window. The value applied is the one of your plan, or the one set on your account if we have set one. In the absence of both, the fallback value is 120 calls per window.

Two counters stack, with the same ceiling: one per key, one for the sum of all your brand's keys. Creating additional keys therefore does not increase the total allowed throughput.

The limit is checked before the key right check and before any database read. A call refused with a 403 for a missing right has therefore already consumed one unit of the current window's budget.

A 200 response carries four headers, which describe the more constraining counter of the two.

These four headers accompany the 200 response and the 429 response. On the other response codes, do not expect them: a key that is absent, unknown, revoked or expired is refused before any counting, and the other refusals do not report these values.

A refusal returns 429 with Retry-After, expressed in seconds remaining in the current window. That value is never lower than 1.

#Path and query parameters

This endpoint has no path parameter.

#Headers

#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 subscriptions at most.

curl -i -X GET "https://api.sealtrust.io/v1/partner/webhooks?skip=0&limit=20" \
  -H "Authorization: Bearer st_test_0000000000000000000000000000000000000000000000"

import { SealTrustClient } from "@sealtrust-io/sdk";

const sealtrust = new SealTrustClient({
  apiKey: "st_test_0000000000000000000000000000000000000000000000",
});

const page = await sealtrust.webhooks.list({ skip: 0, limit: 20 });

console.log(page.total);
for (const abonnement of page.items) {
  console.log(
    abonnement.id,
    abonnement.url,
    abonnement.event_types.join(", "),
    abonnement.health,
  );
}

import requests

response = requests.get(
    "https://api.sealtrust.io/v1/partner/webhooks",
    headers={
        "Authorization": "Bearer st_test_0000000000000000000000000000000000000000000000",
    },
    params={"skip": 0, "limit": 20},
    timeout=30,
)

print(response.status_code)

# X-RateLimit-Remaining is emitted twice. requests joins the two values
# with a comma: the first one is your key's, keep that one.
restant = response.headers["X-RateLimit-Remaining"].split(",")[0].strip()
print(restant)

print(response.json())

To read the next page, raise skip by the value of limit: skip=20 with limit=20, then skip=40, and so on until items is empty. The total field gives you the number of subscriptions to walk through.

#Example response

HTTP code 200.

{
  "items": [
    {
      "id": 41,
      "url": "https://exemple.test/sealtrust/evenements",
      "event_types": [
        "product.minted",
        "batch.completed",
        "batch.failed"
      ],
      "brand_id": 12,
      "is_active": true,
      "health": "healthy",
      "created_at": "2026-08-18T09:14:02.117043+00:00",
      "updated_at": "2026-08-18T09:14:02.117043+00:00"
    },
    {
      "id": 39,
      "url": "https://exemple.test/sealtrust/retours",
      "event_types": [
        "return.requested",
        "return.completed"
      ],
      "brand_id": 12,
      "is_active": false,
      "health": "degraded",
      "created_at": "2026-08-11T16:40:55.902881+00:00",
      "updated_at": "2026-08-19T07:02:31.448190+00:00"
    }
  ],
  "total": 2
}

The list is paginated, and sorted on the creation date, from the most recent to the oldest.

The response has two fields and nothing else.

Each entry of items has eight fields.

health is healthy at creation. It moves to degraded when we give up the delivery attempts on that address. It goes back to healthy on the first successful delivery that follows.

The signing secret of a subscription is never returned by this list, nor by any other read endpoint.

#Errors

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

This endpoint never returns 404. A brand with no subscription at all receives a 200 with an empty items and total at 0.

#See also

• POST /partner/webhooks, record an HTTPS address that will receive your events.
• GET /partner/webhooks/{webhook_id}, read a subscription and its delivery state.
• PUT /partner/webhooks/{webhook_id}, modify the address, the events or the secret of a subscription.
• DELETE /partner/webhooks/{webhook_id}, delete a subscription and the signing secret attached to it.
• Receive events by webhook, create a subscription, verify a signature, catch up on lost events.