17TRACK connector
Your Silux Chat bot answers “where’s my parcel?” from 17TRACK: the customer gives their tracking number and gets the live status and courier — no verification needed, nothing personal shown.
Good to know: courier is 17TRACK's numeric carrier code.
What your bot can do with 17TRACK
Delivery and tracking
Looks a parcel up in 17TRACK by the tracking number the customer gives and answers with its status and courier — no verification needed, and nothing personal is returned. Looking an order up by its order number needs the customer to be verified first.
Customers ask: “What’s my tracking number?” · “Has my parcel been delivered?”
Answered by the bot’s Track My Parcel tool: by tracking number for anyone (status and courier only), by order number only for a verified customer and only for their own order.
Set it up
Most businesses finish in under ten minutes. You need to be able to sign in to 17TRACK as an administrator to create the key.
Step 1 — in 17TRACK
- 117TRACK API console
- 2Settings
- 3Security
- 4copy the key. Numbers must be registered with 17TRACK (your store or a register call) before they can be read.
Least access: grant only the read permissions named above (customers, orders, invoices, bookings or tickets — whichever this connector uses). Never use an owner or full-admin key where 17TRACK lets you create a restricted one.
Step 2 — in Silux Chat
- 1Open Dashboard → Integrations → Connectors and search for “17TRACK”.
- 2Fill in:
Field Example Stored Security key (17token) •••••••• Encrypted - 3Press Connect & test. The platform makes a real, read-only call to 17TRACK with a made-up customer and shows a tick or a cross for each capability, with 17TRACK’s exact error if something is refused.
- 4If your bot has no parcel tracking yet, Track My Parcel is switched on automatically when the tracking test passes; otherwise press Use for tracking to make 17TRACK the one your bot uses.
You create an API key in 17TRACK and paste it into your dashboard. It is sent in a request header on every call, over HTTPS only.
How customer verification works
Tracking needs no verification. A customer who gives their own tracking number hears only the parcel’s status and courier — the same thing 17TRACK’s public tracking page shows — and only when 17TRACK holds a parcel with exactly that number. Looking up an order by its order number needs the customer to be verified first.
17TRACK holds no customer records that the platform can match by name and email, so this connector cannot verify customers by itself. It is tested when you connect it and re-checked every day. To plan how its data should reach your customers alongside your verification route — a connector that can look customers up, or your own Account Connect endpoints — email support@siluxcall.co.uk.
What the bot can and cannot see
Can see (after verification)
No customer records — tracking only.
Tracking, without verification: order number, status, tracking number and courier — only for the tracking number the customer gave.
Only these standard fields are mapped from 17TRACK’s responses. Everything else in the response is discarded before the bot sees it.
Never sees
- passwords, security answers or login details
- records belonging to anyone other than the verified customer
- anything outside the fields listed alongside
Security
Keys encrypted at rest
Credentials are stored encrypted, shown only masked after saving, and destroyed — not just hidden — when you disconnect.
Read-only look-ups
Every capability is a look-up. The connector cannot create, change or delete anything in 17TRACK.
HTTPS only
Calls go to the vendor’s HTTPS address, redirects are not followed, and private network addresses are refused.
Injection-safe
Values a customer types are cleaned before they are placed in 17TRACK’s search, and URL-encoded in addresses.
Other customers filtered out
A row that names a different customer’s email is dropped, whatever the vendor’s search returned.
Checked daily
Connections are re-tested every day, and the owner is emailed if a working connection starts failing.
More: Security & data protection.
Technical details
For developers and IT teams: the 17TRACK endpoints this connector reads, relative to https://api.17track.net/track/v2.2. Values in braces come from the settings you enter.
| Capability | Request | Standard fields returned |
|---|---|---|
| Delivery and tracking | POST/gettrackinfo | order_number, status, sub_status, detail, tracking, courier |
Test level: Documented-API tested. Each capability is run automatically against 17TRACK’s documented example responses and must produce the standard fields; your own connection is then tested with a real call when you connect. The bot receives these through the standard Account Connect endpoints, exactly as if you had built them yourself.
Troubleshooting
| What you see | Likely cause and fix |
|---|---|
| “the vendor refused the credentials (401)” or (403) | The key was revoked, has expired or was copied incompletely, or it lacks a read permission this connector needs. Create a fresh read-only key in 17TRACK and reconnect. |
| Customers are “not matched” although they exist | Customers are looked up by email or mobile, not postcode. Check the customer’s email or mobile is saved on their 17TRACK record, and that the surname matches. |
| A capability shows a cross but others work | That permission wasn’t granted in 17TRACK, or your 17TRACK plan doesn’t include that part of the API. Grant it and press Test. |
| “the vendor kept rate-limiting the request” | 17TRACK returned “too many requests” three times in a row. The platform already waits and retries automatically (up to 10 seconds, as 17TRACK asks); if it persists, ask 17TRACK about your API quota. |
| Results are empty for a verified customer | The records exist under a different email or customer record in 17TRACK, or none are recent. Check the customer’s record in 17TRACK directly. |
Full error reference: Troubleshooting & error reference.
Frequently asked questions
Is the 17TRACK connection read-only?
Yes. Every request Silux Chat makes to 17TRACK is a look-up (a few vendors use POST for searches); none creates, changes or deletes anything in 17TRACK. Give the key or sign-in read-only permissions wherever 17TRACK offers them.
Do I need a developer to connect 17TRACK?
No. You paste the details listed in the set-up steps in Dashboard → Integrations → Connectors and press “Connect & test”. The platform makes a real call to 17TRACK straight away and shows exactly which features work.
How does the bot know it is really my customer?
For tracking it doesn’t need to: the customer gives their own tracking number and hears only the status and courier. 17TRACK can’t verify customers by itself, so looking an order up by its order number needs verification through another connector or your own Account Connect endpoints.
What happens if my 17TRACK key is revoked or expires?
The bot tells customers it can’t check their account right now — it never pretends there are “no orders”. Connections are re-tested daily and the account owner is emailed when a working connection starts failing. Reconnect it in Dashboard → Integrations → Connectors.
How has the 17TRACK connector been tested?
It is Documented-API tested: every capability is run automatically against 17TRACK’s documented example responses and must produce the standard fields. When you connect, it is tested again with a real call to your own 17TRACK account before your bot uses it.
Other shipping & tracking connectors
AfterShip
Delivery and tracking · Orders and order status
DHL (Shipment Tracking – Unified)
Delivery and tracking
EasyPost
Delivery and tracking
FedEx Tracking
Delivery and tracking
Parcel2Go
Delivery and tracking
Printful
Delivery and tracking · Orders and order status
Royal Mail Click & Drop
Delivery and tracking
ShipBob
Delivery and tracking
Shippo
Delivery and tracking
Need help with your integration?
Our integration team can review your endpoints, help you choose the right connector and check a test run with you. Tell us which system you use and what you would like the bot to answer.