API reference
API explorer
Pick an endpoint, fill in its parameters and see the exact request in cURL, JavaScript and Python. With your own API key you can also send it and read the real response.
Requests here are live
QRBold has no sandbox. A request you send from this page acts on the real account your key belongs to: a POST creates a real card or code, a DELETE removes one. Nothing is sent until you press Send.
POST/campaigns/CAMPAIGN_ID/cards
Creates one card from a single record, using the campaign’s template, mapping and short-link rule. Needs the cards:write scope.
One JSON object, up to 1 MB, creates one card. In mapped mode it is your own record, unchanged. In native mode it is a card document whose top-level externalId is required. Do not send templateId: the campaign owns it.
The code for this request
Updates as you type. It reads the key from an environment variable; the key you paste below is never put into it.
curl -X POST "https://api.qrbold.com/api/public/v1/campaigns/CAMPAIGN_ID/cards" \
-H "Authorization: Bearer $QRBOLD_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"employee": {
"id": "EMP-1001",
"name": {
"first": "Ada",
"last": "Lovelace"
},
"contact": {
"email": "ada@example.com",
"mobile": "+44 20 7946 0958"
}
}
}'Send it from this browser
Kept in this page’s memory only, and sent only to the QRBold API in the Authorization header. It is not stored, not logged and not sent to any other server. Reloading the page clears it. Use a key with only the scopes you need, and revoke it afterwards if you created it for testing.
Paste an API key to send the request.
You do not need a key to use the explorer as a request builder. If you would rather work in a dedicated tool, download the Postman collection. New here? Start with the quickstart.