# Connection & access.

> Source: https://implyra.com/docs/authentication
> Implyra API docs · Get started · Connection & access

Set up access to your assigned deployment and keep the integration on your server.

## Request enterprise access

Enterprise API access is currently arranged through private onboarding. Share your use case, the data you need, and your expected traffic. Your onboarding configuration identifies the REST and stream endpoints available to your application.

Authentication and network access are deployment-specific. Use the credentials and headers supplied with your assigned endpoint. Self-service console keys use the separate developer gateway described in the Developer accounts guide.

> **Need your connection details?.** Contact hello@implyra.com or use the enterprise access form. A public dashboard session does not grant enterprise API access.

- [Developer accounts & API keys](https://implyra.com/docs/developer-accounts): Sign in, create keys, and use the staged authenticated REST gateway.

## Environment configuration

Store any deployment credentials alongside these variables in your secret manager. Make REST requests from your server, and expose only the application data your frontend needs.

| Name | Type | Description |
| --- | --- | --- |
| `IMPLYRA_API_URL` | Server environment | The REST base URL supplied during onboarding. Append the endpoint path directly; examples do not add a /v1 prefix. |
| `IMPLYRA_STREAM_URL` | Server environment | The separate stream service base URL supplied for your deployment. |

## Stream access is separate

REST and streaming run on separate services. Access to one does not establish access to the other. Some user-specific streams require an authenticated session or a short-lived stream ticket; see the real-time streams guide before connecting.