Automations
Deactivate an automation
Stop an Instagram automation from processing new triggers and move it to paused, using expected_updated_at to reject a request built on a stale read.
POST
Deactivate an automation
Deactivating an automation stops it from processing new triggers and moves the
status to
This operation is not idempotent. Do not retry it automatically after an
unknown response.
paused. Your API key needs the automations:activate scope and
access to the account in the request body.
Send the automation ID in the path. Send account_id and the automation’s
latest updated_at value as expected_updated_at in the body. Both fields are
required and no other field is accepted.
A successful request returns 200 with the paused automation and its complete
typed configuration.
What deactivation does not change
Deactivation stops new trigger processing. It does not delete the automation, its configuration, its metrics, or its contact history. Activate the same automation again with Activate an automation when you want it to resume. Use Delete an automation when you want the automation archived instead of paused.Protect concurrent changes
Read the automation immediately before you deactivate it, then send its exactupdated_at value. If the automation changed after that read, the API returns
409 with api_automation_version_conflict. Read the automation again and
build a new request from the value it returns.
Example request
Example success response
Illustrative IDs, timestamps, and content. HTTP200.
Authorizations
Levios API key sent as a Bearer token.
Path Parameters
Body
application/json
Required string length:
20 - 32Pattern:
^(?:(?:(?!0000)\d{4})-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|02-(?:0[1-9]|1\d|2[0-8]))|(?:(?!0000)(?:\d{2}(?:0[48]|[2468][048]|[13579][26])|(?:[02468][048]|[13579][26])00))-02-29)T(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d{1,6})?(?:Z|[+-](?:[01]\d|2[0-3]):[0-5]\d)$Response
Successful response.

