canonical: https://jentic.com/apis/aliaddo.com/aliaddo # Aliaddo API 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. ## For AI agents Manage invoices, sales orders, products, contacts, and accounting entries inside Aliaddo, a Colombian accounting and business management platform. ## Scope 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. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 your Jentic One instance, so the agent never sees raw credentials and the resulting invoice IDs are returned for follow-up. Example prompt: Search Jentic for 'create Aliaddo invoice', load createInvoice, and execute with the customer ID and line items extracted from the conversation ## Key endpoints | 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 | ## Key resources - **Invoices** — Electronic invoices with payments and void operations - **Sales Orders** — Pre-invoice sales orders - **Sales Remissions** — Goods movement documents - **Accounting Entries** — Read-only ledger entries (asientos contables) - **Cost Centers** — Read-only cost center hierarchy - **Products and Warehouses** — Product master and inventory locations - **Contacts** — Customers and suppliers ## Why Jentic - **Setup:** Wiring Aliaddo by hand means setting up its bearer token, targeting api.aliaddo.com, and handling invoicing, payment, and inventory calls with your own retries. Through Jentic you install once, import the Aliaddo API from the API Directory, store the bearer token once, and your agent calls it. - **Permission scoping:** Aliaddo puts the invoice id in the URL path (/invoices/{invoiceId}/payments, /invoices/{id}/void), so a rule can pin your agent to one invoice for recording payments. You choose the operations it may call, so voiding invoices or creating contacts is not included unless you add them. - **Credential handling:** Your Aliaddo bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create an invoice in Aliaddo' or 'record a payment on an invoice', and Jentic returns the matching Aliaddo operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Xero Accounting API** — International cloud accounting platform with broader country coverage - **Sage API** — Established accounting suite with deeper enterprise features - **Shopify API** — Storefront platform whose orders can be invoiced into Aliaddo ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Aliaddo API? Yes. Because you run Jentic One yourself, your own rules decide which Aliaddo operations and credentials the agent may use, so you can allow only POST /invoices while withholding PATCH /invoices/{id}/void or POST /contactos. Since Aliaddo puts the invoice id in the URL path, such as /invoices/{invoiceId}/payments, a rule can pin the agent to a single invoice when recording payments. The bearer token stays in your instance and is injected at execution time, so the agent calls only the endpoints you have permitted.