Go-live checklist
What has to be true before a key is switched from sandbox to live.
What we need from you
A buy box. Markets, products, amount range, minimum monthly revenue and months trading, excluded sectors. This is what routing matches against, so the sharper it is the less noise reaches your queue.
An integration route. If we send deals to you, a webhook endpoint or a polling cadence, plus where offers come from on your side. If we post into your own intake API, your API documentation and sandbox credentials.
A commercial agreement covering remuneration per funded deal.
What to prove in the sandbox first
- Create a test deal, list it, retrieve it and read the market object that matches the market you are taking.
- Post an indicative offer, then replace it with firm terms, and confirm your side handles the upsert.
- Report
in_review, adeclinedwith a reason, and afundedwith an amount. - Receive and verify a signed webhook, including a replay of a failed delivery.
- Raise a document request and handle
request.fulfilledarriving immediately from the archive. - Delete the test deals you created.
Then
Confirm your buy box, and routing opens your lane. Keys are the same in the sandbox and live, so nothing changes in your code at go-live except the deals being real.