Skip to main content
Creating an individual end user registers a person on the Diameter platform and immediately kicks off the bank onboarding process for each bank partner you specify. Once the asynchronous onboarding completes, the onboardedInBanks array is populated and the onboardingStatus transitions away from INACTIVE. Use the returned id to reference this end user in all subsequent API calls.

Endpoint

Required scope: com.diameterpay.api/end-users.write

Request Headers

string
required
Bearer token obtained from your OAuth 2.0 token endpoint. Format: Bearer {access_token}
string
required
A UUID v4 string you generate for each unique request. Re-sending the same key within the idempotency window returns the original response without creating a duplicate end user.

Request Body

Required Fields

string
required
UUID v4 of the Diameter product to associate with this end user.
string
required
Individual’s legal first name.
string
required
Individual’s legal last name.
string
required
Individual’s email address. Must be a valid email format.
string
required
Mobile phone number in E.164 format (e.g. +12125551234).
string
required
Date of birth in YYYY-MM-DD format (e.g. 1990-07-15).
string
required
ISO 3166-1 alpha-2 country code representing the individual’s nationality (e.g. US, DE, GB).
string
required
Type of government-issued identification. One of: PASSPORT, DRIVING_LICENSE, NATIONAL_ID_CARD, SSN, ITIN, EIN, OTHER_ID.
string
required
The identifier number on the chosen identity document.
string
required
ISO 3166-1 alpha-2 country code that issued the identity document.
string
required
Politically Exposed Person status. One of: YES, NO.
object
required
The individual’s primary residential address.
array
required
List of bank partners to onboard this end user with. Accepted values: PORTAGE, SLOVAK_SAVINGS_BANK.

Optional Fields

string
Individual’s middle name. When provided, it is included in the auto-built fullName.
string
Your system’s internal identifier for this user. Maximum 255 characters. Useful for correlating Diameter records with your own database.
integer
Numeric code representing the end user’s business activity in your system.
string
The date this user became active in your system (YYYY-MM-DD).
string
Individual’s gender. One of: MALE, FEMALE.
object
Mailing address if different from primaryAddress. Accepts the same fields as primaryAddress.
fullName is deprecated as an input field. It is automatically constructed by concatenating firstName, middleName (if provided), and lastName. Any value you send for fullName in the request body is ignored.

Response

Returns 201 Created with the newly created IndividualEndUserOutput object.
string
Diameter-assigned UUID v4 for this end user. Use this in all subsequent requests.
string
UUID of the associated product.
string
Individual’s first name.
string
Individual’s middle name, if provided.
string
Individual’s last name.
string
Auto-built full name combining firstName, optional middleName, and lastName.
string
Individual’s email address.
string
Mobile phone in E.164 format.
string
Date of birth in YYYY-MM-DD format.
string
ISO 3166-1 alpha-2 nationality code.
string
Identity document type.
string
Identity document number.
string
ISO 3166-1 alpha-2 code of the country that issued the ID.
string
PEP status: YES or NO.
string
Gender, if provided.
string
Overall onboarding status. Starts as INACTIVE immediately after creation; transitions as bank onboarding progresses.
array
List of bank partners where onboarding has completed. Empty immediately after creation.
array
Array of address objects associated with this end user, including primaryAddress and optional mailingAddress.
string
Your internal identifier, if provided.
integer
Internal activity code, if provided.
string
Internal start date, if provided.
string
ISO 8601 timestamp of when the end user was created.
string
ISO 8601 timestamp of the most recent update.

Example Request

Example Response