User Registration for Personal Accounts

This endpoint registers a new personal account holder within the Netevia Banking platform. Partners submit the individual's identity, contact, and address details to create the account. On success, a profile ID and optional financial account ID are returned for use in subsequent API calls.

Endpoint

POST /api/users/personal

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when onboarding a new individual customer to the platform. This is the first step in the personal account lifecycle — the returned profileId is required for opening financial accounts, issuing cards, and initiating transfers on behalf of the customer. Submit complete and accurate identity data to avoid underwriting failures.

Request Body

{
  "givenName": "Jane",
  "familyName": "Smith",
  "middleName": "Marie",
  "email": "[email protected]",
  "phone": "5551234567",
  "ssn": "XXX-XX-XXXX",
  "dateOfBirth": "1990-03-22T00:00:00Z",
  "streetAddress": "123 Main St",
  "extendedAddress": "Apt 4B",
  "postalCode": "30301",
  "locality": "Atlanta",
  "state": 11,
  "password": "S3cur3P@ssword!",
  "login": "janesmith90",
  "partnerId": 1001
}

Response

200 OK

The response may be one of two shapes depending on whether a financial account was simultaneously opened:

boardingresponse (base shape):

changeLog item fields:

openfinancialaccountresponse (extended shape, when a financial account is also opened):

{
  "profileId": 48291,
  "success": true,
  "errors": null,
  "changeLog": [
    {
      "requestType": 1,
      "changes": "Personal account holder created successfully."
    }
  ],
  "financialAccountId": "XXXXXXXXXX"
}

Error Codes

Common Mistakes

• Submitting the SSN with dashes (e.g., 123-45-6789) instead of digits only (123456789). The field requires a 9-digit string matching the valid SSN pattern.
• Formatting the phone number with parentheses or dashes (e.g., (555) 123-4567). Use exactly 10 consecutive digits: 5551234567.
• Using an incorrect dateOfBirth format. The field requires ISO 8601 date-time format — always include the time portion (e.g., 1990-03-22T00:00:00Z).
• Passing a string representation for state instead of the integer enum value. Refer to the state enum mapping to supply the correct integer.
• Omitting partnerId when registering on behalf of a specific partner channel — this may cause the account to be assigned to the wrong partner context.

Related Endpoints

• POST /api/users/business — Register a new business account holder
• POST /api/auth/v2 — Obtain a Bearer token for authentication
• POST /api/auth/refresh — Refresh an existing Bearer token
• GET /api/users/personal/{profileId} — Retrieve personal account holder details
• PUT /api/users/personal/{profileId} — Update personal account holder information
• POST /api/financialaccounts — Open a financial account for an existing profile

Example

curl -X POST https://api.banking.netevia.dev/api/users/personal \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "givenName": "Jane",
    "familyName": "Smith",
    "middleName": "Marie",
    "email": "[email protected]",
    "phone": "5551234567",
    "ssn": "123456789",
    "dateOfBirth": "1990-03-22T00:00:00Z",
    "streetAddress": "123 Main St",
    "extendedAddress": "Apt 4B",
    "postalCode": "30301",
    "locality": "Atlanta",
    "state": 11,
    "password": "S3cur3P@ssword!",
    "login": "janesmith90",
    "partnerId": 1001
  }'