> For the complete documentation index, see [llms.txt](https://developer.openactive.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.openactive.io/specifications/specifications-overview.md).

# Specifications Overview

## Summary

OpenActive's specifications are created in an open and collaborative process. For more information about contributing to these specifications, please see the [OpenActive W3C Community Group](https://w3c.openactive.io).

## List of Specifications

[Paging specification](https://www.openactive.io/realtime-paged-data-exchange/) - The specification for the OpenActive API transport

[Modelling specification](https://www.openactive.io/modelling-opportunity-data/) - The specification for the OpenActive API data fields

[OpenActive activity list ](https://www.openactive.io/activity-list/)- A canonical list of activities for reference in OpenActive data feeds

[Open Booking API ](https://www.openactive.io/open-booking-api/EditorsDraft/)- A draft version of the OpenActive booking specification


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.openactive.io/specifications/specifications-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.