Guides
Going live
A short checklist to move from sandbox to production safely.
- Your integration runs end to end in the sandbox, including failures (insufficient funds, validation errors, 429s).
- Every campaign creation sends a unique
Idempotency-Keyand reuses it on retries. - You verify webhook signatures on the raw body, reject old timestamps and deduplicate by event id.
- Your webhook endpoint answers in under 10 seconds and does heavy work asynchronously.
- API keys live in a secrets manager on your server, never in front-end code or source control.
- You show customers a price from
POST /v1/quotesbefore creating a campaign. - You handle
429by waiting forRetry-After, and5xxby retrying with backoff and the same Idempotency-Key. - You log the
x-request-idresponse header so support can trace any request. - You have decided how to react to
cancelledand refunds in your own system.
Steps
- Create your live keyLog in to your ByteVerse business account, open Developers and create a live key. It is available straight away.
- Fund your walletLive campaigns spend from the same wallet as your ByteVerse dashboard. Top it up in Settings, under Billing. Check the balance with
GET /v1/wallet. - Launch a small first campaignStart with the minimum budget, confirm it is approved and verify the results match your expectations.
- Scale upIf you need higher limits (budget per campaign, campaigns per day, request rate), ask us.
Getting help
Email support@byteverseafrica.com or message WhatsApp +234 904 625 5604. Include the request_id from the error body or the x-request-id header so we can find your request instantly.
