GETMethod GET/partner/webhooks/{webhook_id}

You read a single notification subscription, designated by its number. By the end of this page, you will know how to retrieve its destination address, the list of events it is subscribed to, whether it is on or off, and whether our deliveries to it succeed.

Full address:

GET https://api.sealtrust.io/v1/partner/webhooks/{webhook_id}

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

#Authorization

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

A subscription is visible only to a key of the brand it belongs to. A subscription number that belongs to another brand answers 404, just like a number that does not exist. The response never says whether the subscription exists elsewhere.

This read stays open whatever your plan. Only creating and changing a subscription require your plan to include notifications.

#Rate limit

We measure the rate over a fixed 60 second window. We apply the value set on your account if we set one, otherwise the one from your plan. With neither, the fallback value is 120 calls per window.

Two counters overlap, with the same limit: one per key, one for the sum of all your brand's keys. Creating extra keys therefore does not raise the total rate allowed.

We authenticate your key first. We then check the limit, before checking the webhooks:read scope and before any read of the subscription.

A refusal returns 429 with Retry-After, expressed in seconds remaining in the current window. This value is never below 1. Set your retries from Retry-After.

#Rate limit headers

The response carries a set of X-RateLimit-* headers describing the more constraining of the two counters, your key's or your brand's.

We check your key before running its counter. A 401 response therefore carries only the set from the second counter, and no X-RateLimit-Scope.

#Path and query parameters

This endpoint has no query parameter.

#Headers

#Request body

None. This request has no body.

#Example request

Reading subscription number 7.

curl -i https://api.sealtrust.io/v1/partner/webhooks/7 \
  -H "Authorization: Bearer st_test_0000000000000000000000000000000000000000000000"

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

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

const abonnement = await sealtrust.webhooks.get(7);

console.log(abonnement.url, abonnement.events, abonnement.health);

import requests

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

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

#Example response

HTTP code 200.

{
  "id": 7,
  "brand_id": 12,
  "url": "https://exemple-sas.test/sealtrust/evenements",
  "events": [
    "product.minted",
    "batch.completed"
  ],
  "is_active": true,
  "health": "healthy",
  "created_at": "2026-08-14T09:12:44.318000Z",
  "updated_at": "2026-08-20T07:03:11.902000Z"
}

The response has eight fields and nothing else.

health reads healthy as long as our deliveries to this address succeed. It moves to degraded when the last retry attempt fails in turn, and it returns to healthy as soon as a delivery succeeds. We write only these two values.

#Errors

The body of an error response carries a detail field.

#See also

• GET /partner/webhooks, list your notification subscriptions, page by page.
• PUT /partner/webhooks/{webhook_id}, change 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.
• Receiving events by webhook, create a subscription, verify a signature, catch up on lost events.