Skip to content

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 tokenLive token
ReadsThe member’s real dataThe member’s real data
Requests it sendsArrive in the member’s Inbox marked Test, and never email the requester, whatever notifyRequester saysArrive as from the public page; the requester gets Daysli’s emails and a status link unless notifyRequester is false
statusUrlAlways nullThe requester’s status link when they are notified
GET /me"mode": "test""mode": "live"
Webhooks and requests"test": true"test": false
Rate limitsThe sameThe 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

  1. Make a test token with only the permissions your integration needs.
  2. Check it with GET /me, and branch on mode if your code treats test differently.
  3. Send requests and withdraw them afterwards with POST /requests/{id}/withdraw, so the Inbox stays tidy.
  4. Add a webhook address and use Send a test in Settings → Developer to deliver a fresh ping whenever you like; Recent deliveries shows what was sent and the answer your address gave.
  5. Replay what you missed with GET /webhook-events.
  6. 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.