Skip to main content
The Queue API at /Queues/{queueName} provides authenticated FIFO queues with content decoding/encoding and delayed responses.

​
Methods

​
Authorization

The account needs:
For example:
Supported authentication includes mTLS, JWT bearer, and configured HTTP authentication schemes. HTTPS with at least 128-bit security is required when encryption is enabled.

​
Enqueue

The server first decodes the request by Content-Type, then serializes the resulting object for the queue. Expect 415 for an unsupported type and 422 when the decoded object cannot be serialized.

​
Dequeue or peek

Use Peek=1 to read without removal. Use Count=N for a batch; batches are returned as multipart/mixed, even when N=1. MinTimeout waits briefly for the remainder after the first item arrives. Use HTTP/2 so many delayed dequeue requests can share a connection efficiently.

​
Consumer design

Dequeue removes the item, so persist the business result before considering processing complete. Use an application idempotency key because a caller can fail after the server dequeues but before the caller records success.