Skip to main content
POST
Create and screen a profile

Authorizations

x-api-key
string
header
required

The Minerva API key used for this integration. Manage API keys in the Minerva dashboard under Administration > Developers.

Body

application/json

Profile onboarding request

address1
string

Address line 1 of the profile's known place of residence. Combined with address line 2 to form the "address" value in the screening input.

Example:

"123 Main Street"

address2
string

Address line 2 of the profile's known place of residence. Combined with address line 1 to form the "address" value in the screening input.

Example:

"Apt 4B"

addressCity
string

The city of the profile's known place of residence. Supply the full city name.

Example:

"Toronto"

addressPostalCode
string

The postal code of the known place of residence for the profile.

Example:

"M5V1C2"

addressState
string

The ISO-2 code or full state name of the place of residence of the profile.

Example:

"ON"

allowlistUntil
string

Optional. Creates the profile in an allowlisted state, so ongoing monitoring generates no flags until the date you specify in "YYYY/MM/DD" format. If omitted, the profile is created in a non-allowlisted state, where later screens may generate review tasks.

Example:

"2024/12/25"

archived
boolean
Example:

false

assignee
string
Example:

"12345-123"

country
string

The known country of residence for the profile.

Example:

"Canada"

createdBy
string
Example:

"12345-123"

dateOfBirth
string

The date of birth of the profile in "YYYY/MM/DD" format.

Example:

"1990/01/01"

email
string

The email of the profile. Screening does not use this value, but you can store it on the persistent profile record for cross-referencing.

Example:

"john.smith@example.com"

externalId
string

Optional external reference ID supplied at profile creation, so the profile can be cross-referenced with external systems.

Example:

"123456789"

firstName
string

The first name of the profile. Combined with the last name to form the "name" value in the screening input. Deprecated: use the name field instead.

Example:

"John"

kind
string

One of "individual" or "organization", the entity type in Minerva screening. An individual is a natural person; an organization is an entity.

Example:

"individual"

lastName
string

The last name of the profile. Combined with the first name to form the "name" value in the screening input. Deprecated: use the name field instead.

Example:

"Smith"

middleName
string

The middle name of the profile. Optional. Combined with the first and last names to form the "name" value in the screening input. Deprecated: use the name field instead.

Example:

"Michael"

monitored
string

One of "monitored", "not_monitored", or an empty string. When "monitored", the profile is enrolled in ongoing monitoring, where screening on a regular cadence may generate review tasks for potential risks.

Example:

"monitored"

name
string

Legacy fields (keeping for backward compatibility)

Example:

"John Smith"

nationality
string

The nationality of the profile, being one of the known citizenships of the profile.

Example:

"American"

occupation
string

The known occupation or job title of the natural person.

Example:

"Software Engineer"

organization
string

The affiliated organization or employer of the natural person.

Example:

"MinervaAI"

phone
string

The phone number in e.164 standard format for the profile (+15555555555)

Example:

"+15555555555"

sex
string

The known sex of the natural person, as reported on an onboarding document. Use "f" for Female, "m" for Male, "o" for Other, or leave empty for Unknown.

Example:

"m"

status
string
Example:

"pending"

updatedBy
string
Example:

"12345-123"

profileGroupIds
string[]

Workspace-scoped profile group IDs assigned to this profile for dynamic risk segmentation. A profile can belong to multiple groups.

Example:
profileCustomFields
object

Organization-defined profile values keyed by immutable definition key. Every write retrieves the latest definitions before validation. Unknown or archived keys and wrong types return HTTP 400; if definitions cannot be retrieved, the write is rejected. Omitted keys remain unchanged on PATCH, and null clears one named value. Required fields are enforced on profile creation and onboarding.

Example:

Response

201 - application/json

Profile created successfully

msg
string
Example:

"OK"

result
object
status
integer
Example:

201