Actions81
- Users Actions
- Organizations Actions
- Representatives Actions
- Bridge Actions
- Platforms Actions
- Tools Actions
- User Invites Actions
- Customers Actions
- Paykeys Actions
- Reports Actions
- Charge Actions
- Funding Events Actions
- Payments Actions
- Payout Actions
- Accounts Actions
- Get Account By Id
- put__v1_accounts_account_id
- Create Account
- get__v1_accounts
- post__v1_accounts_account_id_onboard
- post__v1_accounts_account_id_simulate
- patch__v1_internal_accounts_account_id
- get__v1_internal_accounts_account_id
- patch__v1_internal_accounts_account_id_status
- get__v1_internal_accounts_account_id_settings
- Capability Requests Actions
- Linked Bank Accounts Actions
Overview
This node interacts with the Straddle API to retrieve a paginated list of representatives associated with a specific account. It is useful in scenarios where you need to programmatically access detailed information about representatives linked to an account, such as for compliance checks, reporting, or integration with CRM systems.
For example, you might use this node to:
- Fetch all representatives for a given account to display their details in a dashboard.
- Automate compliance workflows by retrieving representative data and verifying their status.
- Integrate representative information into other business processes or databases.
Properties
| Name | Meaning |
|---|---|
| Account Id | The unique identifier of the account to list representatives for. |
| Page Number | Results page number. Starts at page 1. Default value: 1 |
| Page Size | Number of results per page. Default value: 100. Maximum allowed: 1000 |
| Sort By | Field to sort the results by. Default value: "id" |
| Sort Order | Sort order direction. Options: "asc" (ascending), "desc" (descending). Default: "asc" |
| Request Id | Optional client-generated identifier to trace and debug a request (sent as HTTP header) |
| Correlation Id | Optional client-generated identifier to trace and debug a series of requests (HTTP header) |
Output
The node outputs JSON data containing a list of representatives matching the query parameters. Each representative object includes detailed structured information such as:
- Address details (line1, line2, city, state, postal code, country)
- Compliance profile (date of birth, SSN last 4 digits, ID document info)
- Contact and support channels
- Capabilities and settings related to payments and customer types
- Bank account details and verification status
- Status details including messages and reasons for current status
The output structure reflects the comprehensive schema defined by the Straddle API for representatives, enabling downstream nodes or workflows to consume rich representative data.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Straddle API.
- The base URL for API requests depends on the configured environment (e.g., sandbox or production).
- Proper network connectivity to the Straddle API endpoint is necessary.
Troubleshooting
- Invalid or missing Account Id: Ensure the Account Id provided is correct and exists in the system; otherwise, the API may return empty results or errors.
- Pagination issues: If requesting pages beyond available data, the response may be empty. Adjust
Page Numberaccordingly. - API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Rate limiting or throttling: If many requests are made rapidly, the API might throttle calls. Implement retry logic or respect rate limits.
- Incorrect header values: Custom headers like
Request IdandCorrelation Idshould be valid strings if used; malformed headers could cause request failures.
Links and References
- Straddle API Documentation (hypothetical link for reference)
- Pagination and sorting concepts in REST APIs
- Best practices for API authentication and error handling