/api/v1/banking/notes/{profileId}

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

Get Banking Application Notes

Retrieves all notes and history entries attached to a specific banking services application profile. Notes may include reviewer feedback, status updates, clarifications requested by underwriting, and internal administrative comments. Use this endpoint to monitor the progress of a submitted banking application and identify any required follow-up actions.

Endpoint

GET /api/v1/banking/notes/{profileId}

Authentication

Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:

Authorization: Basic {base64(username:password)}

When to use

After submitting a banking services application via POST /api/v1/banking/submit, poll this endpoint to track reviewer notes and any action items. ISOs and administrative teams use this to stay informed about approval delays, document requests, or verification requirements during the banking onboarding process.

Path Parameters

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

Response

200 OK

FieldTypeDescription
dataarray of BankingHistoryList of notes/history entries for the profile
data[].idintegerUnique identifier for the history entry
data[].profileIdintegerBanking profile this note belongs to
data[].profileCreatedIdintegerID of the profile creation record
data[].createdBystringUsername or name of the person who added the note
data[].createdstring (date-time)Timestamp when the note was created (ISO 8601)
data[].messagestringText content of the note
data[].typestring (enum)Category of the note: CustomerService, Risk, Equipment, POS, Other, TechSupport, Accounting, Underwriting, Application, BusinessInfo, FinancialAccounts, PaymentCards, Rewards, ConnectAccount, DisconnectAccount, AccessToProfile, BankingProfileSettings, AccountAccessLog, Transfer
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": 1041,
      "profileId": 7823,
      "profileCreatedId": 502,
      "createdBy": "jane.smith",
      "created": "2025-03-12T10:22:00Z",
      "message": "Additional verification required for tax documents. Please upload a copy of the IRS EIN letter.",
      "type": "Underwriting"
    },
    {
      "id": 1052,
      "profileId": 7823,
      "profileCreatedId": 502,
      "createdBy": "john.reviewer",
      "created": "2025-03-14T09:05:00Z",
      "message": "Banking details verified. Awaiting final compliance sign-off.",
      "type": "FinancialAccounts"
    }
  ],
  "requestId": 98120,
  "success": true,
  "error": null,
  "validationErrors": []
}

Error Codes

CodeWhen it happens
400profileId is missing, non-numeric, or otherwise invalid
401Invalid or missing Basic Auth credentials
403User does not have permission for this operation
404No notes found for the given profileId, or profile does not exist
500Internal server error

Common Mistakes

  • Passing a string value for profileId — it must be an integer.
  • Calling this endpoint before a banking application has been submitted; no notes exist yet for a profile that has never been submitted.
  • Confusing this endpoint with the boarding notes endpoint (GET /api/v1/boarding/notes) — this one is specific to banking/Instant Funding applications.
  • Not checking success: false cases where the response body contains an error string rather than data.

Related Endpoints

  • POST /api/v1/banking/submit — Submit the banking services application that generates the profileId
  • GET /api/v1/banking/status — Check the current approval status of the banking application
  • POST /api/v1/banking/submit/personal — Submit a personal (agent/sole proprietor) banking application

Example

curl -X GET https://hq.staging.netevia.dev/api/v1/banking/notes/7823 \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)" \
  -H "Accept: application/json"
Path 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