Alegra
Service ID: alegra
Cloud-based invoicing, accounting and POS software popular across Latin America (Mexico, Colombia, Peru, Spain, Dominican Republic, Argentina, Chile and others) for SMBs and entrepreneurs.
Beta — this connector is in beta. Functionality and resource coverage may change.
At a Glance
- Difficulty
- ⚡MODERATEBasic Authentication — consumers generate their own API token
- Authentication
- Basic AuthThe Alegra account email as username and an in-app API token as password; not OAuth.
- Webhooks
- Native — invoices, bills, customers/suppliers and invoice-items emit created/updated/deleted events; the other 12 resources are polled.
- Partnership Required
- No(No partner programme, app registration or approval stands between you and the API.)
- Apideck Credentials
- Not available(Alegra has no OAuth app to share, so every consumer brings their own token.)
- Costs
- No additional charge — API access is included in the Alegra subscription plan that carries it.
- Sandbox Availability
- Not available(The API always runs against a real Alegra account; use an account you control.)
- Account Type Required
- Alegra account on a plan that includes API integrations
- Consumer Access Level
- Any Alegra user who can open account settings and generate an API token; the credential is tied to that user's account email.
- Rate Limits
- 150 requests per minute per user; exceeding it returns 429. Every response carries X-Rate-Limit-Limit, -Remaining and -Reset headers.
Responsibility matrix
| Task | You (Customer) | Your Consumer | Apideck |
|---|---|---|---|
| Enable the Alegra Connector | ✓ Via Apideck Dashboard | — | — |
| Alegra Account on a Plan with API Access | — | ✓ | — |
| Generate & Supply the API Token in Vault | — | ✓ | — |
| Store & Encrypt Credentials | — | — | ✓ |
| Build via the Unified API | ✓ Builds the requests | — | ✓ Maintains connector |
| Monitor Connections | ✓ Via Apideck Dashboard | ✓ Can renew or revoke the token anytime | ✓ Logs & alerts |
Environments
- Single environment
- Alegra serves every country edition from one API host and offers no separate sandbox, so testing and production share the same credential shape: an account email plus an API token.
- Testing
- Test against an Alegra account you already control. It holds live data, so treat anything the integration writes as production data.
🚨Important to Know About Alegra
- API access requires an eligible Alegra plan (the Plus plan, per Alegra's help centre), and some plans cap how many active integrations an account may have; the exact tier and cap vary by country. Confirm the plan for your consumers' country.
- Regenerating the API token in Alegra ("Renovar token") invalidates the old one immediately, so a consumer who renews their token breaks the connection until they supply the new value in Vault.
- Building and testing against the API needs no permission, but Alegra's API Terms require its prior written authorisation before you distribute or commercialise a product built on it, and it can refuse anything it judges competitive. Raise this with Alegra early.
- A single Alegra contact can be both a customer and a supplier: the same underlying record appears in both lists and shares one id, so deduplicate by id when you sync both.
- Alegra's developer documentation is Spanish-only.
⚠️
12 gotchas across 12 resources
Connector-specific behaviors and limitations to be aware of
📦
17 supported resources
View field mappings, supported operations, and schema details