User Management Endpoints
Read user
Retrieves a specific user from Parchment
GET
cURL
Response Examples
Success Response - Provider User (200 OK)
Success Response - Non-Provider User (200 OK)
User Not Found (404 Not Found)
Invalid Parameters (400 Bad Request)
Unauthorized (401)
Insufficient Permissions (403 Forbidden)
Response Fields
Success Response Data
| Field | Type | Description |
|---|---|---|
user_id | string | Parchment’s unique user identifier |
email | string | User’s email address |
full_name | string | User’s full display name |
access_roles | array | Array of user roles (admin, provider, etc.) |
details | object | Core user demographics (always present — see below) |
provider_details | object | Provider-specific details (only if user has “provider” or “rx_queue_manager” role) |
Details Object
| Field | Type | Description |
|---|---|---|
given_name | string | User’s given name |
family_name | string | User’s family name |
title | string | null | Professional title |
date_of_birth | string | null | ISO 8601 timestamp; null for non-provider users |
sex | string | null | M/F/I/O; null for non-provider users |
Provider Details Object (when access_roles includes “provider”)
| Field | Type | Description |
|---|---|---|
hpii_number | string | Healthcare Provider Individual Identifier |
prescriber_number | string | Prescriber number |
prescriber_type | string | Prescriber type (M/N/D/P/T) |
ahpra_number | string | AHPRA registration number |
qualifications | string | Professional qualifications |
hospital_provider_number | string | Hospital provider number |
family_name | string | Provider’s family name |
given_name | string | Provider’s given name |
date_of_birth | string | Date of birth (YYYY-MM-DD format) |
sex | string | Sex (M/F/I/O) |
phone | string | Australian phone number |
australian_address | object | Provider’s Australian address |
Australian Address Object
| Field | Type | Description |
|---|---|---|
street_number | string | Street number |
street_name | string | Street name |
suburb | string | Suburb |
state | string | Australian state |
postcode | string | Australian postcode |
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 |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
organization_id | string | Yes | Organization identifier |
user_id | string | Yes | User identifier |
Status Codes
| Code | Status | Description |
|---|---|---|
200 | OK | User details retrieved successfully |
400 | Bad Request | Invalid request format or missing parameters |
401 | Unauthorized | Authentication required or token invalid or scope invalid |
404 | Not Found | User not found |
500 | Internal Server Error | Unexpected server error |
Integration Notes
- Store Request ID: Always log the
requestIdfor debugging support requests - Handle 404 Status: Check if the user exists before attempting to read
- Permission Requirements: Ensure your API token has the
READ_USERscope - Organization Access: You can only read users from organizations you have access to
- Provider Data Availability: If provider details cannot be retrieved,
provider_detailswill benull - Caching: Consider caching user data with appropriate TTL to reduce API calls
- Role-Based Fields: Non-provider users will not have the
provider_detailsfield in the response
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
Response
User retrieved successfully
cURL

