Add user by specifying relevant fields. User must have a valid token with required permissions.
Endpoint: POST /v1/user. Authentication: requires AuthorizationHeader bearer token unless this operation's security is changed. Required AuthMind permission/scope: admin/user (grant this scope on the API token in Admin > API Tokens; a token without it receives 403 Forbidden). No query or path parameters are documented for this operation. Request body: send JSON matching the referenced request schema. Response parsing: inspect success; on failure inspect error, errors, or message depending on the referenced schema.
AuthMind user role. Valid values should be retrieved from GET /v1/roles unless documented otherwise.
Password value used by the user-management operation when applicable.
- Mock serverhttps://apidoc.authmind.com/_mock/v1/docs/v1/user
- https://apidoc.authmind.com/{{.Host}}/amapihttps://apidoc.authmind.com/{{.Host}}/amapi/v1/user
curl -i -X POST \
https://apidoc.authmind.com/_mock/v1/docs/v1/user \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"name": "Jane Doe",
"email": "jane.doe@example.com",
"role": "Admin",
"password": "DummyPassw0rd!",
"locale": "en-US"
}'Request completed successfully. See the referenced schema for the response envelope and result payload.
Error message returned when the request fails. This is free-form, human-readable text intended for logging/display -- AuthMind does not define a stable, cross-endpoint error-code contract for it. Branch integration logic on the HTTP status code and the success boolean, not on the contents of this string.
{ "errors": "", "success": true }