Get Status Histories

This endpoint retrieves the chronological status history of a specified user profile in the Netevia banking system. It returns a list of all status transitions the profile has undergone, including timestamps and status descriptions. This makes it useful for auditing, compliance tracking, and monitoring profile lifecycle changes.

Endpoint

GET /netevia/profile/getStatusHistory

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 you need to audit the full lifecycle of a user profile, such as reviewing underwriting decisions, tracking approval or denial sequences, or generating compliance reports. It is particularly relevant during onboarding workflows to verify that a profile progressed through the expected status stages. Partners can also use this to investigate support cases involving account status disputes.

Query Parameters

Response

200 OK

Returns an array of status history records, each representing one status change event for the profile.

bankingStatus values:

[
  {
    "id": 1042,
    "neteviaUserProfileId": 3819,
    "highNoteProfileId": 204,
    "bankingStatus": "Approved",
    "notes": "All documents verified. Underwriting complete.",
    "createdDate": "2025-11-14T10:32:00Z"
  },
  {
    "id": 1041,
    "neteviaUserProfileId": 3819,
    "highNoteProfileId": 204,
    "bankingStatus": "ApprovedUW",
    "notes": null,
    "createdDate": "2025-11-14T09:15:00Z"
  },
  {
    "id": 1040,
    "neteviaUserProfileId": 3819,
    "highNoteProfileId": 204,
    "bankingStatus": "PendingUW",
    "notes": "Submitted for underwriting review.",
    "createdDate": "2025-11-13T16:45:00Z"
  }
]

Error Codes

Common Mistakes

• Omitting the profileId query parameter may return an empty array or cause unexpected results rather than an error; always pass a valid profile ID.
• Using an expired Bearer token will return a 401 error — ensure you refresh the token before making requests.
• Expecting a single object in the response instead of an array; this endpoint always returns an array even if there is only one history record.
• Interpreting highNoteProfileId as a customer-facing field — this is an internal reference and should not be exposed to end users.

Related Endpoints

• GET /netevia/profile/getProfile — Retrieve the current profile details for a user.
• POST /netevia/profile/createProfile — Create a new user profile.
• PUT /netevia/profile/updateProfile — Update an existing user profile.
• GET /netevia/profile/getStatusHistory — This endpoint.

Example

curl -X GET "https://api.banking.netevia.dev/netevia/profile/getStatusHistory?profileId=3819" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"