nookivia
AboutSign in
Developers

Build with your trips.

The Nookivia API lets your own scripts, apps you approve and AI assistants such as Claude read and change the trips in your nook. Here's how to get started.

At a glance

A small API for your trips.

List, create, change and delete the trips on your account, with JSON in and JSON out. Every request acts as you, and only ever sees your trips.

Early access.

Every account starts without API access, and we switch it on when you ask. Read the API terms first: they say what you can build and what we promise.

Getting access

Two ways in.

An API key, for your own scripts. A key acts as you. Create keys on your account's API keys page, and choose what each one can do: trips:read to read your trips, trips:write to create, change and delete them, sources:read to see the address you forward booking emails to and your bookings’ manage links, sources:write to ask for an email Nookivia set aside to be read anyway. Keep a key secret, like a password: you'll see it once, when you create it.

OAuth, for apps. An app asks for your permission first, and gets only the access you agree to. Nothing else in your nook comes with it.

Ask us to switch it on. Your account starts without API access, so a key or an app is turned away until we grant it. Just ask, through Contact us in Help. AI assistants such as Claude need MCP access, which we grant separately. Your account page shows which you have.

Either way, send the credential with every request as Authorization: Bearer <credential>.

For AI assistants

MCP server

Connect Claude, or any assistant that speaks the Model Context Protocol, to https://mcp.nookivia.com/mcp. It can list and read your trips, and create, change and delete them, with the same rules as the API: a change needs the version you last read, so it never overwrites something you haven't seen.

It takes the same credentials as the API, an API key or an OAuth token, and the credential's scopes decide which tools the assistant is offered: trips:read for reading, trips:write for changes, sources:read for your forwarding address. An assistant that supports OAuth finds out where to sign in from the server itself. MCP access is granted separately from API access, so ask us for the one you need.

Every tool, and what it returns. Read the MCP guide.

Setting up

Connect your assistant.

Claude, Claude Code and Cursor sign in to Nookivia as you, and ask for what they need: reading your trips, or changing them too. You'll see the request before you agree. ChatGPT uses an API key instead. Each works once we've granted your account MCP access.

Claude

On claude.ai, Claude Desktop or the mobile app, open Customize, then Connectors, and choose Add custom connector. Enter https://mcp.nookivia.com/mcp, then connect and sign in to Nookivia.

Claude Code

Add the server from your terminal, then run /mcp in a Claude Code session and choose Nookivia to sign in.

claude mcp add --transport http nookivia https://mcp.nookivia.com/mcp

ChatGPT

ChatGPT connects with an API key rather than by signing in. Create one on your API keys page, with trips:read to read your trips, and trips:write too to change them. A key that stops working sooner is safer; when it does, ChatGPT stops connecting, so create another and put it in ChatGPT.

In a chat, on chatgpt.com or in the app, first turn on Developer mode: open Settings, then Security and login, and switch on Developer mode. Then open Plugins, choose +, and add https://mcp.nookivia.com/mcp as its address with your API key as its bearer token. Your workspace may not offer Developer mode.

In Codex, in the ChatGPT desktop app, the Codex CLI or an IDE, you don't need Developer mode. Add the server to Codex's config.toml, put your API key in the NOOKIVIA_API_KEY environment variable, and restart Codex.

[mcp_servers.nookivia]
url = "https://mcp.nookivia.com/mcp"
bearer_token_env_var = "NOOKIVIA_API_KEY"

Cursor

Cursor needs a client ID from us, which we send with your MCP access. Add the server to mcp.json, then sign in from Cursor's MCP settings. Add trips:write to scopes to let it change your trips.

{
  "mcpServers": {
    "nookivia": {
      "url": "https://mcp.nookivia.com/mcp",
      "auth": {
        "CLIENT_ID": "<the client ID we send you>",
        "scopes": [
          "trips:read"
        ]
      }
    }
  }
}

The rules

API terms

A key or an assistant acts for you, on your own trips. What you can build, what you mustn't, and what we promise while the API is in early access. Read the API terms.

For people

API reference

Every route, its parameters and its responses, with examples you can try. Open the API reference.

For tools

OpenAPI document

The same reference as OpenAPI 3.1 JSON. Point a client generator or your favourite API tool at it. Get the OpenAPI document.

For LLMs

Markdown for LLMs

The full reference as plain Markdown, ready to hand to a language model. Read the Markdown reference. There's also an llms.txt at the root of the site that points the way.

nookivia

Your trips. Your nook.

AboutHelpContactPrivacy PolicyTerms of ServiceCookie PolicyDevelopers