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 operation updates (patches) an existing account in the Straddle system by its Account Id. It allows modifying various aspects of the account such as business profile, account type, capabilities, settings, terms of service, access level, metadata, and external identifiers.
Typical use cases include:
- Updating business information or contact details for an account.
- Changing account capabilities like payment types or customer types supported.
- Adjusting account settings related to charges or payouts.
- Modifying metadata or adding external references for integration purposes.
For example, a user might update the business address and support channels after a company relocation or enable new payout options for an account.
Properties
| Name | Meaning |
|---|---|
| Account Id | The unique identifier of the account to update (required). |
| Request Id | Optional client-generated identifier to trace and debug this specific request (sent as header). |
| Correlation Id | Optional client-generated identifier to trace and debug a series of related requests (header). |
| Business Profile | JSON object containing business profile information including address, industry, and support channels. |
| Account Type | Type of the account; options are "Unknown" or "Business". |
| Capabilities | JSON object describing capabilities such as supported payment types, customer types, and consent types. |
| Settings | JSON object with account settings related to charges and payouts. |
| Terms Of Service | JSON object representing terms of service information. |
| Access Level | Access level of the account; options are "Standard" or "Managed". |
| Speedchex Merchant Id | String identifier for Speedchex merchant integration. |
| Metadata | JSON object for user-defined key-value pairs to store custom metadata. |
| External Id | External identifier string for referencing the account outside the system. |
Output
The node outputs the updated account data in the json field of the output item. This JSON reflects the current state of the account after applying the patch, including all updated fields.
No binary data is produced by this operation.
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., production or sandbox).
- Proper permissions to update accounts via the Straddle API are necessary.
Troubleshooting
- Invalid Account Id: If the provided Account Id does not exist or is malformed, the API will return an error. Verify the Account Id before making the request.
- Malformed JSON Inputs: Fields like Business Profile, Capabilities, Settings, Terms Of Service, and Metadata expect valid JSON objects. Invalid JSON will cause parsing errors.
- Missing Required Fields: Some nested objects have required properties (e.g., address line1, city, state, postal_code, country in Business Profile). Omitting these may cause validation errors.
- Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- API Rate Limits: Frequent updates may hit rate limits imposed by the API provider; handle such errors by retrying after some delay.
Links and References
- Straddle API Documentation (hypothetical link)
- JSON Schema definitions for Business Profile, Capabilities, Settings, etc., are embedded in the node for reference and validation.