| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Get Banking Application Statuses
Returns an array of status update records for a specific banking services application, ordered chronologically. Each record captures a point-in-time status transition along with any accompanying notes. Use this endpoint to track where an Instant Funding or banking onboarding application stands in the approval pipeline.
Endpoint
GET /api/v1/banking/status
Authentication
Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:
Authorization: Basic {base64(username:password)}
When to use
Poll this endpoint after submitting a banking application to determine whether it has moved from Submitted to PendingUW, ApprovedUW, Approved, or another terminal state. ISOs use this alongside GET /api/v1/banking/notes/{profileId} to get a complete picture of the review lifecycle.
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| profileId | integer (int32) | Yes | Unique identifier of the banking services application profile |
Response
200 OK
| Field | Type | Description |
|---|---|---|
| data | array of StatusUpdate | Chronological list of status transitions for the profile |
| data[].id | integer | Unique identifier for this status record |
| data[].highNoteProfileId | integer | External banking provider profile ID (HighNote) |
| data[].bankingStatus | string (enum) | Current status value: New, Submitted, PendingUW, ApprovedUW, Closed, Cancelled, Pending_Review, Denied, Approved, Pending, InReview |
| data[].notes | string | Free-text notes accompanying this status change |
| data[].createdDate | string (date-time) | Timestamp of the status change (ISO 8601) |
| requestId | integer | Echo of the internal request ID |
| success | boolean | true if the call succeeded |
| error | string | Error message if success is false |
| validationErrors | array | Field-level validation errors if any |
{
"data": [
{
"id": 301,
"highNoteProfileId": 44821,
"bankingStatus": "Submitted",
"notes": "Application received and queued for underwriting review.",
"createdDate": "2025-04-01T08:00:00Z"
},
{
"id": 302,
"highNoteProfileId": 44821,
"bankingStatus": "PendingUW",
"notes": "Assigned to underwriting team. Additional documents may be requested.",
"createdDate": "2025-04-02T11:30:00Z"
},
{
"id": 303,
"highNoteProfileId": 44821,
"bankingStatus": "Approved",
"notes": "All documentation verified. Account approved.",
"createdDate": "2025-04-05T14:45:00Z"
}
],
"requestId": 77403,
"success": true,
"error": null,
"validationErrors": []
}Error Codes
| Code | When it happens |
|---|---|
| 400 | profileId query parameter is missing or not a valid integer |
| 401 | Invalid or missing Basic Auth credentials |
| 403 | User does not have permission for this operation |
| 404 | No status records found for the given profileId |
| 500 | Internal server error |
Common Mistakes
- Forgetting the
profileIdquery parameter — this endpoint requires it even though the source docs describe it as having no parameters. The OpenAPI spec clearly definesprofileIdas a required query param. - Confusing
bankingStatusenum values (e.g.,PendingvsPending_ReviewvsPendingUW) — these are distinct states;PendingUWmeans queued for underwriting, whilePending_Reviewmeans an internal reviewer needs to act. - Assuming a single status record will be returned — the response is an array of all historical status transitions, not just the most recent one.
Related Endpoints
POST /api/v1/banking/submit— Submit the banking application that generates the profileIdGET /api/v1/banking/notes/{profileId}— Retrieve reviewer notes associated with the applicationPOST /api/v1/banking/submit/personal— Submit a personal banking application for agents or sole proprietors
Example
curl -X GET "https://hq.staging.netevia.dev/api/v1/banking/status?profileId=7823" \
-H "Authorization: Basic $(echo -n 'username:password' | base64)" \
-H "Accept: application/json"