- Documentation
- API · Version 1.0
- Introduction
Introduction
On this page
The Quiet Social REST API lets your application publish to a brand's networks without going through the dashboard: an article going live, a product launch or a newly created event becomes a publication, scheduled or immediate, on Facebook, Instagram, LinkedIn, Threads and Pinterest.
Nothing here requires a library. To avoid writing the calls yourself, the PHP SDK makes them for any PHP application, and the Laravel package publishes your Eloquent models; everything they do goes through this API.
Base URL
https://quietsocial.dev/api/v1
The version is in the path. A URL therefore carries its version: an example copied from this documentation stays valid, and a version 2 will live alongside version 1, not in its place.
Format
- Request and response bodies are JSON, except file uploads, which use
multipart/form-data. - Every response under
/api/is rendered as JSON, errors included. TheAccept: application/jsonheader is recommended, not required. - Dates use the ISO 8601 format, with their offset:
2026-10-01T09:30:00+00:00. - Resources are identified by a prefixed public identifier —
pub_…,dst_…— never by a number. See Limits and conventions.
First call
Create a key in the dashboard, menu Clés API (API keys) (see Authentication), then ask the API who you are:
curl https://quietsocial.dev/api/v1/me \
-u "$QUIET_CLIENT_ID:$QUIET_CLIENT_SECRET"
The response tells you which workspace and which brand this client acts on, and which scopes it has. It is the first call of any integration: it saves you from discovering your missing permissions one refusal at a time.
Typical flow
- List the brand's destinations with
GET /destinations, to learn their identifiers and what each one accepts. - Upload the image, if any, with
POST /media. - Create the publication with
POST /publications, giving it an idempotency key. - Get notified of the outcome, network by network, through a webhook — or read the publication again with
GET /publications/{id}.
The pages of this reference
- Authentication: credentials, secret,
GET /me. - Scopes: what each permission opens, and a client's brand.
- Idempotency: replay a write without publishing twice.
- Brands and destinations: where you can publish, and what.
- Publications: create, read, release, cancel, retry.
- Media: upload and manage images.
- Webhooks: get notified, and verify the signature.
- Errors: every code, and whether to retry.
- Limits and conventions: rate, pagination, identifiers.
- MCP server: connect an assistant to the API, with the same key.