> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/api/reference/getting-started.md).

# Getting Started

#### Authentication

Secoda API's require an Authorization header with a Bearer token. You can generate an API key in your workspace, as outlined [here](https://docs.secoda.co/api/authentication).

#### Base URL and API Versioning

To determine the base URL of your API requests, please refer to the chart below.

| Workspace URL  | Base URL       |
| -------------- | -------------- |
| app.secoda.co  | api.secoda.co  |
| eu.secoda.co   | eapi.secoda.co |
| apac.secoda.co | aapi.secoda.co |

For teams with an On Premise or Managed instance with a custom domain, the Base URL is the custom domain followed by the appropriate API version path (e.g., `/api/v1/` or `/api/v2/`).


---

# 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://docs.secoda.co/api/reference/getting-started.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.