> For the complete documentation index, see [llms.txt](https://api-docs.rightsline.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-docs.rightsline.com/overview/other-references.md).

# Other references

### Swagger

Rightsline utilizes Swagger to aid in integrating with the API.  You can find the Swagger UI [here](https://ris.rightsline.com/swagger/index.html).

{% hint style="info" %}
If the YAML file is used to generate objects, know that not all properties are required.  It is best to review the data that is returned specifically for your company to understand which fields are needed when creating and updating entities.
{% endhint %}

### Sample projects

Sample code for .NET, Java and Python can be found on our GitHub [here](https://github.com/rightsline/sample-projects).  A sample AWS Lambda project that responds to Rightsline SQS messages can be found [here](https://github.com/rightsline/sample-lambda).

### Message Queues

Documentation of Rightsline's message queues can be found [here](https://queue-docs.rightsline.com).


---

# 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://api-docs.rightsline.com/overview/other-references.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.