> For the complete documentation index, see [llms.txt](https://dev.ropo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ropo.com/readme.md).

# Developer Platform

<h2 align="center">Ropo Developer Portal</h2>

<p align="center"></p>

<p align="center">Welcome to the Ropo One® Developer Portal – your go-to space for technical resources that help you connect systems, automate workflows, and enhance the way you use our solutions. Here you’ll find clear API documentation, integration guides, and technical references to support you through every step of your development or implementation journey. </p>

<p align="center">This portal is designed for our customers and the technical teams who support them, offering everything you need to get started quickly and make the most of Ropo One’s capabilities. </p>

<p align="center"></p>

<p align="center"><img src="/files/Vm3b3OEf47rIULhLixMN" alt=""></p>

<p align="center"></p>

{% columns %}
{% column %}
{% embed url="<https://ropo.com/>" %}
{% endcolumn %}

{% column %}
{% embed url="<https://status.ropo.com/>" %}

{% endcolumn %}
{% endcolumns %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dev.ropo.com/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.