> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/api-and-development/developer-resources.md).

# Developer Resources

### Overview

Developer Resources support integration and automation use cases.

This section covers API tokens and Console usage for investigation and discovery.

### Key Concepts

* **API token**: secret credential used for API authentication
* **Least privilege**: granting the minimum access needed
* **Rotation**: replacing credentials on a schedule to reduce risk
* **Console**: natural language query interface for Project content

### How It’s Used

Use API tokens for system-to-system integration and automation.

Use Console to validate decisions, approvals, and item history during investigations.

### Benefits

* Reduced manual work through automation
* Cleaner governance through traceable sources
* Faster troubleshooting with repeatable query patterns

### Setup Steps

Start with the correct topic:

* [API Tokens](/api-and-development/api-tokens.md)
* [Console](/ai/console.md)

### Best Practices

{% hint style="warning" %}
Treat API tokens like passwords.

Do not paste them into messaging tools, screenshots, or tickets.
{% endhint %}

### Summary

Developer Resources focus on secure API authentication and fast discovery using Console.

Related:

* [Connectors](/administration/connectors.md)
* [Contact Support](/resources/contact-support.md)


---

# 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://help.transform.ai/api-and-development/developer-resources.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.