Skip to main content
POST
cURL

Response Examples

Success Response (201 Created)

Partial Success - User Already Exists (201 Created)

Partial Success = Provider Already Exists (201 Created)

Partial Success - Provider Creation Failed (201 Created)

Validation Error (422 Unprocessable Entity)

Unauthorized (401)

Response Fields

Success Response Data

Common Response Fields

All responses include these standard fields:

Status Codes

Field Validation Requirements

Required Fields

Optional Fields

Phone Number Format

The phone field accepts Australian phone numbers in the following formats: ✅ Valid Examples:
  • 0412345678 - Mobile number (domestic format)
  • 0312345678 - Melbourne landline (domestic format)
  • 0212345678 - Sydney landline (domestic format)
  • 0712345678 - Brisbane landline (domestic format)
  • 0812345678 - Adelaide landline (domestic format)
  • 61412345678 - International mobile (without + prefix)
  • +61312345678 - International landline (with + prefix)
❌ Invalid Examples:
  • 0123456789 - Starts with 1 (invalid area code)
  • 04123456789 - Too many digits
  • 041234567 - Too few digits
  • 04-1234-5678 - Contains formatting characters
  • +1234567890 - Non-Australian number

String Length Requirements

  • Family Name: 1-255 characters, cannot be empty
  • Given Name: 1-255 characters, cannot be empty
  • HPII Number: 16 digits exactly
  • Prescriber Number: 1-10 characters
  • AHPRA Number: 1-15 characters
  • Provider Number: 1-15 characters
  • Qualifications: 1-255 characters

Sex

  • M (Male)
  • F (Female)
  • I (Indeterminate)
  • N (Not-stated)

Access Roles

Valid values for access_roles array:
  • admin (Administrative access)
  • provider (Healthcare provider access)
  • receptionist (Can read patient demographics)
  • rx_reader (Can reissue scripts)
  • rx_queue_manager (Can manage the prescription queue on behalf of prescribers)
When the provider or rx_queue_manager role is included, additional fields become required:
  • provider: date_of_birth, sex, hpii_number, qualifications, and prescriber_type (plus prescriber_number unless prescriber_type is “T”)
  • rx_queue_manager: date_of_birth, sex, hpii_number, and qualifications (prescriber_type and prescriber_number are not required)

Prescriber Types

Valid values for prescriber_type when role is “provider”:
  • M (Medical Practitioner)
  • E (Eye/Optometrist)
  • U (Nurse)
  • F (Midwife)
  • D (Dentist)
  • V (Vetinarian)
  • T (Podiatrist)
  • C (Pharmacist)

Integration Notes

  1. Store Request ID: Always log the requestId for debugging support requests
  2. Handle 202 Status: A 202 response indicates demographic conflicts were found but a matching user was returned
  3. Validation Errors: Use the error.validation array to display field-specific error messages
  4. Partner User ID: Must be unique across your organization; use the format returned in external_user_id
  5. URL Access: The returned url provides direct access to the user in the Parchment portal
  6. Provider Role Requirements: When creating users with the provider or rx_queue_manager role, ensure all required identity fields are included (see Access Roles above) — these roles create a provider record attributed to a verified healthcare individual
  7. Phone Validation: Phone numbers must follow Australian format - see validation requirements above

Example Request

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

Body

application/json

User data to add to Parchment

User information to be created

given_name
string
required

User's given name

Example:

"Darlene"

family_name
string
required

User's family name

Example:

"Cameron"

email
string<email>
required

User's email address

Example:

"darlene.cameron@example.com"

partner_user_id
string
required

Partner's unique identifier for the user

Example:

"CLINIKO#USER_12345"

date_of_birth
string<date>

User's date of birth in YYYY-MM-DD format (required if role includes 'provider' or 'rx_queue_manager')

Example:

"1969-10-02"

sex
enum<string>

User's sex (required if role includes 'provider' or 'rx_queue_manager')

Available options:
M,
F,
I,
O
Example:

"F"

phone
string

User's Australian phone number. Must be a valid Australian number with digits only. Supports mobile (04xxxxxxxx) and landline (0[2378]xxxxxxxx) formats. International format with +61 or 61 prefix is also accepted.

Example:

"0412345678"

access_roles
enum<string>[]

List of access roles for the user. Roles 'provider' and 'rx_queue_manager' require additional identity fields (date_of_birth, sex, hpii_number, qualifications); 'provider' additionally requires prescriber_type (and prescriber_number unless prescriber_type is 'T').

Available options:
admin,
provider,
receptionist,
rx_reader,
rx_queue_manager
Example:
hpii_number
string

Healthcare Provider Individual Identifier (required if role includes 'provider' or 'rx_queue_manager')

Example:

"8003614900029560"

prescriber_type
enum<string>

Prescriber type (required if role includes 'provider')

Available options:
M,
N,
D,
P,
T
Example:

"M"

prescriber_number
string

Prescriber number (required if role includes 'provider' and prescriber_type is not 'T')

Example:

"1234567"

qualifications
string

Professional qualifications (required if role includes 'provider' or 'rx_queue_manager')

Example:

"LLB"

title
string

Professional title

Example:

"Dr"

provider_number
string

Medicare provider number

Example:

"123456789"

ahpra_number
string

AHPRA registration number

Example:

"1234567896321"

hospital_provider_number
string

Hospital provider number

Example:

"H123456"

Response

User created successfully

success
boolean
required

Indicates if the request was successful

Example:

true

statusCode
integer
required

HTTP status code

Example:

201

message
string
required

Human-readable success message

Example:

"User created successfully"

data
object
required

User creation response data

timestamp
string<date-time>
required

ISO 8601 timestamp of the response

Example:

"2024-01-15T10:30:00.000Z"

requestId
string
required

Unique identifier for request tracing

Example:

"req_1705312200000_abc123"

code
string

Machine-readable operation code

Example:

"SUCCESS"

pagination
object

Pagination information for list operations