Sandbox & testing
A test token (dsl_test_) is the same API over the member’s own account, with one difference that matters: nothing it creates can reach a real person.
Test and live, side by side
| Test token | Live token | |
|---|---|---|
| Reads | The member’s real data | The member’s real data |
| Requests it sends | Arrive in the member’s Inbox marked Test, and never email the requester, whatever notifyRequester says | Arrive as from the public page; the requester gets Daysli’s emails and a status link unless notifyRequester is false |
statusUrl | Always null | The requester’s status link when they are notified |
GET /me | "mode": "test" | "mode": "live" |
| Webhooks and requests | "test": true | "test": false |
| Rate limits | The same | The same |
There is no separate test environment or sample data set: a test token reads the account it belongs to. Test against your own Daysli account, or a colleague’s who has agreed, before you ask anyone else for a live token.
A testing routine
- Make a test token with only the permissions your integration needs.
- Check it with
GET /me, and branch onmodeif your code treats test differently. - Send requests and withdraw them afterwards with
POST /requests/{id}/withdraw, so the Inbox stays tidy. - Add a webhook address and use Send a test in Settings → Developer to deliver a fresh
pingwhenever you like; Recent deliveries shows what was sent and the answer your address gave. - Replay what you missed with
GET /webhook-events. - Make a live token with the same permissions and swap it in.
Test against the contract
The OpenAPI 3.1 document at https://daysli.com/developers/openapi.json is built from the definitions the server enforces, and answers are exactly these shapes. Generate a client from it, or validate your mocks against it. Unknown query parameters and body fields are refused with 422 invalid_input, so a typo fails loudly in testing instead of being ignored.