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

# API credentials

> Create scoped organization bearer credentials for applications and automation.

API credentials are organization-owned bearer tokens intended for server-to-server access.

Credential management is session-authenticated:

```text theme={null}
POST   /v1/organizations/{organization_id}/credentials/
GET    /v1/organizations/{organization_id}/credentials/
GET    /v1/organizations/{organization_id}/credentials/{credential_id}
PATCH  /v1/organizations/{organization_id}/credentials/{credential_id}
DELETE /v1/organizations/{organization_id}/credentials/{credential_id}
```

A credential has a name, optional description, scopes, optional expiration time, usage metadata, and disabled state.

## Token handling

The usable token is returned only when the credential is created. Leamout persists a SHA-256 hash and a non-secret prefix, not the plaintext token.

Store the token in a secrets manager and send it as:

```http theme={null}
Authorization: Bearer lm_org_...
```

## Scopes

Telecom resources use resource-specific read/write scopes. For example, an application that lists and controls calls needs both:

```text theme={null}
calls:read
calls:write
```

Prefer narrow scopes over broad credentials. Disabling a credential invalidates it without deleting its audit history.