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

Time	Status	User Agent
Retrieving recent requests…

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

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 BankingHistory	List of notes/history entries for the profile
data[].id	integer	Unique identifier for the history entry
data[].profileId	integer	Banking profile this note belongs to
data[].profileCreatedId	integer	ID of the profile creation record
data[].createdBy	string	Username or name of the person who added the note
data[].created	string (date-time)	Timestamp when the note was created (ISO 8601)
data[].message	string	Text content of the note
data[].type	string (enum)	Category of the note: `CustomerService`, `Risk`, `Equipment`, `POS`, `Other`, `TechSupport`, `Accounting`, `Underwriting`, `Application`, `BusinessInfo`, `FinancialAccounts`, `PaymentCards`, `Rewards`, `ConnectAccount`, `DisconnectAccount`, `AccessToProfile`, `BankingProfileSettings`, `AccountAccessLog`, `Transfer`
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": 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

Code	When it happens
400	`profileId` is missing, non-numeric, or otherwise invalid
401	Invalid or missing Basic Auth credentials
403	User does not have permission for this operation
404	No notes found for the given `profileId`, or profile does not exist
500	Internal 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"