Skip to main content
PUT

Integration Notes

  1. No role updates: access_roles, email attributes will be ignored.
  2. Partial Updates: Only include fields you want to update. Omitted fields will not be modified.
  3. Provider Updates: Use the provider_details object for provider-specific fields to ensure proper validation. This applies to users with the provider or rx_queue_manager role — both roles carry a provider record (HPI-I, date of birth, sex, etc.) that is maintained through provider_details.
  4. Validation Dependencies: Be aware of field dependencies, especially for provider details.
  5. User Existence: The API will return 404 if the user doesn’t exist in the organization.
  6. Request ID: Always log the requestId for debugging support requests.

Request

Update Basic User Information

Update Provider Details

Update Both User and Provider Information

User Fields

Provider Details

When updating provider-specific information, use the provider_details object:

Validation Rules

  1. Prescriber Number: Must be 10 characters or less
  2. Provider Number: Must be 10 characters or less
  3. Provider Details Dependencies:
    • If prescriber_type is provided, qualifications must also be provided
    • If prescriber_type is not ‘T’ (podiatrist), prescriber_number is required
  4. Date Format: Date of birth must be in YYYY-MM-DD format
  5. Sex Values: Must be one of: M (Male), F (Female), I (Indeterminate), N (Not-stated)

Prescriber Types

Valid values for prescriber_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

Common Response Fields

All responses include these standard fields:

Status Codes

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

x-organization-secret
string
required

Organization secret for authentication - provided by Parchment

Path Parameters

organization_id
string<uuid>
required

Organization ID

user_id
string<uuid>
required

User ID

Body

application/json

User data to update in Parchment

The body is of type any.

Response

User updated successfully