Data Export

Use the conversation export endpoint when you need to pull conversation history from Applied into your warehouse, archive, or analysis workflow.

The export endpoint returns conversations with their messages inlined, so each page contains complete thread records for the conversations on that page.

Endpoint

GET https://core.appliedlabs.ai/v2026-04/conversations/export/

Send your Applied API key as a Bearer token and include the shop you want to export:

curl "https://core.appliedlabs.ai/v2026-04/conversations/export/?created_at__range=2026-04-01T00:00:00Z,2026-04-07T23:59:59Z&limit=100" \
  -H "Authorization: Bearer $APPLIED_API_KEY" \
  -H "X-Shop-Id: $APPLIED_SHOP_ID"

See Export conversations for the full API reference.

Page Through Results

Conversation export uses cursor pagination. Start with a date window and follow the next link until it is null.

Each page can return up to 100 conversations:

limit=100

Do not build cursors yourself. Use the next URL returned by the previous response.

Use Date Windows

Use created_at__range for backfills:

created_at__range=2026-04-01T00:00:00Z,2026-04-07T23:59:59Z

Use last_message_at__range when you want conversations with message activity in a window:

last_message_at__range=2026-04-01T00:00:00Z,2026-04-07T23:59:59Z

Each window can span up to 30 days. For larger exports, split the job into multiple windows and complete one window before starting the next.

Handle Rate Limits

Conversation export is rate limited per API token and shop. If you receive a 429 response, pause and retry with backoff before continuing from the same cursor.

For recurring jobs:

• Keep one active export worker per shop.
• Store the last completed window and cursor.
• Retry the same cursor after transient errors.
• Deduplicate records by conversation ID and message ID.

Export Shape

Each result is a conversation object with a messages array ordered from oldest to newest.

The endpoint includes public conversation and message fields such as IDs, timestamps, assignment IDs, status, resolution, channel type, tags, flags, message body, role, format, delivery status, and remote platform IDs.

The endpoint does not export attachment file bytes, internal search vectors, or raw internal metadata. Use media URLs and other resource-specific endpoints when you need related assets.