Skip to content
KelkiDevelopers

Sandbox

With a kk_test_… key, everything works as in production — same catalog, same validations, same errors, same response shapes — but no real request is created and no e-mail is sent.

Test and production

Sandbox (kk_test_, kat_test_)Production (kk_live_, kat_live_)
Accessas soon as the account is openedafter approval by Kelki and acceptance of the terms
Catalog and validationsrealreal
Requestskept apart, never transmittedKelki's normal flow
E-mailsnone (sending simulated)real e-mails to the person
Statusesmoved forward by you (simulate); abandoned after 48 hreal
Webhooksreal, to the test-mode endpointsreal, to the live-mode endpoints
Kelki Agentreal, low message capreal

The two modes are sealed off: a test request is never visible with a live key, and vice versa (404).

Simulating statuses

curl -s https://kelki.ai/api/v1/sandbox/requests/req_01JC00000000000000000000RQ/simulate \
  -H "Authorization: Bearer $KELKI_KEY_TEST" -H "Content-Type: application/json" \
  -d '{"status":"transmitted"}'

Possible values: transmitted, abandoned, sold, not_taken, called_back. Each change triggers the same webhooks as in production. With a live key, this route does not exist.

Dummy data

Going live

Kelki opens real access after reviewing your service (description, screens of the flow, a contact person) and your acceptance of the API terms. You then create a kk_live_… key: your code does not change. The decouverte plan (sandbox only) allows no real request; see rate limits and quotas.