Skip to main content

Archive API — What You Can (and Can't) Do

A plain-language overview of the Archive Partners API (v2): what data is available, what actions are supported, platform coverage, and known limitations.

Written by Anne Buzzi
Updated today

The Archive Partners API (v2) gives you programmatic access to the enriched community data that Archive collects and maintains — social profiles, content, engagement metrics, and CRM-style attributes. This guide explains what is and isn't available so you can plan your integration before writing any code.

All requests are sent as POST requests to https://app.archive.com/api/v2 using GraphQL. For access tokens, please reach out using our support chat.


Platforms supported

The API returns data for content and profiles that Archive has already collected and enriched. If a post or profile has not been captured by Archive, it will not be available via the API.

  • Instagram — Feed posts, Reels, and Stories. Note: Stories do not have a public permalink, so originalUrl returns null for that content type.

  • TikTok — TikTok video content and creator profile data.

  • YouTube — Videos and Shorts, including thumbnails and channel profile data.


What you can read (queries)

The API is primarily read-only. The following queries are available:

  • items — Search and paginate all archived social content in your workspace. Filter by platform, content type, date, engagement range, hashtags, virality score, creator location, contract status, and more. Also supports visual and semantic search via superSearch.

  • mediaContents — Fetch the actual image and video files (URL, dimensions, thumbnail, duration) for a list of item IDs.

  • engagementHistory — Time-series snapshots of engagement metrics for a specific piece of content: likes, comments, views, shares, EMV, and virality score over time.

  • transcriptions — Plain-text transcriptions of spoken audio in video content. Fetch by media content IDs (max 20) or item IDs (max 1,000).

  • socialProfile — Profile data for a creator's social account: handle, follower count, verification status, and contact details. Can look up by ID or by account name + platform. Has an optional fallback to fetch live from the platform if not yet archived.

  • creator / creators — Unified creator records across platforms, including CRM-style custom attributes. Supports filtering by custom attribute conditions.

  • workspace / workspaces — Workspace metadata including tracked hashtags and mentions. Use workspaces to list all accessible workspaces and get their IDs.

  • filterPresets / customAttributeSchemas — List saved filter presets and custom attribute field definitions, useful for building UI dropdowns or interpreting CRM attribute values.


What you can write (mutations)

Two write operations are available, both related to collection management:

  • addItemToCollections — Add a content item to one or more collections by ID or name. Can auto-create collections by name if they don't exist yet.

  • removeItemFromCollections — Remove a content item from one or more collections.

There is currently no API mutation to create, import, or delete creators, social profiles, or content items. These records are created on Archive's side as a result of content being captured and tracked.


Engagement data available per item

For each piece of content, the following engagement data is accessible:

  • Views / plays / impressions

  • Likes

  • Comments

  • Shares

  • Earned Media Value (EMV), returned in cents

  • Virality score: HIGH, MEDIUM, LOW, or NOT_VIRAL

  • Historical time-series for all of the above, including follower count at the time of capture

Note: Engagement rate % is not a direct field — you can calculate it from the raw metrics returned. Reach, saves, and story exits are not exposed in the current schema.


What is not available

  • Creating or deleting content — you can only manage which collection items belong to, not create or delete the items themselves.

  • Instagram Story permalinksoriginalUrl returns null for Stories.

  • Content not yet archived — the API only returns data that Archive has already collected.

  • Reach, saves, or advanced story metrics — not exposed in the current schema.

  • Sending outreach or messages — no messaging functionality is available via the API.

  • Creating or modifying workspaces and filter presets — these can only be read, not created or updated.

  • Writing custom attributes via APIcustomAttributes can be read and filtered, but there is no mutation to set or update them.

  • Real-time webhooks or push notifications — the API is pull-only; no webhook or subscription mechanism is available.


Limits and technical notes

  • Pagination — All list queries use Relay-style cursor pagination. Default page size is 20 items.

  • Transcription limits — Max 20 items when fetching by mediaContentId, max 1,000 when fetching by itemId.

  • Authentication — Requires a Bearer token in the Authorization header. Most queries also require a WORKSPACE-ID header. The workspaces query is the exception and works without a Workspace ID.


For the full technical reference and query examples, visit app.archive.com/api/v2/docs.

Did this answer your question?