Skip to main content
GET
Get a notification channel

Notes

  • To authenticate, you’ll need a Tako API key. It’s best practice to store it as an environment variable to avoid hardcoding sensitive credentials in your code.
  • An id you don’t own returns 404.
  • This response leaves out secret, and so does every request except create. Use this endpoint to check where a channel points and whether it’s still delivering.
  • status_reason is delivery_failures when Tako paused the channel after 2 consecutive failed deliveries, and null when the channel is active or when you paused it yourself. For what counts as a failed delivery, see How Tako retries.

Authorizations

X-API-Key
string
header
required

Path Parameters

id
string<uuid>
required

Resource id

Response

One notification channel, without its signing secret

id
string<uuid>
required
name
string
required
kind
enum<string>
required

How Tako shapes the request body it posts to a channel. webhook sends nested JSON that namespaces the monitor, the firing, and the payload. slack_workflow sends a flat body of strings for a Slack Workflow Builder trigger, which rejects any nested value.

Available options:
webhook,
slack_workflow
url
string
required
status
enum<string>
required
Available options:
active,
paused
status_reason
enum<string> | null
required

Why Tako paused the channel. Null while the channel is active, and null when you paused it yourself.

Available options:
delivery_failures
created_at
string<date-time>
required
updated_at
string<date-time>
required