Connecting 17Track

Setting Up the 17Track Integration in Engaige

Part 1 — Get Your 17Track API Key

1. Log in to your 17Track account at 17track.net

2. Navigate to Settings → Security → Access Key

3. Copy your API key (referred to as your 17token)

Note: The free plan includes 100 tracking lookups/month. For production use, purchase a quota plan at admin.17track.net.

Part 2 — Create the HTTP Integration in Engaige

1. In your Engaige dashboard, go to Integrations → HTTP

2. Click Create Integration and fill in the following:

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

Part 3 — Create the HTTP Action

You can create one or both of the following actions depending on your use case.

Action A — Track a Shipment (get current tracking info)

Body Template:

{    "number": "#{tracking_number}"  }

Upon testing in the Test tab, replace #{tracking_number} with the variable that holds the shipment's tracking number in your workflow. The #{...} syntax is Engaige's template substitution. At runtime, the value will be injected automatically.

Action B — Register a Tracking Number (start tracking a new shipment)

Body Template:

{    "number": "#{tracking_number}",    "tag": "#{order_id}",    "auto_detection": true  }

Part 4 — Test the Integration

Once the action is saved, trigger a test run with a real tracking number to verify connectivity. A successful response looks like:

{  "code": 0,  "data": {    "accepted": [{ "number": "RR123456789CN", ... }],    "rejected": []  }}

If you receive a 401, double-check that the Authorization Header is set to exactly 17token and the API key is correct. If you receive a 429, you have exceeded the rate limit of 3 requests/second.

Key Response Fields (for action output mapping)

When reading the response from gettrackinfo, the most useful fields are:

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