> ## Documentation Index
> Fetch the complete documentation index at: https://symphony-docs.fcamara.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Environments and support

> Which environments to use the API in, how to keep track of changes that affect your integration, and how to get help from the Symphony team.

## What it is

This page explains which environments you can use the API in, how to find out about changes that affect your integration, and how to get help from the Symphony team.

## Environments

| Environment | URL | What it's for |
| - | - | - |
| **Production** | `https://symphony.fcamara.com` | Real use. It's your company's environment, with your models, agents, bases, and usage limit |
| **Staging (HML)** | `https://symphony-hml.fcamara.com` | The Symphony team's test environment. **Access is granted on request to FCamara employees** |

### Testing your integration

There's no open test environment (*sandbox*). In most cases, you can develop directly in production, with a few precautions:

* **Ask your company's administrator for a dedicated technical account.** That way test usage stays separate from your personal usage, and the administrator can set a low usage limit for that account.
* **Use cheaper models** while developing and switch to the final model only at the end.
* **Limit volume.** Test batches with a few items before running the full process.
* **Track usage** with `GET /api/v1/consumption/me`.

### When to request staging access

Request HML access when you need to:

* test an integration that may generate high volume or cost before releasing it in production;
* validate your integration against a Symphony version that hasn't reached production yet.

<Warning>
  HML has a **copy of some** of what exists in production, but not all of it. Before testing, check that your API key, your `X-Enterprise-Id`, and the models and agents you'll use exist in HML.
</Warning>

### How to request HML access

HML access is granted **on request** and only to **FCamara employees**. To request it, contact the **Symphony team** on [WhatsApp](https://wa.me/5511976183072) or by email at [symphony@fcamara.com](mailto:symphony@fcamara.com).

## API changes

### Symphony version

To find out which version is running in an environment:

```bash theme={null}
curl https://symphony.fcamara.com/api/version
# { "version": "2.8.0" }
```

What's new in each version is published in [Releases](/en/changelog).

### What's stable

The API doesn't have its own version numbers. The `v1` that appears in some paths (`/api/v1/...`) is part of the address and doesn't change with each Symphony version.

To keep your integration working over time:

* **Use only the endpoints in the [API reference](/en/desenvolvedores/api/referencia-da-api).** Endpoints outside it are internal and may change without notice.
* **Ignore fields you don't recognize** in responses. New fields can be added at any time, and that isn't considered a breaking change.
* **Handle errors by `code`**, never by message text (see [Errors and limits](/en/desenvolvedores/api/erros-e-limites)).
* **Don't hard-code model IDs.** Read the model from configuration and validate it with `GET /api/models` at startup. The catalog is managed by your company and can change.

## Support

### Before opening a ticket

<Steps>
  <Step title="Check the quickstart">
    See **Most common issues when starting out** in [Connect via API](/en/desenvolvedores/api/conectar-api). Most early problems are the key or `X-Enterprise-Id`.
  </Step>

  <Step title="Look up the error code">
    Check the code catalog in [Errors and limits](/en/desenvolvedores/api/erros-e-limites).
  </Step>

  <Step title="Confirm permissions and limit">
    Check with your company's administrator that your account has the required permission and usage limit.
  </Step>
</Steps>

### Who to contact

| Topic | Who to talk to |
| - | - |
| API key, permissions, usage limit, company ID, available models and agents | **Your company's Symphony administrator** |
| Unexpected error, behavior that differs from the docs, request for a new endpoint, HML access | **The Symphony team** |

Contact the Symphony team on [WhatsApp](https://wa.me/5511976183072) or by email at [symphony@fcamara.com](mailto:symphony@fcamara.com).

### What to send in the ticket

* The **`request_id`** from the error response.
* The **environment** (production or HML).
* The **endpoint**, the approximate **time**, and the time zone.
* The **HTTP status** and the error **`code`**.
* The request body, **without the API key**.

<Warning>
  **Never send your API key**, not in a ticket, an email, or a screenshot. If it leaks, generate a new one right away in **Settings → Account → API keys**.
</Warning>

## Related documents

* [Connect via API](/en/desenvolvedores/api/conectar-api)
* [Building projects with the API](/en/desenvolvedores/api/projetos-com-a-api)
* [API reference](/en/desenvolvedores/api/referencia-da-api)
* [Errors and limits](/en/desenvolvedores/api/erros-e-limites)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.