Create a User
POST/rise/Users
Idempotent upsert — if a user with the same email already exists, they are updated instead of created. Still returns 201 in both cases. On upsert, displayName is not modified — the existing user's value is preserved and the value in the request body is discarded. On production, a successful POST may send a first-access email; users created via this API are SSO-only and cannot log in with username/password. There is no SCIM-side API to check delivery or re-send it — use the RSC product UI for re-sends. A POST without at least one role returns 400 (the error message contains the word "role"); the request has no effect and no first-access email is sent. Troubleshooting — if a user you provisioned is absent from both the GET list and GET /rise/Users/{id} (404), the invitation may still be PENDING (activation failed). Remove the pending invitation with DELETE /rise/Users/{id} (204) and re-create the user via POST.
Request
Responses
- 201
- 400
- 401
- 403
- 500
User created
Invalid request — userName missing/invalid, or none of the roles[].value IDs match an RSC role (the error message reads "must have at least one active role" in that case).
Missing or invalid Bearer token
Tenant is not configured for this product
Internal server error — if this persists, contact your Inspectorio representative.