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

# Welcome!

Here you'll find all the documentation you need to get up and running with the TextMaster API.

## Want to jump right in?

Feeling like an eager beaver? Jump in to the quick start docs and get making your first request:

{% content-ref url="/pages/kyUn6dlB1Mp8CUL1wh9o" %}
[Quick Start](/quick-start.md)
{% endcontent-ref %}

## Want to deep dive?

Dive a little deeper and get more details about available resources:

{% content-ref url="/pages/iQQLDpOFxLu35fhVd8pq" %}
[Resources in the REST API](/overview/resources-in-the-rest-api.md)
{% endcontent-ref %}

Or, start learning about OAuth Apps:

{% content-ref url="/pages/qYrz6Sqapsud2BoZSSbt" %}
[About OAuth Apps](/apps/about-oauth-apps.md)
{% endcontent-ref %}

Or, start exploring our API reference to get an idea of everything that's possible with the API:

{% content-ref url="/pages/2Z4rP31NK4SYpfSsPvfS" %}
[Reference](/reference/abilities.md)
{% endcontent-ref %}

Finally, don't forget to read about Webhooks to build or set up powerful integrations:

{% content-ref url="/pages/D7qSqAH0UxaINYqHIGBE" %}
[Webhooks & Events](/webhooks-and-events/webhooks.md)
{% endcontent-ref %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://developer.textmaster.com/welcome.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 `build a script that syncs our docs to a CMS` 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.