Automations
Create an automation
Create an Instagram automation from one complete typed configuration and receive its ID, status, trigger type, timestamps, and stored configuration.
POST
Create an automation by sending an accessible
account_id, a name, a
status, and one complete configuration. All four fields are required and no
other field is accepted. Your API key needs the automations:write scope.
There are no template identifiers in API v1. The configuration you send is the
configuration the automation runs.
Choose the starting status
status is an enum with two values:
Creating a
live automation needs the automations:activate scope in addition
to automations:write. Create a draft first when you want to review the
stored configuration before it runs.
A successful request returns 201 with the stored automation.
Send the complete configuration
configuration is a complete, typed object. It is not a partial merge and it
has no server-side defaults to fall back on. Five sections are required:
The OpenAPI document is the source of truth for every
field, enum, bound, and nested action shape. Its
PublicAutomationCreateV1
schema defines the complete request body. The API rejects unknown properties
and returns 422 with api_automation_invalid_configuration and a list of
issues in error.details.issues.
Use List Instagram media to find the media id for a
trigger that watches one specific publication.
Example request
Retry behavior
Creating an automation is not idempotent. An automatic retry can create a second automation.Carousel messages
Use Send carousel messages for image cards, URL buttons, a complete request, and a separate following message.Example success response
Illustrative IDs, timestamps, and content. HTTP201.
Authoring guides
Authorizations
Levios API key sent as a Bearer token.
Body
application/json
The body is of type any.
Response
Successful response.

