Getting started

Everything you need before you call Gurita from your own code: where the API lives, how to authenticate and what requests and responses look like.

Every Gurita customer has their own system at their own address. In these guides, https://YOUR-DOMAIN stands for that address, and the API lives under https://YOUR-DOMAIN/api.

What you can build

• Scripts and integrations on the REST API — call the same API the Gurita app uses, authenticated with a personal API key that runs as one Gurita user.
• AI assistants over MCP — let Claude, ChatGPT or your own agent answer questions from live Gurita data, read-only. See MCP server.
• Online booking on your website — embed the Gurita booking widget. See Booking widget.

Important: The REST API isn't versioned and has no public endpoint reference yet. Routes can change between releases. If you're planning an integration, contact us first.

Before you start

• You need a user account on the Gurita system you're integrating with.
• For API keys, an administrator must switch on the User API Keys module under Active Modules.
• Plan which permissions the integration needs. Best practice is a dedicated Gurita user with only those permissions — see Users & Access.

In this chapter

• Authentication & API keys — create a key and send it with your requests.
• Requests, paging & errors — JSON conventions, paging parameters and the error format.