Alegra API

Name: Alegra API API
Brand: Alegra API
Availability: InStock

★ Only Publicly Available SpecFinanceAccountingbasic33 EndpointsREST

For Agents

Create and manage invoices, items, contacts, estimates, and payments inside an Alegra accounting account through 33 REST endpoints.

Quickstart

Get started with Alegra API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an alegra invoice"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Alegra API API.

Create, list, update, and delete Alegra invoices and email them to a customer with /invoices/{id}/email

Manage the product and service items used as invoice line items

Maintain customer and supplier contact records via /contacts

Record payments against invoices and reconcile bank account activity

GET STARTED

Start building with Alegra API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Alegra API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Alegra API, keeping it validated and agent-ready. Alegra is an accounting and invoicing platform widely used by SMBs across Latin America and Spain. The REST API exposes invoices, items, contacts (customers and suppliers), payments, estimates, credit notes, bank accounts, and chart-of-accounts categories. Authentication uses HTTP basic auth with the user's Alegra email and an API token from the Alegra account.

Use Cases

Patterns agents use Alegra API API for, with concrete tasks.

★ Automated invoicing from a billing system

A SaaS billing system creates an invoice in Alegra each time a subscription renews by calling POST /invoices with the customer contact id, line items, and dates. The same workflow then calls POST /invoices/{id}/email to deliver the invoice straight to the customer. Bookkeeping stays in Alegra while the system of record stays in the SaaS app.

POST /invoices with the contact id and items array, then POST /invoices/{id}/email with the recipient address

Two-way contact sync between a CRM and Alegra

An ops engineer mirrors customers from a CRM into Alegra by listing /contacts, comparing against CRM records by email, and creating or updating contacts as needed. Keeping contact metadata aligned lets the accounting team produce invoices without re-entering names and tax IDs.

GET /contacts to list existing entries, then POST /contacts for missing CRM customers and PUT /contacts/{id} for changed records

Payment reconciliation and credit notes

An AR clerk reconciles incoming bank transfers against Alegra invoices by listing /payments and matching amounts to invoice ids. When a refund is required, the clerk issues a credit note via the credit notes resource, keeping the ledger consistent without manual journal entries.

GET /payments for the period, match each row to an invoice by amount and contact, and POST a credit note for any refunds

Agent-driven invoice lookup and dispatch

A Jentic agent answers requests like 'send the latest invoice to client X' by listing the contact, finding the most recent invoice, and emailing it via POST /invoices/{id}/email. The agent never sees the basic auth credentials and never has to compose Spanish-language email templates manually.

Search Jentic for 'create and email an Alegra invoice', execute POST /invoices for the contact, then chain POST /invoices/{id}/email with the recipient

Key Endpoints

33 endpoints — jentic publishes the only available openapi specification for alegra api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/invoices

Create an invoice

GET

/invoices/{id}

Retrieve an invoice

POST

/invoices/{id}/email

Email an invoice to a contact

POST

/contacts

Create a contact

POST

/items

Create a product or service item

POST

/payments

Record a payment

POST

/estimates

Create an estimate

POST

/invoices

Create an invoice

GET

/invoices/{id}

Retrieve an invoice

POST

/invoices/{id}/email

Email an invoice to a contact

POST

/contacts

Create a contact

POST

/items

Create a product or service item

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Alegra basic auth credentials (account email plus API token) are stored encrypted in the Jentic credential vault. Jentic builds the Authorization header at execution time, so the raw token never appears in the agent's prompt.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create an alegra invoice', 'record a payment'), and Jentic returns the matching Alegra operation with its input schema for direct execution.

Time to first call

Direct Alegra integration: 2-3 days for auth, invoice payload modelling, and reconciliation logic. Through Jentic: under an hour with search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Xero Accounting API

Use Xero for English-speaking SMB accounting outside Alegra's Latin America and Spain footprint

Choose Xero when the customer is in AU/NZ/UK/US; choose Alegra when the customer is based in Latin America or Spain

Complementary

Stripe API

Pair with Alegra so Stripe handles card collection while Alegra produces the legal invoice

Use Stripe alongside Alegra when payment capture must happen in Stripe but the bookkeeping ledger lives in Alegra

Complementary

Airtable API

Source line item data from an Airtable base to drive Alegra invoice creation

Use Airtable alongside Alegra when the catalogue or project data feeding invoices is maintained by a non-finance team in Airtable

FAQs

Specific to using Alegra API API through Jentic.

Why is there no official OpenAPI spec for Alegra API?

Alegra does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Alegra API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Alegra API use?

Alegra uses HTTP basic auth, where the username is the account email and the password is the API token from the Alegra account settings. Jentic stores both encrypted and injects the Authorization header at execution time so the credentials never enter the agent's prompt context.

Can I create and email an invoice with the Alegra API?

Yes. POST /invoices with the contact id, items, and dates to create the invoice, then POST /invoices/{id}/email with the recipient address to send it. The same id can be retrieved later with GET /invoices/{id} for audits.

What are the rate limits for the Alegra API?

The OpenAPI spec does not declare rate limits. Alegra enforces plan-based limits server-side (commonly a few requests per second per token), so batch high-volume invoice or contact sync jobs accordingly.

How do I record a payment against an invoice through Jentic?

Search Jentic for 'record an alegra payment', load the schema for POST /payments, and execute it with the invoice id, amount, and bank account id. Jentic returns the payment record so an agent can confirm reconciliation.

Can I issue a credit note for a refund using the Alegra API?

Yes. The credit notes resource lets you issue a credit against an existing invoice. The credit note keeps the ledger consistent without manual journal entries and is visible in the same Alegra account as the original invoice.