# Authentication



## Scope and provenance

- Product: web
- Status: Imported reference snapshot. Import date is not a verification date or guarantee of current release support.
- SDK version: Not declared for this page. Versions in examples must not be assumed current.
- Environment: Page-specific. Confirm the environment host, credentials, and service configuration; do not infer them from another product.
- Source: https://websdk2docs.idmission.com/getting-started/authentication
- Imported at: 2026-10-21T17:27:01.149Z
- Canonical page: https://docs.idmission.com/web/getting-started/authentication
- Agent index: https://docs.idmission.com/llms.txt

---

<a id="authentication"></a>

### Authentication

Before using the IDmission WebSDK, you will need to obtain an API key. New customers receive their API credentials via email. If you haven't received them, reach out to <support@idmission.com>.

To test that your credentials are valid:

```bash
curl -s -H "Content-Type: application/json" \
  -d '{"api_key_id": "your-api-key-id", "api_key_secret": "your-api-secret"}' \
  https://portal-api.idmission.com/portal.sessions.v1.SessionsService/CreateSession
```

Prior to initializing the WebSDK on the client, you should generate a session on your server using these credentials. Be careful not to leak them on the client side! The generated session id is safe to pass to the client, but the secrets used to generate them are not. If you have inadvertently leaked your credentials, react out to <support@idmission.com> to rotate them.

If you are using NodeJS, check out our [auth client for server-side JavaScript](https://www.npmjs.com/package/idmission-auth-client).