SimpleQ

Appearance

SimpleQQueues-as-a-Service

A reliable webhook-delivery API for async work.

Examples
Concepts

Ack mode

Acknowledge the webhook immediately, run the real work out of band, report the outcome back with ack / nack / defer.

Backpressure

Relay a downstream 429 / 503 / 529 to defer the job. Deferred jobs are held and redelivered without burning an attempt.

Idempotency

Dedupe publishes with idempotencyKey. On redelivery your worker dedupes to avoid double-spending tokens.

What is SimpleQ? ​

A queues-as-a-service API. You POST a job to SimpleQ; SimpleQ queues it and POSTs it to your webhook with retries, backoff, a dead-letter queue, and rate-aware redelivery handled for you.

How it works ​

  1. Publish — POST a job to /v1/queues/<queue-name>/jobs.
  2. Deliver — SimpleQ POSTs the job to the webhook URL you configured on the queue.
  3. Acknowledge — Your webhook returns 2xx. The job is done.
  4. (Ack mode) — Or, for work that exceeds the 15-second webhook ceiling, return 2xx immediately and have your worker report back later with /ack, /nack, or /defer.

Publish a job ​

bash
curl -X POST $SQ_API_URL/v1/queues/my-queue/jobs \
  -H "Authorization: Bearer $SQ_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "payload": { "task": "hello" },
    "idempotencyKey": "task-001"
  }'

Request body:

  • payload (object, required) — your job data, delivered verbatim to your webhook.
  • idempotencyKey (string, optional) — dedupes the publish; a second POST with the same key returns the existing job.
  • delay (number, optional) — seconds to defer the first delivery (max 86400).

Auth: every request uses Authorization: Bearer sq_live_.... Get a key from the dashboard under API Keys.

Where to go ​

  • Examples — task-oriented integration examples for common downstreams.
  • Concepts — the load-bearing ideas: ack mode, backpressure, idempotency, signature verification.
  • API reference — every endpoint, body, and status code.