Skip to Content
Introduction

Archive API

Programmatic access to your Archive workspace: every piece of UGC, every creator in your CRM, every engagement snapshot, every saved view and collection — accessible through a single GraphQL endpoint that returns the same data your team sees in the Archive UI.

If your team uses Archive to track creator content and you want to push that data somewhere — a dashboard, a data warehouse, a CRM, an internal LLM workflow, an Airtable base — this API is the way.

What you can do

Filter posts by hashtag, creator, platform, engagement range, date, location, virality, usage-rights status. Sort by EMV, likes, comments, views, or shares.

Search and filter UGC

Read the latest snapshot, the full historical curve, or force a fresh refresh on a known set of posts.

Pull engagement data

Search creators by name, email, location, label, or any custom attribute. Pull every social profile linked to a creator.

Query your creator CRM

Resolve a handle or URL to a full profile — followers, verification, contact info — with optional fallback to fetch fresh platform data.

Look up social profiles

Iterate items inside any saved Content View or Collection. Add or remove items from a collection programmatically.

Read views and collections

Pull the campaigns in your workspace and the items inside each one.

List campaigns

Send Archive an Instagram, TikTok, or YouTube post URL and the post lands in your workspace in ~30–75 seconds.

Import a UGC by URL

Get started

Getting StartedGenerate a token, set up your client (Postman, curl, or Claude via the API System Prompt), and run your first request.
WorkspacesDiscover the workspaces your token has access to and pick the one to use.
Best PracticesRate limit, batching, caching, and the production-design choices that determine whether your client is fast or slow.
For Coding AgentsSame ground as Best Practices, written defensively against the mistakes AI agents (Claude, Cursor, ChatGPT) tend to make on this API.
RoadmapRecently shipped, coming soon, and feature requests.

Endpoint and authentication

All requests are POST to a single GraphQL endpoint:

POST https://app.archive.com/api/v2

Two headers on every request (except the workspaces query, which only needs the first):

Authorization: Bearer <ARCHIVE_APP_TOKEN>
WORKSPACE-ID: <workspace-uuid>

Generate your token from the Archive UI under Settings → API — see Generating an API token . Tokens are scoped per workspace (or per agency, on agency plans). If you’re not sure whether your plan includes API access, reach out to your Customer Success Manager.

A quick GraphQL primer

If you’ve only worked with REST APIs before: GraphQL is one endpoint that lets you describe exactly the data you want in each request. You don’t pick a URL per resource; you write a query and the server returns the shape you asked for — no more, no less.

query LatestPosts {
  items(first: 5, sorting: { sortKey: TAKEN_AT, sortOrder: DESC }) {
    nodes {
      id
      caption
      provider
      currentEngagement { likes comments earnedMediaValue }
      socialProfile { accountName followers }
    }
  }
}

The same query as a POST body:

{ "query": "query { items(first: 5, sorting: { sortKey: TAKEN_AT, sortOrder: DESC }) { nodes { id caption provider currentEngagement { likes comments earnedMediaValue } socialProfile { accountName followers } } } }" }

You don’t have to write queries by hand. Drop the API System Prompt into a Claude Project (or any GraphQL-aware AI assistant) and ask in plain English — Claude will compose, run, and explain the queries for you.

More documentation

The auto-generated GraphQL schema (every field, type, and enum) lives at app.archive.com/api/v2/docs . It reflects engineering changes in real time. The documentation on this site is curated by Support — it adds context, examples, and “Using with AI” recipes on a slower cadence than the schema itself.

Last updated on
Getting Started