Pre-generate AWB numbers ahead of order creation.
Generate AWBs (pool replenishment)
Requests a batch of AWBs, topped up from your existing unused pool.
If you already have enough unused AWBs sitting idle, this can return those instead of minting new ones — it only generates fresh numbers when your unused pool is below the requested count.
See AWB Generation for when to use this vs. the always-fresh endpoint.
Generate AWBs (pool replenishment) › Request Body optional
countNumber of AWBs to request. Defaults to 10, max 100,000.
Generate AWBs (pool replenishment) › Responses
AWBs returned
messageawb_numbersRequest fresh AWBs (async)
Requests AWBs that are guaranteed newly minted, regardless of how many unused ones you already have.
Asynchronous — submit a request here, then poll GET /v1/clients/awb/{request_id}/ for the result.
See AWB Generation for when to use this vs. pool replenishment.
Request fresh AWBs (async) › Request Body
awb_countNumber of AWBs to request. Defaults to 1000, max 100,000.
request_typeRequest fresh AWBs (async) › Responses
Request accepted
statusrequest_idmessagedelay_timeSeconds to wait before polling for the result. Scales with request size and queue depth.
Poll for fresh AWB result
Poll for the result of a fresh-AWB request submitted via POST /v1/clients/awb/. While the batch is still generating, returns status: PENDING with retry_flag: true — wait and poll again.
path Parameters
request_idPoll for fresh AWB result › Responses
Request status and AWBs if ready
awb_numbersstatusretry_flagTrue if the batch is still generating and you should poll again.