Archive Partners API

The Archive Partners API gives you programmatic access to your Archive workspace — enabling you to build custom integrations, automate reporting workflows, and pull data into your own tools and systems.

With the API you can query creators and their attributes, search and filter archived content (UGC), retrieve historical engagement metrics, access Content Views and manage collections, and look up social profiles by handle or URL. All data is the same as what you see in the Archive UI, accessible via a single GraphQL endpoint.

The API is designed for teams who want to go beyond the Archive UI — whether that’s syncing data into Google Sheets or Airtable, building automated performance reports, integrating Archive data into a CRM, or running custom analysis on your creator and content data.

All requests are made via a single GraphQL endpoint:


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

Looking for a purely technical reference? The auto-generated GraphQL schema lives at app.archive.com/api . It reflects the API in real time as soon as engineering ships changes. This documentation is curated by the Support team — it adds context, examples, and “Using with AI” recipes, but is updated on a slower cadence than the schema itself.

About GraphQL

The Archive API uses GraphQL — a query language for APIs that works differently from the more commonly known REST APIs.

The key difference: With REST, each resource has its own URL (e.g. /creators, /items, /collections) and you get back a fixed set of fields. With GraphQL, there is a single endpoint and you describe exactly what data you want in each request — no more, no less.

Why this matters for you:

You decide which fields come back. If you only need id and full_name, you ask for just those — no wasted data.
You can fetch nested data in one request. For example, a single query can return creators along with their social profiles and engagement metrics.
You can request multiple things at once, or paginate through large datasets with precise control.

Basic notation:


query QueryName {
  queryField(parameter: value) {
    fieldYouWant
    anotherField
    nestedObject {
      nestedField
    }
  }
}

All requests are POST with a JSON body containing a query field:


{
  "query": "query { creators(first: 20) { nodes { id customAttributes } } }"
}

If you’re used to REST APIs, think of GraphQL as a single flexible endpoint where you control the shape of the response. If you’re using Claude with the API System Prompt, you don’t need to write queries manually — just ask in plain language.

Documentation

Setup


Getting Started	Authentication via an API client or Claude, and how to set up your environment
Workspaces	Discover your workspaces and configure your workspace ID
Pagination	How to navigate through large result sets — explained step by step

Querying your data


Creators	Query creators by name, email, or attributes
Social Profiles	Look up social accounts by handle, ID, or fetch fresh platform data
Custom Attributes	Discover and filter by custom fields on creators and items
Items (UGC)	Search, filter, and sort archived content — posts, reels, stories, and videos
Content Views	Access your saved content views from Social Listening
Collections	Manage collections — add and remove items
Operations	Trigger bulk engagement refresh and track background operations (requires feature flag)

Reference


Glossary: UI to API	Map what you see in the Archive UI to the corresponding API fields and queries
Common Workflows	Real-world examples combining multiple queries and mutations
Error Handling	Common errors, what causes them, and how to fix them
Feature Requests	Submit ideas for new API capabilities

API access is available on select plans. If you’re not sure whether your plan includes API access, reach out to your Customer Success Manager. If you know you have access and need your API token, contact support@archive.com or use the in-app chat.