Sandbox Testing

📘
Sandbox environment only
Magic identifiers only work with a sandbox API key. They have no effect in production.

Overview

When you submit a login request in the sandbox using one of the magic identifiers below, Palenca always returns the corresponding pre-configured response. This lets you test every status code, OTP flow, and error condition your integration needs to handle — without hitting a live platform.

Identifier formats

Email: <platform>+<case>@palenca-tests.com

Example: [email protected]

Phone: A fixed phone number per case. See the platform phone table below.

📘
Phone identifiers
The full phone lookup table is published by engineering. Contact your integration support contact or check the API Reference for the complete list.

Platform support

Platform	Email	Phone
`uber`	✅	❌
`rappi`	✅	✅
`didi`	❌	✅
`didi_food`	❌	✅
`ifood`	❌	✅
`indriver`	❌	✅
`pedidos_ya`	❌	✅
`noventa_nove`	❌	✅

Test cases

Final states

Submit the identifier and receive the response in a single call.

Case	`status`	`status_detail`
`success`	`success`	—
`incomplete`	`incomplete`	—
`invalid_credentials`	`error`	`invalid_credentials`
`login_refused`	`error`	`login_refused`
`platform_unavailable`	`error`	`platform_unavailable`
`request_timeout`	`error`	`request_timeout`
`platform_error`	`error`	`platform_error`
`recent_login_successful`	`error`	`recent_login_successful`
`not_registered`	`error`	`not_registered`
`banned`	`error`	`banned`

OTP flow (2-step)

The first call returns a normal OTP challenge. Any OTP you submit on the second call triggers the error.

Case	`status_detail` on 2nd call
`invalid_otp`	`invalid_otp`
`expired_otp`	`expired_otp`
`could_not_send_otp`	`could_not_send_otp`
`invalid_otp_auth_key`	`invalid_otp_auth_key`
`invalid_otp_session`	`invalid_otp_session`

Account warnings

Returned alongside a success response to simulate accounts with specific conditions.

Case	Warning flag
`rider_account`	`rider_account`
`fleet_account`	`fleet_account`
`incomplete_profile_data`	`incomplete_profile_data`
`id_mismatch`	`id_mismatch`

Webhooks in sandbox

All sandbox webhook notifications are delivered with a 30-second delay to simulate real-world processing latency. This applies to all webhook events: login.created, login.success, login.incomplete, and login.error.

If you are testing with a tool like webhook.site, wait at least 30 seconds after submitting a login before expecting the notification.

See Webhooks for setup instructions.