# Register a personal access client

Registers a new personal access client against the authenticated user and returns it.
The `id` on the response is the `client_id` the token endpoint expects.
The client belongs to the caller. It is not shared with the rest of the account, and it
carries the caller's own access - a token issued through it can reach whatever that user
can reach, so register the client as the user whose access the integration should have.
**The response does not include the client secret**, and no endpoint returns it
afterwards. Ask Rosterfy for the secret that goes with the `client_id` this call
returns; until you have it, the client cannot complete a token exchange.

Endpoint: POST /api/v2/oauth/clients
Version: 2.0.0
Security: default

## Header parameters:

  - `Rosterfy-Platform` (string)

## Request fields (application/json):

  - `name` (string, required)
    A label for the client, shown wherever the client is listed. Use something that identifies the system that will hold the credentials, so a client can be recognised and withdrawn later without guesswork.

  - `redirect` (string, required)
    The absolute URL an authorisation response is returned to. Required in practice: a request that omits it fails, so send a URL you control even when the integration never redirects a browser anywhere.

## Response 201 fields (application/json):

  - `user_id` (integer)

  - `name` (string)

  - `provider` (string | null)

  - `redirect` (string)

  - `personal_access_client` (boolean)

  - `password_client` (boolean)

  - `revoked` (boolean)

  - `updated_at` (string)

  - `created_at` (string)

  - `id` (integer)