Skip to content
Quiet Social

Introduction

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

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. The Accept: application/json header 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

  1. List the brand's destinations with GET /destinations, to learn their identifiers and what each one accepts.
  2. Upload the image, if any, with POST /media.
  3. Create the publication with POST /publications, giving it an idempotency key.
  4. 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