# Approve a registration request `POST /api/v1/presubscriptions/{id}/approve` Approves the request and links or creates the applicable athlete or staff record. ## Permissions Send your API key in `X-API-Key`. Required permissions are **Presubscriptions → Write**. ## Headers - `X-Sport-Id` (integer, required) — The sport ID from [List sports](/api/sports/list.md). Use the sport the record belongs to. ## Path parameters - `id` (integer, required) — ID of the registration request. ## Body parameters - `onApprovedSetup` (map) — Optional approval configuration. Athlete requests support plan_ids, team_ids, and send_approval_email. Athlete requests need a given name, surname, and tax code before approval. Configure the plans, teams, and email behavior before approving. Approval can create linked records. If the workspace requires a user for those writes, complete the approval in the workspace. ## Request Set ASDINCLOUD_API_KEY and any variables named in the example before running it. ```sh curl --request POST \ --url "https://api.asdincloud.com/api/v1/presubscriptions/${ID:?Set ID}/approve" \ --header "X-API-Key: $ASDINCLOUD_API_KEY" \ --header "X-Sport-Id: ${SPORT_ID:?Set SPORT_ID}" \ --header "Content-Type: application/json" \ --data '{"onApprovedSetup":{"send_approval_email":false}}' ``` ## Response **200 OK** Returns the approval result and related records in `data`. An already approved request returns its existing linked result. Example with fictional data and selected fields. ```json { "message_key": "entities.presubscription.messages.approved_successfully", "data": { "id": 34, "approved_at": 1794564000, "athlete_id": 42, "athlete": { "id": 42, "firstname": "ALEX", "surname": "EXAMPLE", "sport_id": 3 }, "parent1": null, "parent2": null, "medical_document": null, "medical_document_id": null, "medical_status": null, "generic_document": null, "generic_documents": [], "subscriptions": [], "team_assignments": [] } } ``` ## Errors - `401` — The API key is missing or invalid. - `403` — The API key lacks the required permission. - `404` — The requested record was not found. - `409` — An existing identity or document conflicts with the request. - `422` — One or more fields failed validation. - `500` — Approval failed. - `503` — The approval document could not be prepared.