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

# Developers

{% hint style="info" %}
This section covers the UI sections of the Workspace related to development tools. If you're looking for documentation, examples and technical references, check our [CARTO for Developers documentation](https://github.com/CartoDB/gitbook-documentation/blob/master/carto-user-manual/developers/broken-reference/README.md).
{% endhint %}

CARTO Workspace has been designed to be the start of the journey and the centralized experience for all things CARTO — And that includes our tools to make the development of large-scale geospatial custom applications as easy as possible.

To achieve this, the **Developers section** provides easy access to:

* **Credentials management:** Manage the authentication credentials for your different projects, from simple and static API Access Tokens to more dynamic OAuth Clients. [Learn more about Credentials](/carto-user-manual/developers/managing-credentials.md).
* **API-enabled Workflows:** Get a quick overview of all the CARTO Workflows that you have enabled to be programmatically executed from an API endpoint. [Learn more about executing Workflows via API](/carto-user-manual/workflows/executing-workflows-via-api.md).
* **Named Sources:** Avoid exposing SQL queries in your application while keeping a lightweight and efficient modern data architecture. [Learn more about Named Sources](/carto-user-manual/developers/named-sources.md).
* **Documentation and resources:** Let us set you up for success — We've curated a set of links and examples so that you can learn how to build powerful, large-scale geospatial applications with CARTO that drive value for your organization. Learn more about [CARTO for Developers](/carto-for-developers/overview.md).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-63d897d708968ca2035f6638acff29b434117617%2FScreenshot%202024-11-21%20at%2014.36.01.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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://docs.carto.com/carto-user-manual/developers.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.