User Management Endpoints
Update user
Updates a user in Parchment
PUT
Integration Notes
- No role updates:
access_roles,emailattributes will be ignored. - Partial Updates: Only include fields you want to update. Omitted fields will not be modified.
- Provider Updates: Use the
provider_detailsobject for provider-specific fields to ensure proper validation. - Validation Dependencies: Be aware of field dependencies, especially for provider details.
- User Existence: The API will return 404 if the user doesn’t exist in the organization.
- Request ID: Always log the
requestIdfor debugging support requests.
Request
Update Basic User Information
Update Provider Details
Update Both User and Provider Information
User Fields
| Field | Type | Required | Description |
|---|---|---|---|
full_name | string | No | User’s given name |
Provider Details
When updating provider-specific information, use theprovider_details object:
| Field | Type | Required When | Description |
|---|---|---|---|
given_name | string | No | Prescriber’s given name |
family_name | string | No | Prescriber’s family name |
date_of_birth | string | No | Date of birth in YYYY-MM-DD format |
sex | string | No | Sex (M/F/I/N) |
hpii_number | string | No | Healthcare Provider Identifier |
phone | string | No | Provider phone number |
title | string | No | Professional title |
prescriber_number | string | When prescriber_type is not ‘T’ (podiatrist) | Max 10 characters |
provider_number | string | No | Max 10 characters |
prescriber_type | string | No | Prescriber type (M/E/U/F/D/V/T/C) |
ahpra_number | string | No | AHPRA registration number |
qualifications | string | When prescriber_type is provided | Professional qualifications |
hospital_provider_number | string | No | Hospital provider number |
erx_entity_id | string | No | ERX Entity ID provided by ERX |
Validation Rules
- Prescriber Number: Must be 10 characters or less
- Provider Number: Must be 10 characters or less
- Provider Details Dependencies:
- If
prescriber_typeis provided,qualificationsmust also be provided - If
prescriber_typeis not ‘T’ (podiatrist),prescriber_numberis required
- If
- Date Format: Date of birth must be in YYYY-MM-DD format
- Sex Values: Must be one of: M (Male), F (Female), I (Indeterminate), N (Not-stated)
Prescriber Types
Valid values forprescriber_type:
M(Medical Practitioner)E(Eye/Optometrist)U(Nurse)F(Midwife)D(Dentist)V(Veterinarian)T(Podiatrist)C(Pharmacist)
Response
Success Response (200 OK)
Validation Error (422 Unprocessable Entity)
User Not Found (404 Not Found)
Unauthorized (401)
Insufficient Permissions (403 Forbidden)
Rate Limited (429 Too Many Requests)
Response Fields
Success Response Data
| Field | Type | Description |
|---|---|---|
user_id | string | Parchment’s unique user identifier |
Common Response Fields
All responses include these standard fields:| Field | Type | Description |
|---|---|---|
success | boolean | Indicates if the request was successful |
statusCode | number | HTTP status code |
timestamp | string | ISO 8601 timestamp of the response |
requestId | string | Unique identifier for debugging |
Status Codes
| Code | Status | Description |
|---|---|---|
200 | OK | User successfully updated |
400 | Bad Request | Invalid request format or invalid parameters |
401 | Unauthorized | Authentication required or token invalid |
403 | Forbidden | Insufficient permissions (missing update:user scope) |
404 | Not Found | User not found |
409 | Conflict | Update conflict (e.g., duplicate values) |
422 | Unprocessable Entity | Request validation failed |
429 | Too Many Requests | Rate limit exceeded |
500 | Internal Server Error | Unexpected server error |
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Organization secret for authentication - provided by Parchment
Path Parameters
Organization ID
User ID
Body
application/json
User data to update in Parchment
The body is of type any.
Response
User updated successfully

