TekipostAPI
Merchant API

Book a shipment with four calls. Collect the AWB on the fifth.

Base URL https://api.tekipost.com. Every response is JSON. Everything is scoped to your own account by the token you send — no endpoint takes a sender_id, so supplying one changes nothing.

webhook.tekipost.com remains a working alias for every path here. Existing integrations need no change — this host is an addition, not a move.

Quickstart

  1. Which couriers serve the lane, and what each costs.

  2. Create the order. You get an order_id.

  3. Request the booking. Answers 202, not the AWB.

  4. Poll until state is no longer booking_in_progress.

  5. The label PDF.

Start here

Reference

What is not here

The merchant portal also uses endpoints for your profile, staff logins, channel integrations, agreements, outbound webhooks, API keys, analytics, invoices, wallet and communications. Those are portal features: they have no public route and cannot be called from outside our cluster, so documenting them here would describe something you cannot reach.

If your integration needs one, ask — for most it is an ingress path and a decision about the auth model, not a build.