/api/v1/banking/status

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

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

ParameterTypeRequiredDescription
profileIdinteger (int32)YesUnique identifier of the banking services application profile

Response

200 OK

FieldTypeDescription
dataarray of StatusUpdateChronological list of status transitions for the profile
data[].idintegerUnique identifier for this status record
data[].highNoteProfileIdintegerExternal banking provider profile ID (HighNote)
data[].bankingStatusstring (enum)Current status value: New, Submitted, PendingUW, ApprovedUW, Closed, Cancelled, Pending_Review, Denied, Approved, Pending, InReview
data[].notesstringFree-text notes accompanying this status change
data[].createdDatestring (date-time)Timestamp of the status change (ISO 8601)
requestIdintegerEcho of the internal request ID
successbooleantrue if the call succeeded
errorstringError message if success is false
validationErrorsarrayField-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

CodeWhen it happens
400profileId query parameter is missing or not a valid integer
401Invalid or missing Basic Auth credentials
403User does not have permission for this operation
404No status records found for the given profileId
500Internal server error

Common Mistakes

  • Forgetting the profileId query parameter — this endpoint requires it even though the source docs describe it as having no parameters. The OpenAPI spec clearly defines profileId as a required query param.
  • Confusing bankingStatus enum values (e.g., Pending vs Pending_Review vs PendingUW) — these are distinct states; PendingUW means queued for underwriting, while Pending_Review means 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 profileId
  • GET /api/v1/banking/notes/{profileId} — Retrieve reviewer notes associated with the application
  • POST /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"
Query Params
int32
required
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
text/json