Integrations Documentation
Step-by-step guides for connecting external tools and automation platforms — n8n, Zapier, Make, Apps Script, and others — to the Valora API. Each page is task-oriented (built around a single workflow) rather than endpoint-oriented, so you can follow it end-to-end without jumping between docs.
API hosts (use these with the paths below):
- Production:
https://valora.spotahome.com/(sandbox compatible)- Staging / testing:
https://valora-testing.laravel.cloud/(sandbox compatible)
Before you start
Most integrations call authenticated Valora endpoints, so you'll usually need:
| Requirement | Details |
|---|---|
| Auth type | Bearer token (long-lived API token, auth:api guard) |
| How to obtain a token | See Long-Lived API Token Authentication |
| Headers | Authorization: Bearer {token} and Accept: application/json |
| Token class | Match the endpoint — Employee tokens for /api/v1/e/..., Customer tokens for /api/v1/c/.... The wrong class returns HTTP 403. |
| Sandbox first | Test against https://valora-testing.laravel.cloud/api/sandbox/v1/... with a sandbox token before pointing the workflow at production. |
| Rate limits | 5000 req/min per employee, 120 req/min per customer, 60 req/min per IP for guest (unauthenticated) routes. |
The Get Started section covers the API conventions (headers, pagination, errors, amounts in minor units) that every integration relies on — read it first if you haven't already.
Guides
| Guide | Tool | Workflow |
|---|---|---|
| Send a File to Valora Storage | n8n | Configure an n8n HTTP Request node to upload a generated file (XML, PDF, CSV, …) to Valora's storage API. |
More step-by-step guides for n8n and other automation tools (Zapier, Make, Apps Script) will be added here as they're written. If you're integrating with a tool not yet documented, the authentication reference plus the relevant Customer or Employee endpoint page is enough to wire up almost any HTTP-capable platform.
Looking for unauthenticated endpoints? Public routes under
/api/v1/open/...(VAT validation, etc.) live in their own Open Endpoints section.