When something is not working: what each message means, whom to contact and what can be fixed right away — without reading code.
When something is not working, guessing is the worst option. First recognise what is going on, then take the step from the table — and tell support what they need to solve it on the first try.
The company cannot take rides
Code
Means
Fix
errors.launchNotReady
It did not pass the readiness gate (12 checks)
Home → Company readiness shows what is missing; the company owner fills it in
errors.moduleDisabled
The module is not enabled for the company
The platform enables the module (Money → Modules); data stays
errors.tenantInactive
The company is not active (trial, block)
The platform checks the subscription and company status
400 uz key polja
An invalid form field — key names the field
The field is marked with a message; fix it and save again
Sign-in and session
Code or symptom
Means
Fix
errors.invalidCredentials
Wrong e-mail or password
Check case and spaces; use Forgot password?
errors.sessionExpired
The session expired or was revoked
Sign in again; if it repeats, the platform checks account security
errors.accountInactive
The account is deactivated
The company owner reactivates it under Users
Sign-in asks for a code but you have no app
Two-factor protection is on
Use a recovery code or ask the platform to reset the second factor
Rides
Symptom
Usual cause
Fix
A ride waits but drivers “exist”
Drivers are not on duty, lack valid documents, or their vehicle does not match the service type
Fleet → Drivers and Alerts; assignment only offers eligible drivers
The ride cannot be cancelled
It is already finished or cancelled (errors.rideTransitionNotAllowed)
Refresh the ride; if a new one is needed, create it
An offer does not reach the driver
Notifications are off or the driver is paused
The driver enables notifications and checks the shift state
The price in the app and in settlement differ
A different period, or the ride is not finished yet
Check the period and the ride status in Settlement
API and integrations
Status and code
Means
Fix
401 errors.invalidApiKey
The key is not recognised
Check the X-API-Key header or Authorization: Bearer
403 errors.forbidden
The key lacks a scope
The company owner adds the scope (Company → Developer)
403 errors.apiKeyRevoked / apiKeyExpired
The key was revoked or expired
Issue a new key and switch the integration
403 errors.apiKeyIpNotAllowed
The request comes from an address not on the list
Add the address to the key list or remove the restriction
429 errors.tooManyRequests
Rate limit exceeded (120/min per key)
Honour the Retry-After header; reduce calls or polling
A webhook does not arrive
The endpoint returns errors or the address was rejected (private address, http)
GET /api/v1/webhooks shows delivery counts and dead letters
Apps on the phone
Symptom
Fix
No offers in the background
Allow notifications and background work; on Android disable battery optimisation for the app
Location is not being sent
Location permission must be “while using” or “always”; also check GPS is on
The map is blank
No network or the map key expired — ask the company to check map settings
The app asks for sign-in every time
The session was revoked or “Remember me” is off
What to tell supportSend: the error code, the time (date and hour), the ride number (R-…) and the role you were using. Those four facts shorten a fix from a day to minutes.