Skip to content
Efidis
Efidis

Operations8 min read

Siigo API: what you can connect and how

3D illustration of a clipboard with an order linked by a cable and a lilac plug to an icon with the Siigo logo, next to two delivery boxes.
In this article

The Siigo API is the door that lets another program write to and read from your Siigo Nube without anyone typing. It fits a very common case: accounting and invoicing already live in Siigo, but orders, the day's stock, deliveries and commissions are still in spreadsheets and WhatsApp chats. This guide covers what the API does today according to the official documentation, what it doesn't, and how the connection is built, with a single example: a distributor with sales reps on the road.

What the Siigo API does today

We reviewed the Siigo API documentation in November 2026 (Siigo, Siigo API documentation). This is what another system can do:

You need toIn the API?How
Invoice a saleYesCreates the sales invoice, one at a time or in batches, and can send it as an e-invoice and by email in the same request. It can also read it, void it and download its PDF and XML.
Find out why an e-invoice was rejectedYesThere is a lookup that returns the errors on rejected invoices.
Create and update customersYesCreates, reads, lists and updates customers, including the sales rep assigned to each one.
Keep the catalog currentYesCreates, updates and deletes products and their inventory groups. Reads price lists, taxes and warehouses.
Check stockYesEach product returns the quantity available in total and by warehouse.
Hear when inventory changesYesWebhooks: Siigo notifies your system when a product is created or modified and when its stock changes.
Send quotesYesCreates, edits, reads and deletes quotes.
Record a paymentYesCreates cash receipts, and every invoice you read comes with its balance due.
Record purchases and expensesYesPurchase invoices, support documents, payment vouchers and journal entries.
Pull accounting reportsPartlyGeneral trial balance, trial balance by third party, and accounts payable.
Take orders, issue delivery notes or schedule dispatchNoThe documentation has no orders, delivery notes, dispatch or routes. Delivery notes exist in the Siigo Nube screens, not in the API.
Calculate commissionsNoThere are no commissions. It does carry the sales rep on each invoice and each line, which is the data you need to calculate them elsewhere.

The rule that comes out of the table: Siigo receives the sale once it's closed. Everything that happens before (the order, picking in the warehouse, the route, the delivery) and what gets calculated after (the commission) needs another system that talks to Siigo.

The example: a distributor with reps on the road

This is a made-up example with round numbers. A food distributor has 6 sales reps who visit shops, one warehouse and its accounting in Siigo. Today the rep sends the order over WhatsApp, someone copies it into a spreadsheet, the warehouse asks whether there's stock, the delivery goes out and, at the end of the day, someone types every invoice into Siigo. At 60 orders a day, that's 60 invoices keyed in by hand, plus the commission math at month end. What that typing costs is in what manual data entry costs.

With the API, the work splits like this:

  1. The rep takes the order in an appThis happens in your system, because the API has no orders. The app already knows the customers, products and prices, copied from Siigo through the API so the codes match.
  2. The app shows what's in the warehouseYour system keeps a copy of stock levels and updates it with the stock-change webhook. That way it doesn't ask Siigo about every product on every visit, and the rep doesn't promise stock that isn't there.
  3. The warehouse picks and shipsAlso in your system: the pick list, the day's route and proof of delivery. Siigo doesn't know about it yet.
  4. On delivery, the invoice is created in SiigoYour system creates the invoice with the customer, products, warehouse and sales rep, and asks for it to be sent as an e-invoice. If the connection drops and it has to retry, the idempotency key keeps the invoice from going out twice.
  5. The payment is recorded as a cash receiptWhen the customer pays, your system creates the receipt in Siigo and reads the invoice balance. Receivables by rep come from there, with no matching statements by hand. Why collecting on time matters is in what collecting late costs.
  6. Commissions calculate themselves at month endYour system adds up the invoices, or the amount collected if commission is paid on collections, by the sales rep on each invoice. Siigo doesn't calculate commissions, but it does store the data that makes them possible.

