Retrieves the collection of NotificationDestination resources.
const url = 'https://api.facteur.local/notification-destinations';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.facteur.local/notification-destinations \ --header 'Authorization: Bearer <token>'Retrieves the collection of NotificationDestination resources.
Authorizations
Section titled “Authorizations”- bearerAuthorg:read
Responses
Section titled “Responses”NotificationDestination collection
Where the alerts of the organization are written: an email address (or its owners and administrators), a Slack or Discord channel, or a PagerDuty or OpsGenie service.
object
The address the alerts are written to, or null for the owners and administrators of the organization; always null for a destination that is not an email.
Enough of the webhook address or of the integration key to recognise it (its host and its last four characters, or … and its last four characters), never the credential itself, which is stored sealed and never comes back. Null for an email destination.
When the last alert written to this destination was settled, sent or failed; null when none was. An email destination without an address has none.
The reason the last delivery was refused; null when it was accepted or when none was settled.
The language of the messages.
What the screen calls the destination.
The region of the OpsGenie account the key belongs to; null for every other kind.
The enabled alert rules that write to this destination, one per alert and scope.
object
The alert, such as quota.threshold.
The name of the workspace or of the inbox; null for the organization.
True when this destination is the only one the rule names: deleting it leaves the rule to the owners and administrators.
Example
[ { "kind": "email", "locale": "fr", "region": "eu", "usedBy": [ { "scopeKind": "organization" } ] }]No key, or a key that is refused. WWW-Authenticate says where to read how to present one.
A refusal, as RFC 9457 application/problem+json with the code of the register. A code adds the members its rule needs (retryAfter, permission…), so more members than these may come.
object
The stable code of the refusal. It never changes once shipped.
English prose for the person who reads the answer. It may be reworded: branch on code.
The HTTP status.
The name of the HTTP status.
The address of the problem: /errors/<code>.
On a body that fails validation, one entry per field.
object
Example
{ "code": "BAD_REQUEST", "status": 404, "title": "Not Found", "type": "/errors/INBOX_NOT_FOUND", "violations": [ { "code": "BAD_REQUEST" } ]}The key does not hold the permission of the operation, or the operation refuses every key.
A refusal, as RFC 9457 application/problem+json with the code of the register. A code adds the members its rule needs (retryAfter, permission…), so more members than these may come.
object
The stable code of the refusal. It never changes once shipped.
English prose for the person who reads the answer. It may be reworded: branch on code.
The HTTP status.
The name of the HTTP status.
The address of the problem: /errors/<code>.
On a body that fails validation, one entry per field.
object
Example
{ "code": "BAD_REQUEST", "status": 404, "title": "Not Found", "type": "/errors/INBOX_NOT_FOUND", "violations": [ { "code": "BAD_REQUEST" } ]}More calls than the key may make in a minute. Retry-After says when to try again.
A refusal, as RFC 9457 application/problem+json with the code of the register. A code adds the members its rule needs (retryAfter, permission…), so more members than these may come.
object
The stable code of the refusal. It never changes once shipped.
English prose for the person who reads the answer. It may be reworded: branch on code.
The HTTP status.
The name of the HTTP status.
The address of the problem: /errors/<code>.
On a body that fails validation, one entry per field.
object
Example
{ "code": "BAD_REQUEST", "status": 404, "title": "Not Found", "type": "/errors/INBOX_NOT_FOUND", "violations": [ { "code": "BAD_REQUEST" } ]}default
Section titled “default”Any refusal: an application/problem+json body whose code says which.
A refusal, as RFC 9457 application/problem+json with the code of the register. A code adds the members its rule needs (retryAfter, permission…), so more members than these may come.
object
The stable code of the refusal. It never changes once shipped.
English prose for the person who reads the answer. It may be reworded: branch on code.
The HTTP status.
The name of the HTTP status.
The address of the problem: /errors/<code>.
On a body that fails validation, one entry per field.
object
Example
{ "code": "BAD_REQUEST", "status": 404, "title": "Not Found", "type": "/errors/INBOX_NOT_FOUND", "violations": [ { "code": "BAD_REQUEST" } ]}