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

# Getting started

Learn how to integrate with the Sylvera API

#### Overview <a href="#overview" id="overview"></a>

This API allows you to programmatically retrieve data for various carbon credit projects.

#### Base URL <a href="#base-url" id="base-url"></a>

`https://api.sylvera.com/v1`

#### Content type <a href="#content-type" id="content-type"></a>

All requests should include:

`Content-Type: application/json`

#### Rate limiting <a href="#rate-limiting" id="rate-limiting"></a>

API requests are rate-limited to ensure fair usage. Implement appropriate retry logic with exponential backoff for production applications.

**Important notes**

* Access tokens expire after 30 minutes
* Use the refresh token to obtain new access tokens
* Include the Bearer token in all subsequent API requests
* Treat API keys like passwords — keep them secure

**Data availability**

The data available through the API is dependent on your account permissions. Some endpoints or data fields may return limited results or require additional access rights. Contact your account manager if you need access to additional data.<br>


---

# 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.sylvera.com/api/getting-started.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.
