Create AWB (Bulk)
POST
/api/pay/v1/orders/{orderId}/awbCreates one or more AWB records for a cross-border order.
Captures AWB number, date, courier name, and tracking URL.
Returns an awb_id for each record which is used in the subsequent file upload step.
Prerequisites:
- Order must exist and be in
PROCESSEDstate. - Merchant must be Cross Border Import enabled.
- Maximum 5 AWB records per request.
- AWB numbers must be unique (no duplicates within the request or existing records for any order).
Requires
Bearer token. Get token →Path Parameters
| Name | Type | Description |
|---|---|---|
orderId | stringrequired | Order ID returned from Create Order API. |
Status Codes
202 | AWB records created successfully. |
400 | Bad Request — Validation error in the request. Possible error codes: - `DOC_INVALID_REQUEST_BODY` — Malformed JSON or cannot parse request body - `DOC_ORDER_ID_MISSING` — orderId path parameter is missing - `DOC_EMPTY_AWB_REQUEST` — Empty array provided - `DOC_AWB_MAX_LIMIT_EXCEEDED` — More than 5 AWB records in a single request - `DOC_AWB_VALIDATION_FAILED` — Field validation failed (missing awb_number, invalid date, etc.) - `DOC_DUPLICATE_AWB_IN_REQUEST` — Duplicate AWB numbers found within the request - `DOC_DUPLICATE_AWB_NUMBER` — AWB number already exists for this order/merchant |
422 | Unprocessable Entity — Order not eligible for AWB creation. Possible error codes: - `ORDER_NOT_FOUND` — The specified order does not exist - `ORDER_IS_NOT_IN_PROCESSED_STATE` — Order is not in PROCESSED state |
500 |
Request
curl --request POST \
--url https://pluraluat.v2.pinepg.in/api/pay/v1/orders/%7BorderId%7D/awb \
--header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
--header 'Content-Type: application/json'Run this request
orderId