A simple REST API with personal keys. Every key acts with its creator's permissions, so your data stays as safe as in the app.
curl "$QUILO_URL/api/v1/clients?q=marti" \
-H "Authorization: Bearer $QUILO_API_KEY"The Quilo API lets your own software read and write your Quilo data: clients, sales, custom orders, appointments, tasks and invoices. Use it to connect a website form, a webshop, a point-of-sale system, a spreadsheet or an automation tool such as n8n, Zapier or Make.
| Area | Read | Create | Change | Delete |
|---|---|---|---|---|
| Clients | yes | yes | yes | yes (owners, admins, managers) |
| Sales | yes | yes | yes | yes (owners, admins, managers) |
| Custom orders | yes | yes | yes | yes (owners, admins, managers) |
| Appointments | yes | yes | yes | yes (owners, admins, managers) |
| Tasks & follow-ups | yes | yes | yes | yes (owners, admins, managers) |
| Invoices (with lines) | yes | — | — | — |
| Brands | yes | — | — | — |
Every member of a Quilo company can create personal API keys under Settings → API keys. A key belongs to one person in one company and acts as that person: it sees exactly the brands and records that person sees in the app, with the same role. A Read only key can never change anything. You send the key in the Authorization header of every HTTPS request, and Quilo answers with JSON.
$QUILO_URL is the address of your Quilo, for example https://quilo.example.ch. Settings → API keys shows yours in the test command.$QUILO_API_KEY is a key you created. Keep it in an environment variable, never in code./api/v1.