Update Banking Status - Main Profile

This endpoint allows administrators and authorized partners to update the banking application status of a user's main profile in the Netevia banking system. It supports status transitions such as approving, suspending, or reactivating a profile. Only authenticated users with appropriate permissions may invoke this endpoint.

Endpoint

POST /netevia/profile/changeBankingStatus

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 an administrative or support workflow requires modifying the banking status of a customer's main profile — for example, moving a profile from PendingUW to ApprovedUW after underwriting review, suspending an account by setting it to Closed or Cancelled, or reactivating a profile by transitioning it back to Approved. It is also used internally by automated underwriting flows that progress profiles through the approval pipeline.

Query Parameters

BankingStatus Allowed Values

Response

200 OK

The response may return one of two schemas depending on whether a financial account was opened as part of the status change.

BoardingResponse

changeLog item

OpenFinancialAccountResponse (extends BoardingResponse)

{
  "profileId": 10482,
  "errors": null,
  "success": true,
  "changeLog": [
    {
      "requestType": 3,
      "changes": "Banking status updated to Approved"
    }
  ]
}

With financial account opened:

{
  "profileId": 10482,
  "errors": null,
  "success": true,
  "changeLog": [
    {
      "requestType": 3,
      "changes": "Banking status updated to ApprovedUW; financial account created"
    }
  ],
  "financialAccountId": "fa_8c3d2e1f4a9b7056"
}

Error Codes

Common Mistakes

• Passing an invalid BankingStatus string value not in the allowed enum list will result in a 400 error. Use only the exact values listed above.
• Omitting ProfileId when intending to target a specific profile may result in no update being applied or an unintended profile being modified.
• Using an expired Bearer token (lifetime is 10 minutes) will result in a 401 response. Refresh via POST /api/auth/refresh before retrying.
• Attempting to set a status that represents an illogical transition (e.g., moving from Approved back to New) may succeed at the API level but can cause downstream workflow issues — validate status transitions in your business logic.

Related Endpoints

• POST /api/auth/v2 — Obtain a Bearer authentication token
• POST /api/auth/refresh — Refresh an existing Bearer token
• POST /netevia/profile — Create a new main profile
• GET /netevia/profile — Retrieve main profile details

Example

curl -X POST "https://api.banking.netevia.dev/netevia/profile/changeBankingStatus?ProfileId=10482&BankingStatus=Approved&Notes=Underwriting+review+complete&NeteviaUserProfileId=201" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"