Download a QR code with JSON options

Méthode POST {API_BASE}/v2.1/client/{key}/{crid}/qrcode

Same behavior as GET, with color and size options accepted in the JSON body for legacy clients.

Autorisation

Scope requis client_v2

The API key is intentionally kept in the path for V2 compatibility: /v2.1/client/{key}/{crid}/... or /v2.1/user/{key}/{crid}/.... Client routes require the client_v2 scope. User routes require the user_v2 scope. Unknown, expired, revoked, malformed, or wrong-scope keys return the legacy JSON error envelope.

Paramètres

Nom	Emplacement	Type	Requis	Contraintes	Description
`key`	Chemin	`string`	Requis		API key kept in the URL for V2 compatibility. Requires `client_v2` or `user_v2` depending on the route.
`crid`	Chemin	`string`	Requis		Client reference ID, usually an order or campaign reference.

Corps de la requête

Facultatif application/json Schéma QRCodeOptions

Nom	Type	Requis	Description
`dark`	`string`	Facultatif
`light`	`string`	Facultatif
`extension`	`string`	Facultatif	Filename extension hint only; image body remains PNG. Par défaut `png`
`size`	`integer`	Facultatif	Par défaut `256` Contraintes min 64

Réponses

200 image/png

PNG QR code image.

400 application/json Schéma LegacyError

Invalid key, CRID, payload, message state or business precondition.

403 application/json Schéma LegacyError

Key is authenticated but scope or platform constraints are invalid.

json 403

{
  "status": 1,
  "error": "forbidden"
}

forbidden

json 403

{
  "status": 1,
  "error": "forbidden"
}

invalidPlatformConstraint

json 403

{
  "status": 1,
  "error": "key_invalid"
}

503 application/json Schéma LegacyError

API key backend is temporarily unavailable.

json 503

{
  "status": 1,
  "error": "auth_unavailable"
}