Testing your integration
Test against the real API, with real validation, without touching a single real destination.
Test and live keys
Every account gets two API keys, tk_test_... and tk_live_.... Which one you send determines what happens, not a separate environment or a different base URL. A test-key request is validated exactly like a live one, same required fields, same rejection on a malformed hash, but it's never actually forwarded to Google, Meta, or anywhere else. Nothing you send with a test key can affect a real campaign's numbers.
The response still tells you what would have happened
A test request gets back the same shape of response a live one would, a status per destination, just marked as simulated rather than delivered. That's how you catch a destination-specific problem (a hashing mistake, a missing required field for one particular network) before it's live, not just whether Toplu itself accepted the request.
{ "id": "evt_1a2b3c", "status": "simulated", "destinations": { "google": { "status": "simulated", "code": 200 }, "meta": { "status": "simulated_failure", "code": 400, "error": "invalid_user_data" } }}Need a hand?
Coding is hard sometimes, and that's okay. Visit our help center or reach out directly, we're here to help.