01API keys
API keys go in the Authorization: Bearer header. A key sent in the query string is refused, because by then it is already sitting in a log somewhere — the API answers 400 key_in_query without acting on it.
Keys are scoped and revocable. You create them in the console under Settings → Developers, where each key is shown once and can be given only the scopes it needs (renders:write, renders:read, backgrounds:read). If a key leaks, revoke it there and make a new one. See the API reference.
02Signed webhooks
Webhook deliveries are signed in the X-Spin-Signature header with HMAC-SHA256 over the timestamp and the raw request body. A webhook_url given on a single request is signed with your account's webhook secret only once you have registered a webhook under Settings → Developers. Until then it arrives unsigned, so register one before you rely on the signature. Verify the signature with your webhook secret before you trust a delivery, so a forged call cannot stand in for ours.
03Account isolation
Your work is visible only to your account. A render, spin or vehicle that belongs to another account answers 404 — the same reply as something that does not exist — so one account cannot even confirm another's work is there.
04Idempotent requests
Send an Idempotency-Key with POST /renders, /spins or /merchandise/process and a retry with the same value from the same key gets the first answer back instead of a second render. The record is kept for up to 24 hours, though a restart of our service can clear it sooner.
05Your photos and data
- Not used for training. Your photographs and renders are yours and are not used to train any model.
- Deletion is real. Deleting a vehicle deletes its finished photos, spin and tour. To remove an account, see data deletion.
- No card numbers. Payments run through our payment processor; Autorestage never receives or stores full card numbers.
- Global Privacy Control is honored. If your browser sends a GPC signal, we treat it as an opt-out. More in the Privacy Policy.
06What this page does not cover
This page states only what is built and verifiable today. We do not make claims here about hosting, encryption at rest or backups; when we can describe them precisely, they will be added. For how we handle personal information, see the Privacy Policy.