Our API documentation¹ has had a thorough overhaul: it is much faster, every topic is explained from the ground up, you can ask Claude or ChatGPT about any endpoint with one click, and the complete API description is available from a URL, ready to import into the API client or code generator of your choice.

Nothing changes in the API itself, and every existing link into the documentation keeps working.

Ask an AI assistant about any endpoint

Each endpoint now has a Copy button with a menu:

• 🤖 Open in Claude / Open in ChatGPT start a chat that reads our API description and answers your questions about that endpoint: which fields a request needs, what a response looks like, how to call it from your language of choice.
• 📋 Copy for LLM copies the endpoint’s part of the API description, to paste into whichever assistant or coding agent you work with.

The API description from a URL

The documentation is built from an OpenAPI 3.0 description of the API, and that file now has a stable address:

https://docs.motiontools.io/schema.yml

It always matches the published documentation, so tools can load it directly instead of you downloading and passing around a copy: API clients, code generators, and AI assistants and coding agents that can fetch a URL. The download button at the top of the documentation leads to the same file.

The documentation’s introduction has a new section on putting the address to use, Use the API in your tools². It explains how to import the description into Bruno³ and Insomnia⁴, two popular API clients for sending requests and inspecting the responses, which gives you a ready-made collection with a request for every endpoint.

Easier to find your way around

• 📖 Every topic explained. Each topic in the sidebar now says what the feature is, what you do with it and which endpoints to start with, and each group opens with an overview of how its topics fit together: see Bookings⁵ or Tours⁶ for an example.
• 👋 A new introduction that walks through the platform end to end, from booking and package intake through dispatching and tours to the customer’s payment and the drivers’ compensation, and where the API comes in.
• ⚡ Much faster. The documentation opens noticeably quicker and stays responsive while you browse: each topic and endpoint now opens as a page of its own instead of everything loading as one very long page.
• 🔍 A search that finds more. Open it from the sidebar or with the keyboard shortcut shown there: it looks through the names, paths and descriptions of endpoints as well as the properties of their requests and responses, and a result takes you right to the endpoint or property it matched.
• 🔗 Deep links to any property. Every request and response property has a link of its own, including properties nested deep inside a response. When you discuss a specific property with a colleague or our support team, send them its link and the documentation opens right on it, with no more describing where to scroll and what to expand.
• 🌗 A fresh design with a dark mode, following your system’s setting, with syntax highlighting for the code examples and diagrams drawn to match.

What changes for your integration

Requests and responses stay exactly as they were. Two things are worth a look if you work with the documentation or the API description itself:

• Links keep working. Addresses in the documentation have a new format, and links in the previous format still lead to the right place, including those to “Managing Organizations”, which is now called Organization Management⁷.
• Filter parameter names in the API description are shorter, e.g. BookingsQueryFilter-filters. If you generate types or clients from the description and refer to these by name, update the names when you regenerate.