> 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/guide-to-openactive-on-github/rpde.md).

# RPDE

Code and other tools related to Real-Time Paged Data Exchange.

'RPDE' stands for 'Realtime Paged Data Exchange', a specification that outlines how [Opportunity](https://www.openactive.io/modelling-opportunity-data/) (and to some extent [Booking](https://www.openactive.io/open-booking-api/EditorsDraft/)) data is to be chunked and sequenced by publishers for consumption by OpenActive data clients.  

Repos with the topic `rpde` include:

* [**realtime-paged-data-exchange**](https://github.com/openactive/realtime-paged-data-exchange)**:** Backend repo for the published [RPDE specification](https://www.w3.org/2017/08/realtime-paged-data-exchange/).
* [**activation**](https://github.com/openactive/activation)**:** Has no content as such, but serves as a focal point and forum for discussion and issue-raising with regard to the RPDE spec. 
* [**rpde-sample-azure**](https://github.com/openactive/rpde-sample-azure)**:** Quick and dirty implementation of RPDE using Azure Functions.
* [**azure-rpde-proxy**](https://github.com/openactive/azure-rpde-proxy)**:** An app allowing RPDE clients to self-register, along with a deployment template for Azure services. 
* [**rpde-validator**](https://github.com/openactive/rpde-validator)**:** Library supporting validation of RPDE feeds.


---

# 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/guide-to-openactive-on-github/rpde.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.