Automations
Get Automation Activity
Cursor-paginated audit log for one automation
GET
Documentation Index
Fetch the complete documentation index at: https://www.ayrshare.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Beta. See the Automations Overview for the full feature description.
Activity row status
Each row has a top-levelstatus plus a per-action status inside actionResults[].
| Status | When it’s recorded |
|---|---|
pending | Row was just written; the worker hasn’t picked it up yet |
in_flight | The worker is currently dispatching |
sent | Every action succeeded |
failed | At least one action failed (and none hit an auth error) |
auth_error | The Instagram access token was invalid; the DM was not retried |
rate_limited | The daily DM cap (tier or per-profile) was hit. No DM was sent |
deduplicated | This action already fired to this recipient inside its dedup window (default 7 days, per-action configurable) |
skipped | The automation became inactive or was deleted between fan-out and dispatch |
pending and in_flight are transient; everything else is terminal.
Header Parameters
Path Parameters
The automation ID returned from
POST /automations.Query Parameters
Page size. Default
25, max 100. Values outside [1, 100] are clamped; non-integer or ≤0 returns HTTP 400.Opaque cursor from a previous response’s
meta.next. Omit on the first request.Forward-only — passing ?previous= returns HTTP 400.Response Shape
The response wraps the result list inactivity[] and the cursor info in meta:
meta.next is a base64-encoded opaque blob — treat it as a black box and pass it back unchanged in the next request’s ?next=. meta.hasMore is true when at least one more page exists.
