Skip to main content

Authentication

Every Alerta v2 request requires an API key and API secret. Get them from Configuration > API Credentials in the Alerta dashboard.

Required Headers​

x-api-key: your_api_key
x-api-secret: your_api_secret
Content-Type: application/json

Both headers are required on every request. A missing or invalid value returns a 403 response.

Base URL​

https://api.alerta.encrisoft.com/v2

Example Request​

curl -X POST https://api.alerta.encrisoft.com/v2/slack/send \
  -H "Content-Type: application/json" \
  -H "x-api-key: $ALERTA_API_KEY" \
  -H "x-api-secret: $ALERTA_API_SECRET" \
  -d '{
    "channel": "alerts",
    "message": "Database replication lag exceeded threshold."
  }'

Idempotency​

Send and reply endpoints may accept an optional idempotency key to prevent duplicate deliveries if a request is retried:

x-idempotency-key: your-unique-event-id

Use a stable identifier tied to the event — for example, an incident ID or an alert UUID. If the same key is seen within the deduplication window, the request is acknowledged but not re-delivered.

Credential Rotation​

  1. Create a new credential in Configuration > API Credentials.
  2. Update your sending service to use the new values.
  3. Verify alerts are still being delivered.
  4. Delete the old credential.

See API Credentials for storage and rotation best practices.