Umovi integration platform
Errors and troubleshooting
OAuth failures, authorization errors, validation and retry decisions.
REST Integration API
| Status | Meaning | Response |
|---|---|---|
400 | Invalid input or business rule violation | Fix request data; do not retry unchanged. |
401 | Missing, invalid or expired token | Obtain a new token and retry once. |
403 | Missing scope or provider mismatch | Correct client permissions or provider configuration. |
404 | Resource not found in the provider boundary | Verify identifiers and ownership. |
409 | Slot conflict or idempotency conflict | Re-read state; choose another slot or reconcile the original attempt. |
429 | Integration rate limit exceeded | Respect server guidance and retry with backoff. |
5xx | Temporary server failure | Retry idempotent operations with bounded exponential backoff. |
Responses can include a machine-readable code. Branch on stable codes and HTTP status, not human message text. Preserve X-Request-Id when reporting a problem to support.
Browser tester
The tester sends requests directly from the browser. If it reports Failed to fetch, check:
- that the Base URL uses an explicitly configured allowed HTTPS origin and is reachable from the browser;
- whether the selected origin is present in
TESTER_ALLOWED_ORIGINS_JSON; - CORS response headers;
- VPN, tunnel or Cloudflare connectivity;
- the browser Network panel for blocked preflight requests.
Credentials are not sent through a documentation proxy.
MCP
Protected MCP tools can return an OAuth challenge with the required scopes. Reconnect or authorize the missing scope instead of repeatedly calling the tool. Stable MCP result fields such as status, statusCode, nextAction, missing and consent flags should drive the client flow.