---
title: "Connect parcelLab to Rig — Rig guide"
description: "Connect parcelLab to Rig with an account ID and a read-only API token and sync delivery trackings with carrier, status and delay flags."
canonical: "https://rig.so/guides/connect-parcellab"
format: markdown
---

Search guides, references, playbooks…⌘K

Browse guides

# Connect parcelLab to Rig

parcelLab tracks parcels across carriers after checkout. Rig pulls one row per tracking, with the carrier, last status, order reference and destination, so you can measure delivery performance and join deliveries to orders.

## Before you start

- You need access to the parcelLab app with permission to manage API tokens, or a parcelLab support contact who can create one for you.
- You need your numeric account ID.
- The token must be a plain read token. A token tied to an integration such as Zendesk or Salesforce cannot list trackings.

## Step 1: Create a read-only parcelLab API token

1. Sign in to the parcelLab app and open the API token page in your account settings, or ask parcelLab support to create the token for you.
2. Create a token with the `read` scope only.
3. Copy the token. Use the value exactly as parcelLab shows it.
4. Note your numeric account ID, which sits under Admin and Accounts in the app.

Integration tokens fail
parcelLab rejects a token that carries integration scopes when Rig lists trackings, even if it also has read access. Create a separate plain read token for Rig.

## Step 2: Connect it in Rig

New to Rig? Watch how to find Connections

Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

1. In Rig, open `Connections`, choose the `Connectors` tab and go to `Sources & actions`.
2. Search for **parcelLab**, open the card and click `Connect`.
3. **parcelLab account ID**: Your numeric account ID.
4. **API token**: Paste the read-only token.
5. Click `Continue`. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click `Connect`.
6. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click `Sync` on its row; `Test` pulls a small sample first if you want to check the connection.

## What Rig pulls in

parcelLab lands in its own `parcellab` schema in your warehouse:

- **Trackings**: one row per parcel, with carrier, creation time, last status, order number, recipient country, articles and the delayed, escalated, returned and bounced flags.

Per-parcel checkpoint history is not pulled. The last status and the reporting flags on each tracking carry the delivery picture.

## Good to know

- parcelLab lists trackings newest first and cannot be queried for a closed date range, so each sync reads everything since a start date and merges it by tracking ID.
- After a successful sync, the next one re-reads the most recent days, because tracking statuses keep changing while parcels are in transit.
- Rig builds the authorisation value from your account ID and token, so you enter them in separate fields.
- To disconnect parcelLab, click the bin icon on the source's row under `Sources & actions`. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

## What people use this for

- Measure carriers on what they actually deliver
- Connect delivery experience to repeat purchase
- Anticipate support volume

[More ideas for using parcelLab](https://rig.so/integrations/parcellab)

## parcelLab documentation

- [parcelLab API authentication](https://docs.parcellab.com/docs/developers/getting-started/authentication)

Was this guide helpful?

Yes No

---

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