Erreurs & Réponses

Guide d'intégration application mobile

Codes de statut HTTP

200	OK - requête réussie.
204	No Content - returned for `OPTIONS` preflight requests (CORS).
400	Bad Request - paramètre manquant ou invalide.
401	Unauthorized - token manquant ou invalide.
404	Not Found - endpoint ou ressource inexistant.
405	Method Not Allowed - mauvaise méthode HTTP pour cet endpoint.

Schéma de réponse succès

JSON

{
  "success": true,
  "...": "endpoint-specific fields"
}

Schéma de réponse erreur

JSON

{
  "success": false,
  "message": "Human-readable error description"
}

CORS

All API responses include the following headers, so the API can be called from web clients:

HTTP

Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, OPTIONS
Access-Control-Allow-Headers: Authorization, Content-Type, X-API-Token

Browsers send a preflight OPTIONS request before a cross-origin POST. The API responds with 204 No Content and the CORS headers above - no body required.