Roadmap
Have an idea for the API? We’d love to hear it.
If there’s a query, mutation, filter, or capability you’d like to see added to the Archive API, submit a feature request through our feedback portal:
Your feedback directly influences our API roadmap. The more detail you can share about your use case, the better we can prioritize and build what matters most.
Coming soon
What we’re actively working on next.
| Feature | What it is |
|---|---|
| Outbound webhooks | Push events to customer-owned endpoints when new content lands in your workspace or when engagement snapshots refresh — item.captured and item.engagement_updated for v1, with HMAC-signed payloads, idempotency keys, and at-least-once delivery. Replaces the daily polling loop most integrations build today. |
| Preset expansion | Rounding out preset support: filterPresets returning Social Profile and Creator views (today it only returns Content Views and Collections), and socialProfiles(presetId:) applying a view’s filters blob on read. To be precise about where this stands today: a Social Profile View’s customAttributeConditions are applied correctly (labels, post date, and other CRM conditions — including the timezone stored on the view), but its filters blob is still ignored, so a view that narrows by followersCount or verified returns every profile in the workspace. There’s no inline workaround for those two — SocialProfileFilterInput only accepts platform. |
Recently shipped
Improvements that were on the request list and are now live. If you’d asked for any of these, they’re ready to use today.
| Date | Feature | What changed |
|---|---|---|
| 2026-07-20 | Collections can be grouped via API | New moveCollectionToGroup(collectionId: ID!, groupId: ID) mutation, plus a matching MCP tool — the API equivalent of the UI’s right-click Add Collection to Group. Previously only Content / Social Profile / Creator Views could be grouped from code; Collections were UI-only. Two read fields came with it so you can verify a move: Collection.group and ViewGroup.collections. This brings the connector to 24 write tools. See Content Views → Move something into a group. |
| 2026-07-19 | MCP write actions | The MCP server can now write, not just read — 23 write/delete tools alongside the 28 read tools. Collections (create/update/delete + add/remove items), Content / Social Profile / Creator Views (create/update/delete), view groups (create/update/delete, move, reorder), and item actions (uploadItemFromUrl, refetchEngagementBulk). Every write is gated behind a per-call approval in the AI client, and deletes only remove the saved view/collection/group — never the underlying content. See MCP Server. |
| 2026-07-15 | Creator Views via API | Creator Views — the saved filters under Creators → Views in the Social Listening sidebar — are now fully manageable from code, completing the view-management surface. The creatorViews query returns every view, and createCreatorView / updateCreatorView / deleteCreatorView cover the write side; read a view’s creators with creators(presetId:). One quirk to know: a Creator View narrows by its customAttributeConditions, not by a free-form filters blob (the filters field is stored but not applied on read). See Creators → Creator Views. |
| 2026-07-13 | Views & collections readable everywhere | New dedicated read queries: collections (list collections without accessor filtering), viewGroups (sidebar groups), and socialProfiles (page through every social profile in the workspace with totalCount + cursor pagination). The MCP server also gained seven read tools to match: getCollections, getCollection, getCreatorViews, getCreatorView, getSocialProfileView, getViewGroups, getViewGroup — 28 tools total. See Collections, Social Profiles, and Content Views → View groups. |
| 2026-07-10 | Create and manage views via API | Content Views and Social Profile Views are now fully manageable from code. New queries contentViews and socialProfileViews return every view with its full filter definition, and new mutations createContentView / updateContentView / deleteContentView and createSocialProfileView / updateSocialProfileView / deleteSocialProfileView cover the write side. Filter inputs match the ones you already use for reading, so an existing search can be saved as a view in one call — and updates are partial (omitted fields keep their values). See Content Views and Social Profiles → Social Profile Views. |
| 2026-06-30 | MCP Server | Archive now ships a native Model Context Protocol server — connect Claude, ChatGPT, Cursor, Claude Code, VS Code, Windsurf, Cline, and other compatible clients directly to your workspace without writing GraphQL by hand. Two ways to connect: a one-click browser sign-in (recommended, no API token to copy) and a config-file path that bridges via mcp-remote for desktop clients. See Connecting an Agent. |
| 2026-06-15 | TikTok Stories via API | TikTok Stories are now captured alongside Instagram Stories and queryable via the items query. Use the new TIKTOK_STORY filter on itemTypes to scope to TikTok Stories specifically. On the response side, both Instagram Stories and TikTok Stories come back as type: "STORY" — disambiguate by provider. See Items. |
| 2026-06-15 | Competitor Brands via API | New competitorBrands and competitorBrand queries list the competitors tracked on your workspace, competitorBrandItems(brandId: ID!) returns the content captured for each one (with the full engagement payload), and mediaContents now accepts competitorBrandItemIds so you can pull media files for competitor content the same way you do for your own UGC. Available on plans that include Competitor Insights. See Competitor Brands. |
| 2026-05-20 | Campaigns via API | New campaigns query lists your workspace’s campaigns, and a new campaignsIds filter on items lets you pull the content inside any campaign. |
| 2026-05-20 | API Key Self-Service | Customers can now generate, rotate, and disable their own API tokens directly from Settings → API — no more waiting on Support or your CSM. Agency plans get one token covering every workspace in the org. See Getting Started and Generating an API token . |
| 2026-05-18 | Public Archive URLs on items | Every item now exposes an archivePublicUrl field — a shareable link to the item inside Archive. Works for every item type, including Stories and any other content without a permanent originalUrl. Available across all workspaces and plan tiers. See Items → All available item fields. |
| 2026-05-08 | Import a post by URL | New uploadItemFromUrl mutation — the API equivalent of “Add UGC by Link” in the UI. Pass an Instagram / TikTok / YouTube URL and the post gets imported into your workspace asynchronously. See Items → Add an item from a URL. |
| 2026-04-23 | Bulk engagement refresh | A new refetchEngagementBulk mutation lets you force a fresh pull of engagement metrics for a set of items, and track progress via the operation query. Useful for time-sensitive reporting workflows where Archive’s natural polling cadence isn’t fresh enough. Requires a feature flag — talk to your CSM if you need it. See Operations. |
What’s already been requested
These API-related requests are already on our feedback board. Vote for them if they match your needs — statuses below were last checked 2026-07-28.
| Feature | Status | Description |
|---|---|---|
| Creator Search via API with Filters | In Review | Programmatic creator discovery — search Archive’s full creator index by tag, keyword, and follower count range, instead of only the creators already saved in the workspace |
| Creator Mutations via API for Labels and Collaboration Status | In Review | Write labels and collaboration_status on creators via the API to sync from external CRMs (e.g. nightly “Do Not Contact” / “Contacted” / “Ambassador” flags). Today creator metadata can only be edited in the Archive UI |
| Outbound Webhooks for Push-Based Event Streaming | Planned | Push events to customer-owned endpoints (e.g. item.captured, item.engagement_updated) instead of requiring polling — lets integrations react in near-realtime and cuts request volume on both sides. Now in Coming soon above |
| Expose Creator Audience Insights via API and CRM Integrations | In Review | Once a creator’s audience data has been enriched in Creator Search, expose the demographic and audience-insight fields via the public API and CRM integrations — today those fields are only available in the Creator Search UI and the Creator modal inside Campaigns |
| Bulk label + social-profile upload/management via API | In Review | Expose the UI’s bulk-upload template through the API — create, update, and remove labels on existing content and creators, and bulk-import new social profiles with labels attached, in a single call. Today this is UI-only, so agencies automating client reporting still have a manual step every cycle |
| Generate Post Summaries via the API | In Review | An API endpoint to trigger post summary generation programmatically. Today summaries are read-only via the API — there’s no way to initiate generation in bulk, so backfills still depend on the UI |
| Add Creators or Items to a Campaign via the API | In Review | Programmatic endpoint to add creators or items to an existing campaign. The campaigns surface in the API is read-only today — you can list campaigns and pull the content already inside, but pushing new creators or items into a campaign still requires the Archive UI |
| Competitive Insights API Export for Share of Voice Measurement | In Review | Aggregate competitive benchmarking metrics (Share of Voice and similar rollups) via the API. Partly addressed by Competitor Brands, shipped 2026-06-15 — you can now pull each tracked competitor’s captured content and engagement, but the dashboard’s aggregate Share-of-Voice figures are still UI-only |
Last updated on