Aliaddo API
★ Only Publicly Available OpenAPI DocumentFinanceAccountingbearer17 EndpointsREST
For Agents
Manage invoices, sales orders, products, contacts, and accounting entries inside Aliaddo, a Colombian accounting and business management platform.
Use for: I need to create an invoice in Aliaddo, Record a payment against an existing invoice, List all sales orders for the current month, Void an invoice that was issued in error
Not supported: Does not handle payment processing, payroll, or storefront management - use a payment gateway, payroll system, or commerce platform for those. Use this API for accounting, invoicing, and inventory inside Aliaddo only.
Jentic publishes the only available OpenAPI specification for the Aliaddo API, keeping it validated and agent-ready. Aliaddo is a Colombian accounting and business management platform, and its API exposes 17 endpoints covering invoicing, sales orders, sales remissions, accounting entries, cost centers, products, warehouses, and contacts. The API is bearer-token authenticated and is aimed at integrators automating billing, inventory, and contact sync between Aliaddo and external commerce systems.
Install Jentic One Beta
Connect the Aliaddo API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Aliaddo API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Aliaddo API.
Issue and manage electronic invoices via /invoices, including void via PATCH /invoices/{id}/void
Record customer payments against an invoice via POST /invoices/{invoiceId}/payments
Create and list sales orders via /sales-orders
Create and list sales remissions for goods movement tracking via /sales-remissions
Look up accounting entries (asientos contables) and cost centers (centros de costos) for reporting
Manage product catalog and inventory locations via /productos and /bodegas
Maintain customer and supplier contact records via /contactos
Use Cases
Patterns agents use Aliaddo API for, with concrete tasks.
★ E-commerce to Aliaddo invoice sync
When an e-commerce store closes a sale, an integration can call POST /invoices to issue an electronic invoice in Aliaddo, capture the customer via /contactos if not yet present, and record the customer's payment via POST /invoices/{invoiceId}/payments. The flow keeps the storefront and the accounting ledger in sync without manual data entry.
POST /contactos to upsert the customer, POST /invoices with the line items, and POST /invoices/{invoiceId}/payments to register the payment in COP
Inventory and product catalog automation
Pull the current product catalog with GET /productos and warehouse list with GET /bodegas to power external storefronts or BI dashboards. New SKUs can be created via POST /productos, keeping the master catalog in Aliaddo while exposing it elsewhere.
GET /productos to fetch the catalog, then POST /productos for any SKU missing in Aliaddo
Accounting reporting and cost-center analysis
Pull accounting entries via GET /asientos-contables and cost centers via GET /centros-de-costos to feed an external reporting tool. The endpoints provide the same data the Aliaddo dashboard uses, so reports stay consistent with the source ledger.
GET /asientos-contables for the requested date range, group by /centros-de-costos, and write the rows to the BI warehouse
Agent-driven invoicing in conversational tools
An AI assistant operating through Jentic can pull up customer details, draft an invoice from a chat conversation, and post it to Aliaddo. The bearer token stays in the Jentic vault, so the agent never sees raw credentials and the resulting invoice IDs are returned for follow-up.
Search Jentic for 'create Aliaddo invoice', load createInvoice, and execute with the customer ID and line items extracted from the conversation
Key Endpoints
17 endpoints — jentic publishes the only available openapi specification for the aliaddo api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/invoices
Create an invoice
POST
/invoices/{invoiceId}/payments
Record a payment against an invoice
PATCH
/invoices/{id}/void
Void an invoice
POST
/sales-orders
Create a sales order
GET
/productos
List products
POST
/contactos
Create a contact
GET
/asientos-contables
Read accounting entries
POST
/invoices
Create an invoice
POST
/invoices/{invoiceId}/payments
Record a payment against an invoice
PATCH
/invoices/{id}/void
Void an invoice
POST
/sales-orders
Create a sales order
GET
/productos
List products
POST
/contactos
Create a contact
GET
/asientos-contables
Read accounting entries
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Aliaddo bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped Jentic token at request time; the raw bearer value never enters agent context or logs.
Intent-based discovery
Agents search Jentic by intent (e.g. 'create Aliaddo invoice' or 'list Aliaddo products') and Jentic returns the matching Aliaddo operation with its input schema.
Time to first call
Direct integration: 1-2 days to wire auth, invoice creation, payment recording, and contact sync. Through Jentic: under 30 minutes - search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Aliaddo API through Jentic.
Why is there no official OpenAPI spec for the Aliaddo API?
Aliaddo publishes documentation on its readme.io site but does not host a packaged OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Aliaddo 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 Aliaddo API use?
HTTP bearer authentication. Tokens are issued from the Aliaddo dashboard and passed as Authorization: Bearer {token}. Through Jentic, the bearer token is stored in the vault and injected at request time so agents never handle the raw value.
Can I issue an electronic invoice with this API?
Yes. POST /invoices creates an invoice with line items, customer reference, and tax data. Use POST /invoices/{invoiceId}/payments to register payment and PATCH /invoices/{id}/void to cancel an invoice issued in error.
What are the rate limits for the Aliaddo API?
The spec does not declare numeric rate limits. Aliaddo throttles per-account; plan for 429 responses on bulk imports and back off when they appear. Schedule heavy syncs outside Colombian business hours where possible.
How do I create an invoice through Jentic?
Search Jentic for 'create Aliaddo invoice', load the createInvoice operation, and execute with the customer ID and line items. Jentic injects the bearer token from the vault and posts to /invoices, returning the new invoice ID.
Does Aliaddo expose accounting reports through this API?
It exposes the underlying data. GET /asientos-contables returns accounting entries and GET /centros-de-costos returns the cost-center tree. Aggregation and report formatting happen on the consumer side.
GET STARTED