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 allows you to create a "Capability Request" in the Straddle API. Capability Requests are typically used to configure or update account capabilities related to payments, payouts, and other financial services. This operation is useful when you want to programmatically request enabling or modifying specific capabilities for an account, such as charges, payouts, internet access, individuals, businesses, or signed agreements.
Practical examples include:
- Enabling ACH or card payment capabilities for a merchant account.
- Configuring payout options like same-day payouts.
- Submitting compliance-related information about individuals or businesses associated with the account.
- Attaching signed agreement data to the capability request.
Properties
| Name | Meaning |
|---|---|
| Account Id | The unique identifier of the account for which the capability request is being created. |
| 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). |
| Charges | JSON object containing charges-related information and settings. |
| Payouts | JSON object containing payouts-related information and settings. |
| Internet | JSON object containing internet-related information. |
| Individuals | JSON object containing information about individuals related to the capability request. |
| Businesses | JSON object containing information about businesses related to the capability request. |
| Signed Agreement | JSON object containing signed agreement details relevant to the capability request. |
Note: The JSON properties (Charges, Payouts, Internet, Individuals, Businesses, Signed Agreement) expect valid JSON strings that will be parsed and sent in the request body.
Output
The node outputs the response from the Straddle API after creating the capability request. The output is structured as JSON data representing the newly created capability request resource, including all submitted fields and any additional metadata returned by the API.
If the API returns binary data (not indicated here), it would be included accordingly, but based on the provided code and properties, the output is primarily JSON.
Dependencies
- Requires an API key credential for authenticating with the Straddle API.
- The base URL for API requests is dynamically set based on the environment credential parameter.
- The node sends HTTP requests with
Accept: application/jsonandContent-Type: application/jsonheaders. - No other external dependencies are indicated.
Troubleshooting
- Invalid JSON in input properties: Since several properties require JSON strings, invalid JSON syntax will cause parsing errors. Ensure all JSON inputs are well-formed.
- Missing required Account Id: The Account Id property is mandatory; omitting it will likely result in an error from the API.
- API authentication errors: If the API key credential is missing or invalid, the request will fail with authentication errors.
- Header tracing IDs: If using Request Id or Correlation Id headers, ensure they are unique and correctly formatted to aid debugging.
- API endpoint errors: Network issues or incorrect environment configuration can cause failures connecting to the API.
Links and References
- Straddle API Documentation (Assumed official docs for more details on capability requests)
- n8n documentation on HTTP Request Node for understanding how headers and JSON bodies are handled.
This summary is based solely on static analysis of the provided source code and property definitions.