Skip to main content
POST
Create a Meridian user for a partner

Authorizations

X-Meridian-Signature
string
header
required

Meridian HMAC header authentication, for server-to-server calls.

Required headers:

  • X-Meridian-Api-Key
  • X-Meridian-Timestamp
  • X-Meridian-Program-Id
  • X-Meridian-User-Id (MULTI_USER integrations only)
  • X-Meridian-Signature

X-Meridian-Signature is the HMAC SHA-256 signature of the canonical request string, computed per request. See Authentication for how to construct it.

Headers

X-Meridian-Api-Key
string
required

Server-to-server (HMAC) requests only. Partner API key issued by Meridian during provisioning.

X-Meridian-Timestamp
string
required

Server-to-server (HMAC) requests only. Current time in milliseconds since the Unix epoch. Must be within 60 seconds of the request.

X-Meridian-Program-Id
string
required

Server-to-server (HMAC) requests only. Identifies the program context for the request.

X-Meridian-User-Id
string

Server-to-server (HMAC) requests only. Identifies the Meridian user targeted by the request. Required for MULTI_USER integrations; omit for SINGLE_USER.

Body

application/json

Person or business user payload

Meridian person user creation payload

externalId
string
required

Partner-defined external identifier for the user

Example:

"partner-user-123"

person
Person Profile · object
required

Person profile data

type
enum<string>
required

Type of Meridian user being created

Available options:
PERSON,
BUSINESS

Response

The id of the newly created user

Response containing the created Meridian user identifier

userId
string
required

Created Meridian user identifier

Example:

"user_123"