# Organizations API - Authentication

Organizations API calls use OAuth2 Client Credentials with the MyNamirial OIDC provider.

This model is designed for machine-to-machine integrations where a partner or customer-side integration calls One Platform APIs without an interactive user session.

## Token Request


```shell
MY_NAMIRIAL_BASE_URL="https://auth-preprod.namirial.app"

curl --request POST \
  --url "${MY_NAMIRIAL_BASE_URL}/realms/namirial/protocol/openid-connect/token" \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data 'grant_type=client_credentials' \
  --data 'client_id=<client_id>' \
  --data 'client_secret=<client_secret>'
```

If the request is valid, MyNamirial returns an `access_token`.

## API Request


```shell
ONE_PLATFORM_BASE_URL="https://<one-platform-api-host>"

curl --request GET \
  --url "${ONE_PLATFORM_BASE_URL}/v1/organizations/<organization_id>/consumers" \
  --header "Authorization: Bearer <access_token>"
```

The response is limited to the organization and permissions associated with the integration client.

## Security Notes

- Store `client_id` and `client_secret` in a secure server-side secret store.
- Do not expose credentials in browser code, mobile apps, or public repositories.
- Request only the permissions required by the integration.
- Rotate credentials according to the agreed operational security policy.


## Related Pages

- [Organizations API Overview](/products/oneplatform/one-platform-knowledge-center/04-api-and-integration/organizations-api/overview)
- [Organizations API Endpoints](/products/oneplatform/apis/oas/organizations)
- [Integration Guides](/products/oneplatform/one-platform-knowledge-center/04-api-and-integration/organizations-api/integration-guides/overview)