Fair rules for building with your trips.
These terms cover the Nookivia API and MCP server: API keys, the apps you approve and the AI assistants you connect. They sit on top of our Terms of Service, which still apply.
At a glance
Your credentials, your trips.
A key, an app or an assistant acts as you, and reaches only your trips. Use it for yourself, keep it secret, and don't use it to reach anyone else's nook.
The API and MCP server are new. We switch access on account by account, and things may change while we learn what works.
Who it's for
It acts for you, on your trips.
An API key acts as the account that created it. An app or assistant you approve acts as you, with only the access you agreed to. Either way, it can see and change your trips and nobody else's.
Use the API for yourself: your own scripts, and the apps and assistants you choose to connect. You're responsible for what they do with your trips, as if you'd done it yourself.
Keep it nice
What you must not do
Hold other people's access
Don't ask for, collect or store anyone else's Nookivia keys or tokens, or build a service that reaches other people's accounts.
Sell or share access
Don't sell, rent or hand on your access, or put the API behind a service of your own for others to use, unless we've agreed it with you in writing.
Get round the limits
Stay within the rate limits in the API reference. Don't spread requests across keys or addresses to get round them, or probe for ways past them.
Everything our Terms of Service say you must not do applies here too.
Looking after keys
Keep keys like passwords.
Anyone holding a key can do whatever its scopes allow. Keep it out of code you share and places others can read, and give it only the scopes it needs. If a key may have leaked, revoke it on your API keys page straight away, and tell us if it was used.
Access
We switch it on, and we can switch it off.
Every account starts without API access or MCP access, and we grant each when you ask. We may limit, suspend or withdraw either, or revoke a key or an app's access, where we reasonably need to protect you, other people or the service, or where these terms are broken. We'll tell you why where we can.
What we promise
Early access, with no uptime promise.
We work to keep the API and MCP server running and accurate, but we don't promise they'll always be available, fast or free of mistakes. Don't build anything that can't cope with them being unavailable for a while.
Within a version of the API we only add things, such as a new route or field, and they can come at any time. A change that would break something built on the API comes as a new version beside the old one, and we aim to keep the old one working for at least 30 days after we announce it, in the API reference and in the Deprecation and Sunset headers on its responses. The MCP server's tools change the same way: we add to them, and aim to give 30 days' notice in the API reference before changing or removing one. A change needed for security, or to meet the law, may come sooner.
Keeping the rules current
We may update these terms.
If we make a material change, we'll update this page and its version and effective date. Using the API or MCP server after that means you accept the new terms; if you don't, revoke your keys and remove your apps and assistants.
The other important pages
The rest of the rules still apply.
The Terms of Service cover everything else, including liability and where disputes belong. The Privacy Policy explains how we handle personal data, and the Cookie Policy explains cookies. Where these terms and the Terms of Service differ, these terms apply to the API and MCP server.
Ready to build?
Keys, the reference and how to connect your assistant.
Back to Developers