Skip to main content

What You Can Do With the Archive API

A plain-language overview of what the Archive Partners API is for, what data it can return, and what it cannot do.

Written by Anne Buzzi
Updated today

πŸ“‹ Available on: Startup, Growth, Enterprise, Agency, and Custom 2026 plans.

The Archive Partners API gives you programmatic access to the data your workspace has already captured β€” social content, creator profiles, engagement metrics, and CRM-style attributes. It's designed for teams that want to plug Archive data into other tools (spreadsheets, CRMs, internal dashboards) or build custom reporting on top of it.
​

This article explains, in plain language, what the API is for and what you can expect from it. For the full technical reference β€” endpoints, fields, examples, and authentication β€” visit api-docs.archive.com.


What the API Is For

Common use cases:

  • Sync Archive data into other tools β€” pull captured content, creators, and metrics into Google Sheets, Airtable, your CRM, or a data warehouse.

  • Build custom reports and dashboards β€” generate performance dashboards using your own BI stack instead of relying on the Archive UI.

  • Run custom analysis β€” query specific subsets of your data for research, audits, or one-off projects.

  • Manage Collections programmatically β€” add or remove content from Collections in bulk.


What Data Is Available

The API returns data that Archive has already captured for your workspace:

  • Content β€” Instagram Feed posts, Reels, and Stories; TikTok videos; YouTube videos and Shorts. Includes captions, transcriptions, post URLs, and media files.

  • Engagement metrics β€” views, likes, comments, shares, EMV, and virality score, with historical time-series data.

  • Creators and social profiles β€” handles, follower counts, contact details, and verification status across platforms.

  • CRM attributes β€” your custom attributes (Magic Fields, Labels, Collections, etc.) on creators and content.

  • Workspace metadata β€” tracked hashtags, mentions, and saved filter presets.


What the API Cannot Do

The API is primarily read-only. The following are not supported:

  • Creating or deleting content, creators, or social profiles β€” these records are created automatically as Archive captures content. The API can only read them.

  • Sending outreach or messages β€” no messaging or DM functionality.

  • Writing custom attributes β€” you can read and filter by custom attributes, but you cannot set or update them via the API.

  • Creating or modifying workspaces, filter presets, or campaigns.

  • Real-time webhooks or push notifications β€” the API is pull-only.

  • Pulling content that has not yet been captured by Archive.

The only write operations currently available are adding and removing content from Collections and Content Views.


Getting Started

API keys are generated by the Archive team. To request a key, contact Archive Support via the in-app chat with your Workspace ID and a brief description of your use case. For the full technical reference, visit api-docs.archive.com.

Did this answer your question?