How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

PostEx Orders API

Booking, tracking, and listing shipment orders

PostEx Orders API is one of 2 APIs that PostEx publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Order. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 5 operations across 5 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 3.

Requests are made against a single base URL, https://api.postex.pk/services/integration/api/order.

5 operations 5 paths 1 schemas 2 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3
Base URL
https://api.postex.pk/services/integration/api/order
Authentication
API Key
Resource Areas
1

Authentication & Security 1

PostEx Orders API declares 1 security scheme for authenticating requests. An API key is passed in the header as token (merchantToken). By default, every request must be authenticated.

  • merchantToken — Merchant API token issued from the PostEx merchant dashboard, supplied in the token request header on every call.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 2 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Orders 5

Booking, tracking, and listing shipment orders

POST
/v3/create-order
Create an order (v3)
createOrder body → 200400
POST
/v2/create-order
Create an order (v2)
createOrderV2 body → 200400
POST
/v1/create-order
Create an order (v1)
createOrderV1 body → 200400
GET
/v1/track-order/{trackingNumber}
Track an order
trackOrder 1 param → 200400
GET
/v1/get-unbooked-orders
List unbooked orders
getUnbookedOrders → 200400

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Error (5 properties). Each schema is shown below with its type and property counts.

Error
object
PostEx / Spring Boot error envelope returned on failed requests (Content-Type application/json). Not RFC 9457 problem+json.
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

postex-orders-api-openapi.yml Raw ↑

Other APIs PostEx publishes across the network.

PostEx Reference API
Where this information came from

This is an independent, third-party profile of PostEx Orders API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.