Upsert users (full records)
POST/v1/users
Customer portal users. is_active, active_from and active_to keep their value when a POST leaves them out. The email is unique across live users; a deleted user holding it is restored under the new login account. password (login_type 1) is stored hashed and must be changed at the next sign-in; groups [{ external_code }] replace the memberships; send_invite emails a set-password link. Tenant-wide: a key limited to organizations cannot use it.
Keys: id, source_system + source_record_id, login_account. Rights: READ_USER to read, POST_USER to write (and READ_DATA / POST_DATA).
Up to 1,000 records. Each record is matched by its keys and created or updated as a whole: fields left out get their default (except fields marked "kept"). Whether a record of another source system, or one entered in Nuntiq, may be changed depends on the API user's record ownership: All records, All integrated records (never records entered in Nuntiq), All records where the source system matches (default: its own records; records entered in Nuntiq are taken over), or All integrated records where the source system matches (its own records only). Otherwise the record is refused (owned_by_other_source). Only real changes are written; the answer says per record created, updated (with the changed fields) or unchanged.
Request
Responses
- 200
- 207
- 400
- 401
- 403
- 413
- 422
Every record succeeded
Some records were rejected or not found (see each result)
The request itself is invalid (not an array, empty)
Missing or invalid API key
The key lacks the right, or the record is outside its organizations
More than 1,000 records
Every record was rejected, or all_or_none rolled the request back (results inside)