Validate Token

Validate authentication token and return organization data. This endpoint allows other services (like context-graph-api) to validate tokens without duplicating auth logic. The control plane handles all validation, caching, and Kubiya API integration. The token should be passed in the Authorization header: - Bearer <token> for user JWT tokens - UserKey <token> for worker/API key tokens Returns: Organization dict with user and org information: { "id": "org-slug", "name": "Organization Name", "slug": "org-slug", "user_id": "user-uuid", "user_email": "[e-mail]", "user_name": "User Name", "user_avatar": "...", "user_status": "...", "user_groups": [...] } Raises: 401: Invalid or expired token 500: Internal server error Example: ```bash curl -H "Authorization: Bearer <token>" \ https://control-plane.kubiya.ai/api/v1/auth/validate ```

GET /api/v1/auth/validate

Validate Token

cURL

curl --request GET \
  --url https://control-plane.kubiya.ai/api/v1/auth/validate \
  --header 'Authorization: Bearer <token>'

200

{}

Authorizations

Authorization · string · header · required

Enter your Kubiya API token (format: Bearer )

Response

200 - application/json

Successful Response

The response is of type Response Validate Token Api V1 Auth Validate Get · object.