List notification endpoints
Where your notifications are sent, oldest first.
A disabled endpoint is still listed, with disabled: true. Removing an endpoint disables
it rather than deleting the row — the record of where something was sent is kept — so a
list that hid disabled endpoints would make a removal look like a disappearance and leave
no way to turn one back on.
disabled_reason is set when we disabled the endpoint ourselves, after repeated delivery
failures. usable: false means the stored destination cannot be delivered to at all;
unavailable-shaped rows like that are listed on purpose, because they are the ones worth
deleting.
Free.
Authorization
bearerAuth Your API key, sent as Authorization: Bearer rc_live_….
In: header
Query Parameters
Page size.
1 <= value <= 10020Return the page after the object with this id. Cannot be combined with ending_before.
uuidReturn the page before the object with this id. Cannot be combined with starting_after.
uuidResponse Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://api.registercheck.de/v1/notification-endpoints" \ -H "Authorization: Bearer $REGISTERCHECK_API_KEY"{ "object": "list", "has_more": true, "data": [ { "id": "string", "object": "notification_endpoint", "channel": "email", "destination": "string", "disabled": true, "disabled_at": "2019-08-24T14:15:22Z", "disabled_reason": "string", "usable": true, "unusable_reason": "string", "metadata": { "crm_id": "0015g00000XyZ", "team": "kyc" }, "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z" } ]}