Connecting ParcelPanel

Last updated: June 29, 2026

Setting Up the ParcelPanel Integration in Engaige

Prerequisites

Access to your Engaige dashboard (Admin role)
A ParcelPanel account with API v2 access (Shopify)
For extra info or endpoints, you can refer to the ParcelPanel API v2 docs.

Part 1 — Get Your ParcelPanel API Key

Log in to your ParcelPanel (Shopify) admin.
Navigate to Settings → API & Webhooks.
Copy your API key. Keep it private — it authenticates every request and should only ever be used server-side.

Note: ParcelPanel allows 120 requests per minute per API key. Requests beyond that limit return a 429 and are retried with backoff.

Part 2 — Create the HTTP Integration in Engaige

In your Engaige dashboard, go to Integrations → HTTP
Click Create Integration and fill in the following:

Field	Value
Integration Name	`ParcelPanel` (or any name you prefer)
Domain	`open.parcelwill.com`
Authentication Method	`API Key`
Authorization Header	`x-parcelpanel-api-key`
API Key	(paste your ParcelPanel API key from Part 1)

Note: Enter the Domain as the host only — no https://, no trailing slash, and no path. ParcelPanel expects the key in the custom x-parcelpanel-api-key header, so the Authorization Header must be set to exactly that — not the default Authorization. Paste the key as-is, with no Bearer prefix.

Save the integration. Note the Integration ID — you'll need it in Part 3.

Part 3 — Create the HTTP Action

Action — Get Order Tracking

Field	Value
Action Name	`Get Order Tracking`
Integration	Select the `ParcelPanel` integration created above
HTTP Method	`GET`
Path	`api/v2/tracking/order?order_number=#{order_number}`

The #{...} syntax is Engaige's template substitution. At runtime, replace #{order_number} with the variable that holds the order number in your workflow (e.g. #1034) and it will be injected automatically. You can look up an order by either order_number or order_id — to use the order ID instead, set the path to api/v2/tracking/order?order_id=#{order_id}. At least one of the two is required.

Part 4 — Test the Integration

Once the action is saved, trigger a test run with a real order number to verify connectivity. A successful call returns 200 OK with the order's shipment, carrier, status, and checkpoint data.

Troubleshooting common responses:

Status	Meaning & fix
`401`	Wrong or expired API key. Double-check the API Key and that the Authorization Header is set to exactly `x-parcelpanel-api-key`.
`404`	The order doesn't exist in ParcelPanel. Verify the order number / order ID.
`400` / `422`	Missing or malformed query parameter. Supply a valid `order_number` or `order_id`.
`429`	Rate limit exceeded — ParcelPanel allows 120 requests/minute per key.

Key Response Fields (for action output mapping)

The tracking response includes the order, shipment, carrier, and checkpoint history. The most useful fields for an agent are typically:

Field	Description
`status` / `status_label`	Machine status and human-readable label (e.g. "In Transit", "Delivered")
`substatus` / `substatus_label`	More granular status detail
`tracking_number`	Carrier tracking number
Carrier name / tracking URL	Carrier identity and the link the customer can follow
Estimated / actual delivery date	Expected or confirmed delivery date
Checkpoints array	Historical status updates with timestamps

For the complete response schema and exact field paths, see the ParcelPanel API v2 docs.

That's it! Once both steps are complete, your Engaige agent will be able to look up live order & shipment tracking information via ParcelPanel.