Create a User
POST/sight/Users
Idempotent upsert — if a user with the same email already exists, they are updated instead of created. If the existing user is INACTIVE, the upsert also reactivates them. Still returns 201 in both cases. Role IDs are integers but must be sent as JSON strings — e.g. { "value": "4" }, not { "value": 4 }. On upsert, displayName is preserved from the existing user record. 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 QRM 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.
Request
Responses
- 201
- 400
- 401
- 403
- 409
- 500
User created
Invalid request — userName missing/invalid, or none of the roles[].value IDs match a QRM 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
Conflict — POST upsert on an INACTIVE user attempted reactivation but the org user quota is exceeded
Internal server error — if this persists, contact your Inspectorio representative.