> ## Documentation Index > Fetch the complete documentation index at: https://docs.skyfree.io/llms.txt > Use this file to discover all available pages before exploring further. # Create or update user > Create or update a platform user. type is mandatory (create | update | both). Backend always enforces role=admin. Legacy app:* permissions are rejected with 400. Authentication: API key via X-API-Key header (or Authorization: Bearer). Permissions: User API key Rate limit: api_admin_write — 20 requests/min per API user. ## OpenAPI ````yaml /api-reference/platform.openapi.json post /api/platform/v1/users/manage openapi: 3.1.0 info: title: Platform API version: 1.0.0 description: >- Manage platform users, subscriptions, add-ons, and support tickets across your platform. These endpoints require platform-level access on the account that owns the API key. Generate your API key in the Developer Portal (profile menu → Developer) and send it in the `X-API-Key` header, or as `Authorization: Bearer `. Never put the key in the URL. Every endpoint accepts POST with a JSON body, and also accepts GET with the same parameters as query-string values. All responses use the envelope `{ success, data?, message?, error? }`. servers: - url: https://YOUR_DOMAIN description: Your deployment, for example https://app.example.com security: [] tags: - name: Platform - name: Users - name: Subscriptions - name: Add-ons - name: Tickets paths: /api/platform/v1/users/manage: post: tags: - Users summary: Create or update user description: >- Create or update a platform user. type is mandatory (create | update | both). Backend always enforces role=admin. Legacy app:* permissions are rejected with 400. Authentication: API key via X-API-Key header (or Authorization: Bearer). Permissions: User API key Rate limit: api_admin_write — 20 requests/min per API user. parameters: - name: platformId in: query required: false description: Your platform id. schema: type: string example: pf_1 - name: type in: query required: false description: create | update | both. schema: type: string - name: email in: query required: false description: User email (lookup key). schema: type: string example: john@acme.com - name: username in: query required: false description: Required when creating. schema: type: string - name: password in: query required: false description: Required when creating. schema: type: string - name: firstName in: query required: false description: First name. schema: type: string - name: lastName in: query required: false description: Last name. schema: type: string - name: phone in: query required: false description: Phone digits. schema: type: string - name: countryCode in: query required: false description: 2-letter code, e.g. IN. schema: type: string - name: countryDialCode in: query required: false description: Dial code, e.g. +91. schema: type: string - name: status in: query required: false description: Account status. schema: type: string requestBody: required: true content: application/json: schema: type: object required: - platformId - type - email properties: platformId: type: string description: Your platform id. example: pf_1 type: type: string description: create | update | both. email: type: string description: User email (lookup key). example: john@acme.com username: type: string description: Required when creating. password: type: string description: Required when creating. firstName: type: string description: First name. lastName: type: string description: Last name. phone: type: string description: Phone digits. countryCode: type: string description: 2-letter code, e.g. IN. countryDialCode: type: string description: Dial code, e.g. +91. status: type: string description: Account status. example: platformId: pf_1 type: both email: john@acme.com username: john_admin password: StrongPass@123 responses: '200': description: 'Success. Envelope: { success:true, data, message? }.' content: application/json: schema: type: object required: - success properties: success: type: boolean example: true data: {} message: type: string pagination: type: object total: type: number example: success: true message: User created successfully data: email: john@acme.com role: admin '400': description: >- Missing/invalid parameters. Body has success:false plus error and message. content: application/json: schema: type: object required: - success - error properties: success: type: boolean example: false error: type: string message: type: string '401': description: >- Missing or invalid API key (or session expired for session endpoints). content: application/json: schema: type: object required: - success - error properties: success: type: boolean example: false error: type: string message: type: string '403': description: >- Authenticated but not authorized — wrong permissions or cross-tenant resource. content: application/json: schema: type: object required: - success - error properties: success: type: boolean example: false error: type: string message: type: string '404': description: Email not found when type=update. content: application/json: schema: type: object required: - success - error properties: success: type: boolean example: false error: type: string message: type: string '409': description: Email/username already exists when type=create. content: application/json: schema: type: object required: - success - error properties: success: type: boolean example: false error: type: string message: type: string '429': description: >- Rate limited. Retry after the Retry-After seconds; see RateLimit-* headers. content: application/json: schema: type: object required: - success - error properties: success: type: boolean example: false error: type: string message: type: string '500': description: >- Unexpected server error. Body has success:false plus error and message. content: application/json: schema: type: object required: - success - error properties: success: type: boolean example: false error: type: string message: type: string security: - apiKeyHeader: [] - bearerAuth: [] components: securitySchemes: apiKeyHeader: type: apiKey in: header name: X-API-Key description: Preferred. API key value directly. bearerAuth: type: http scheme: bearer description: Alternative. API key as the bearer token. ````