The result: accounting stays in Siigo, nobody types an invoice again, and what used to live in the chat sits in a custom system with a date, an owner and a status.

Siigo API or Siigo MCP: which one is for what

In October 2026 Siigo added an MCP, in beta: an official connection that lets Claude or ChatGPT look up your customers, products and invoices, and create customers and invoices with your authorization; it shows you each invoice to confirm before creating it (Siigo, 2026). It's free, only an admin user can turn it on, and it uses the same credentials as the API.

It's good for a manager's questions: how much was invoiced this month, which customers bought the most, where receivables stand. It doesn't replace the integration in the example: it doesn't take orders, ship or calculate commissions, and a person confirms each invoice inside the chat. To get 60 orders a day invoiced without anyone stepping in, you need the API.

Limits to know before you connect

  • 100 requests per minute per company in production and 10 in the test company. A distributor with 60 orders a day fits easily; an online store with traffic spikes should send in batches or queue.
  • Average response time is under 2 seconds, but Siigo recommends waiting up to 120 seconds before giving up when creating invoices, credit notes, receipts or journal entries. The rep shouldn't be staring at the screen meanwhile: the invoice is created in the background.
  • The access token lasts 24 hours and has to be renewed. Every request also carries a header with the name of the application connecting.
  • Webhooks only cover product and stock changes. For invoices, receipts or customers created inside Siigo, your system has to check periodically.
  • An admin generates the credentials in Siigo Nube: Configuración, Alianzas e integraciones, «Credenciales de integración a plataformas digitales (Siigo API)». Test company details are requested from Siigo support.
  • The API and the MCP come with the Premium, Profesional Independiente and Emprendedor plans of Siigo Nube (Siigo, 2023 and 2026). On another plan, talk to Siigo first.

Checklist before you ask for the integration

  • Your Siigo Nube plan includes the API and you have a user who can generate the credentials.
  • Every product has a unique code, and it's the same in Siigo and in your spreadsheets.
  • Products sold from the warehouse have inventory control turned on, and warehouse management is on if you have more than one.
  • Every sales rep exists as a user in Siigo, because the invoice requires one.
  • You know which invoice type, payment method and cost center each sale uses.
  • You've decided when the invoice is created: when the order is taken, when it ships or when it's delivered.
  • You know how commission is calculated: on invoiced or collected amounts, and at what rate per product or per rep.
  • Someone reviews rejected invoices, and there's a rule for retrying.

When you don't need the Siigo API

If you sell from a single location, invoice from Siigo's point of sale and have no reps on the road, the API saves you almost nothing: you already invoice where you sell. It also isn't worth it if all you want is to pass sales from a well-known online store platform; look for a ready-made connector first and pay for a custom integration only if that connector doesn't cover your rules. The API pays off when a sale goes through several steps and several people before it becomes an invoice, like the distributor in the example.

Sources

  1. Siigo, Siigo API documentation (Apiary), accessed 2026 (opens in a new tab)
  2. Siigo, Siigo API developer portal (opens in a new tab)
  3. Siigo, "Generar credenciales API," customer portal, 2026 (opens in a new tab)
  4. Siigo, "Siigo API: qué es, cómo habilitarla y para qué sirve," 2023 (opens in a new tab)
  5. Siigo, "Elaborar remisiones," customer portal, 2026 (opens in a new tab)
  6. Siigo, "MCP: conecta Siigo con asistentes de inteligencia artificial como ChatGPT o Claude," 2026 (opens in a new tab)
  7. Siigo, "Preguntas frecuentes de MCP," 2026 (opens in a new tab)
See how we work in route-based distribution

Frequently asked questions

Get every order invoiced in your Siigo

At Efidis we build the app where your team takes orders, ships and collects, and we connect it to your Siigo. On the call we go over your workflow and tell you what the API can automate and what it can't.