---
title: "Connect Archive to Rig | Rig guide"
description: "Generate a workspace-scoped Archive API token, find the workspace ID the API will accept, and sync UGC items, creators, social profiles and campaigns."
canonical: "https://rig.so/guides/connect-archive"
format: markdown
---

Search guides, references, playbooks…⌘K

Browse guides

# Connect Archive to Rig

Sync the UGC your brand gets tagged in, the creators behind it and the campaigns you organised it into. Engagement counts inside Archive keep moving for weeks after a post goes up, so the reason to land this in the warehouse is being able to line those numbers up against the days you actually sold something.

Requirements

An Archive plan that includes API access, and a login that can open `Settings`

Time required

5 mins

## Before you start

API access comes with the Startup, Growth, Enterprise, Agency and Custom plans. It is not available on Free, and it is not available on Archive's legacy plans, so an older contract may need moving across before any of this works. Within an eligible plan you can do the whole thing yourself, with no request form and no approval to wait on.

## Generate an API token

1. Open `Settings`, then `API`, in your Archive workspace.
2. Find the **API Token** card.
3. Click `Generate`.
4. Copy the token and put it somewhere safe before you leave the screen.

You get one look at it
Archive shows the full token once, immediately after it is generated. Come back later and you will only see the last four characters. If you lose it you are not locked out, but the fix is to generate a replacement, and doing that invalidates the old token, so anything else already using it stops working. Tokens themselves do not expire, so this is the only time you have to be careful.

## Find your workspace ID

Tokens are scoped to a workspace, so Rig needs to know which one. If Archive is your only workspace, take the short number from the app URL and paste that. Archive's own API will not accept it, but Rig resolves it to the real identifier for you whenever your token can see exactly one workspace.

If you have more than one workspace, that shortcut cannot work, because the number is ambiguous. You need the workspace UUID instead. Send this query to Archive with your token, which is the one request that does not itself need a workspace ID:

List your workspaces

```
curl -X POST https://app.archive.com/api/v2 \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "query { workspaces(first: 20) { nodes { id name } totalCount } }"
  }'
```

Copy

Each `id` in the response is a workspace UUID. Take the one matching the workspace you want to sync.

## Connect it in Rig

New to Rig? Watch how to find Connections

1. In Rig, open `Connections` and go to `Sources & actions`.
2. Search for **Archive** and open the card. It is listed as **Archive (archive.com)**.
3. **API token**: paste the token you generated.
4. **Workspace ID**: the number from the app URL, or the UUID if you have several workspaces.
5. Click `Test`, then `Sync`.

## What Rig pulls in

Archive lands in its own `archive_io` schema in your warehouse, in seven tables.

- **Items**, the content itself: posts, reels and stories with their caption, platform, when they were taken, hashtags, account mentions, location, transcriptions and live engagement
- **Creators** and **social profiles**, the people behind the content and their handles, follower counts and verification status
- **Campaigns** and the mapping of which items belong to them, plus **collections** and **content views**, which are the saved views your team already built in Archive

Earned media value is in cents
The column is an integer count of cents, not a decimal amount of currency. Divide by a hundred before you put it in a chart, or your EMV will read a hundred times larger than it is.

Rig re-reads the whole workspace on every sync rather than only fetching what is new. That is deliberate: likes, views and earned media value on a post carry on changing for a long time after it was published, so a sync that only looked at recent content would leave last month's numbers frozen at whatever they were the night Rig first saw them.

## Troubleshooting

- **The workspace is rejected and the error lists several names**: your token can see more than one workspace, so the short number cannot be resolved. The error names each workspace with its UUID next to it. Copy the UUID you want and paste that instead.
- **You no longer have the token**: Archive will not show it again. Generate a new one, remembering that the old one stops working the moment you do, then update the connection in Rig.
- **The token is refused outright**: check the plan. API access is not included on Free or on Archive's legacy plans, and a token generated before a downgrade will stop being accepted.
- **Engagement numbers differ from the Archive dashboard**: they are read at different moments. Rig shows you what the last sync saw, and Archive shows you now. On a post published in the last few days the two will keep diverging until the engagement settles.

## What people use this for

- Measure creator and UGC performance
- Quantify earned media value
- Report on campaigns and saved views
- Connect creator content to sales

[More ideas for using Archive](https://rig.so/integrations/archive)

Was this guide helpful?

Yes No

---

- [This page as HTML](https://rig.so/guides/connect-archive)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)