DHL (Shipment Tracking – Unified) connector

Your Silux Chat bot answers “where’s my parcel?” from DHL (Shipment Tracking – Unified): the customer gives their tracking number and gets the live status and courier — no verification needed, nothing personal shown.

API key Documented-API tested 1 capability Read-only
Start free Set-up guideDHL (Shipment Tracking – Unified) API docs

Good to know: Default quota is 250 calls a day; ask DHL for more before going live.

What your bot can do with DHL (Shipment Tracking – Unified)

Delivery and tracking

Looks a parcel up in DHL (Shipment Tracking – Unified) 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.

Order numberStatusLast updatedTracking numberCourierService

Set it up

Most businesses finish in under ten minutes. You need to be able to sign in to DHL (Shipment Tracking – Unified) as an administrator to create the key.

Step 1 — in DHL (Shipment Tracking – Unified)

  1. 1developer.dhl.com
  2. 2My Apps
  3. 3Create app
  4. 4add Shipment Tracking – Unified
  5. 5copy the API key.

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 DHL (Shipment Tracking – Unified) lets you create a restricted one.

Step 2 — in Silux Chat

  1. 1Open Dashboard → Integrations → Connectors and search for “DHL (Shipment Tracking – Unified)”.
  2. 2
    Fill in:
    FieldExampleStored
    API key (developer.dhl.com app)••••••••Encrypted
  3. 3Press Connect & test. The platform makes a real, read-only call to DHL (Shipment Tracking – Unified) with a made-up customer and shows a tick or a cross for each capability, with DHL (Shipment Tracking – Unified)’s exact error if something is refused.
  4. 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 DHL (Shipment Tracking – Unified) the one your bot uses.

You create an API key in DHL (Shipment Tracking – Unified) 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 DHL (Shipment Tracking – Unified)’s public tracking page shows — and only when DHL (Shipment Tracking – Unified) holds a parcel with exactly that number. Looking up an order by its order number needs the customer to be verified first.

DHL (Shipment Tracking – Unified) 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 DHL (Shipment Tracking – Unified)’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 DHL (Shipment Tracking – Unified).

    • 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 DHL (Shipment Tracking – Unified)’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 DHL (Shipment Tracking – Unified) endpoints this connector reads, relative to https://api-eu.dhl.com. Values in braces come from the settings you enter.

    CapabilityRequestStandard fields returned
    Delivery and trackingGET/track/shipmentsorder_number, status, updated, tracking, courier, service

    Test level: Documented-API tested. Each capability is run automatically against DHL (Shipment Tracking – Unified)’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 seeLikely 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 DHL (Shipment Tracking – Unified) and reconnect.
    Customers are “not matched” although they existCustomers are looked up by email or mobile, not postcode. Check the customer’s email or mobile is saved on their DHL (Shipment Tracking – Unified) record, and that the surname matches.
    A capability shows a cross but others workThat permission wasn’t granted in DHL (Shipment Tracking – Unified), or your DHL (Shipment Tracking – Unified) plan doesn’t include that part of the API. Grant it and press Test.
    “the vendor kept rate-limiting the request”DHL (Shipment Tracking – Unified) returned “too many requests” three times in a row. The platform already waits and retries automatically (up to 10 seconds, as DHL (Shipment Tracking – Unified) asks); if it persists, ask DHL (Shipment Tracking – Unified) about your API quota.
    Results are empty for a verified customerThe records exist under a different email or customer record in DHL (Shipment Tracking – Unified), or none are recent. Check the customer’s record in DHL (Shipment Tracking – Unified) directly.

    Full error reference: Troubleshooting & error reference.

    Frequently asked questions

    Is the DHL (Shipment Tracking – Unified) connection read-only?

    Yes. Every request Silux Chat makes to DHL (Shipment Tracking – Unified) is a look-up; none creates, changes or deletes anything in DHL (Shipment Tracking – Unified). Give the key or sign-in read-only permissions wherever DHL (Shipment Tracking – Unified) offers them.

    Do I need a developer to connect DHL (Shipment Tracking – Unified)?

    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 DHL (Shipment Tracking – Unified) 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. DHL (Shipment Tracking – Unified) 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 DHL (Shipment Tracking – Unified) 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 DHL (Shipment Tracking – Unified) connector been tested?

    It is Documented-API tested: every capability is run automatically against DHL (Shipment Tracking – Unified)’s documented example responses and must produce the standard fields. When you connect, it is tested again with a real call to your own DHL (Shipment Tracking – Unified) account before your bot uses it.

    Other shipping & tracking connectors

    17TRACK

    Delivery and tracking

    AfterShip

    Delivery and tracking · Orders and order status

    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.

    support@siluxcall.co.uk