Skip to content
Quiet Social

Limits and conventions

This documentation is translated from French. Should the two versions differ, the French version prevails.

What the API limits, and the conventions it follows on all its routes: rate, pagination, identifiers, dates and quotas.

Rate limits

Two limits, which do not measure the same thing:

Limit Default Counts
Per IP address 300 requests per minute All requests, including those that fail authentication.
Per API client 120 requests per minute This client's authenticated requests, whatever address they come from.

The first protects against credential scanning, which belongs to no client; the second, against an integration that runs away.

An authenticated response carries the headers of the client's limit:

Header Meaning
X-RateLimit-Limit The number of requests allowed per minute.
X-RateLimit-Remaining How many remain in the current minute.

Beyond either one, the API responds 429:

{
  "error": {
    "code": "too_many_requests",
    "message": "Too many requests. Retry after the delay given by the Retry-After header."
  }
}

The response then carries Retry-After (in seconds), X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (Unix timestamp of the reset) for the limit reached. Wait for the Retry-After delay before resuming, and watch X-RateLimit-Remaining on successful responses to slow down before being stopped. A request refused by the client's limit is not counted in the workspace's usage.

A webhook's test notification has its own limit: 5 per minute and per endpoint (see Webhooks).

Pagination

GET /destinations, GET /publications and GET /media are paginated. per_page is 25 by default and is bounded between 1 and 100. GET /brands and GET /webhooks return the full list.

The three paginated lists also accept brand_id: a client that covers the whole workspace reads a single brand there. A brand out of the client's scope returns an empty list, without an error.

A paginated response carries three keys: data, links and meta.

{
  "data": ["…"],
  "links": {
    "first": "https://quietsocial.dev/api/v1/publications?page=1",
    "last": "https://quietsocial.dev/api/v1/publications?page=3",
    "prev": null,
    "next": "https://quietsocial.dev/api/v1/publications?page=2"
  },
  "meta": {
    "current_page": 1,
    "from": 1,
    "last_page": 3,
    "links": ["…"],
    "path": "https://quietsocial.dev/api/v1/publications",
    "per_page": 25,
    "to": 25,
    "total": 61
  }
}

Paginate by following links.next until it is null. The request parameters — filters included — are kept in these links. meta.links is for displaying pagination; its labels are not part of the contract.

Identifiers

The API never exposes a sequential number: it could be guessed, and would let someone probe another workspace's resources. Each resource carries a public, prefixed and immutable identifier:

Prefix Resource
qsc_ API client
brd_ Brand
dst_ Destination
pub_ Publication
med_ Media
whe_ Webhook endpoint
whd_ Webhook delivery

After the prefix comes a string of lowercase characters (pub_01k4b8y5t2v9h6p8w0y2z4b6c8). Treat the identifier as an opaque string, and infer nothing from it.

Dates and time zones

Returned dates are in ISO 8601 with their offset, in UTC. Dates you send must follow ISO 8601 and may carry any offset: 2026-10-02T08:00:00+02:00 and 2026-10-02T06:00:00Z designate the same instant. Without an offset, the time is read as UTC; any other form is refused with 422.

timezone (IANA time zone, Europe/Paris) accompanies a publication; it is the brand's by default.

Quotas

A brand can have two monthly caps, readable in GET /brands:

  • monthly_publication_limit — publications created in the month. Beyond it, creation responds 422 publication_not_publishable.
  • monthly_delivery_limit — successful deliveries to a network in the month. It is checked when a held publication is released with publish: 409 transition_not_allowed if the targets to release exceed what remains.

null means "no cap". The counters restart from zero on the first of each month, at midnight UTC.

What the API does not do

  • It creates no connection, destination or brand: that is done in the dashboard.
  • It does not approve a publication submitted for approval; only the team does, in the dashboard.
  • It does not return download URLs for media.