Skip to main content
PATCH
Pause or resume 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.
  • status is the only field this endpoint takes. Set paused to stop deliveries, or active to resume.
  • Tako pauses a channel itself after two consecutive failed deliveries, and sets status_reason to delivery_failures. Fix the destination, then resume — resuming clears the consecutive-failure count.
  • Pausing a channel doesn’t pause the monitors that post to it. They keep evaluating and recording firings; those firings just don’t reach this destination. To stop a monitor, pause the monitor.

Authorizations

X-API-Key
string
header
required

Path Parameters

id
string<uuid>
required

Resource id

Body

application/json
status
enum<string>
required

Set paused to stop deliveries, or active to resume. Resuming a paused channel clears the consecutive-failure count.

Available options:
active,
paused

Response

One channel, without its 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, and 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