Actions215
- V1 > Bank Billets Actions
- V1 > Bank Billet Accounts Actions
- V1 > Bank Billet Batches Actions
- V1 > Bank Billet Batch Exports Actions
- V1 > Bank Billet Discharges Actions
- V1 > Bank Billet Payments Actions
- V1 > Bank Billet Registrations Actions
- V1 > Bank Billet Remittances Actions
- V1 > Customers Actions
- V1 > Customer Subscriptions Actions
- V1 > Discharges Actions
- V1 > Email Deliveries Actions
- V1 > Events Actions
- V1 > Imports Actions
- V1 > Installments Actions
- V1 > Remittances Actions
- V1 > Reports Actions
- V1 > SMS Deliveries Actions
- V1 > User Info Actions
- V1 > Webhook Deliveries Actions
- V1 > Webhooks Actions
- Admin > Users Actions
- Admin > Connections Actions
- Admin > Certificates Actions
- Admin > Subaccounts Actions
- Charge > PIX Actions
- Charge > PIX Accounts Actions
- Data > Bank Billet Queries Actions
- EDI > EDI Boxes Actions
- Financial > Accounts Actions
- Financial > Balances Actions
- Financial > Commands Actions
- Financial > Statement Transactions Actions
- Financial > Transaction Imports Actions
- Financial > Providers Actions
- Payment > Bank Billets Actions
- Payment > Bank Billet Batches Actions
- Payment > Batches Actions
- Payment > DARFs Actions
- Payment > DARF Batches Actions
- Payment > PIX Actions
- Payment > PIX Batches Actions
- Payment > Utilities Actions
- Payment > Utility Batches Actions
- Transfer > Batches Actions
- Transfer > Internal Actions
- Transfer > Internal Batches Actions
- Transfer > PIX Actions
- Transfer > PIX Batches Actions
- Transfer > TED Actions
- Transfer > TED Batches Actions
Overview
This node allows you to interact with the Kobana API specifically for managing PIX charge accounts under the "Charge > PIX Accounts" resource. The "Update" operation lets you modify an existing PIX account by specifying its ID and providing a JSON request body with the fields to update.
Typical use cases include:
- Updating details of a PIX account such as account information or configuration.
- Automating updates to PIX accounts in bulk workflows.
- Integrating PIX account management into larger financial automation processes.
For example, you might update the name or status of a PIX account by providing the account ID and a JSON object with the new values.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the PIX account to update (required). |
| Additional Fields | Optional JSON object containing extra fields for the request (flexible additional data). |
| Request Body | Required JSON object representing the data to update on the PIX account. |
Output
The node outputs the JSON response returned by the Kobana API after updating the PIX account. This typically includes the updated PIX account details such as its ID, updated fields, timestamps, and status.
No binary data output is involved in this operation.
Dependencies
- Requires an active Kobana API credential with appropriate permissions.
- The node uses the Kobana API endpoint, switching between production and sandbox environments based on the credential environment setting.
- No other external dependencies are required.
Troubleshooting
- Invalid ID: If the provided ID does not correspond to an existing PIX account, the API will return an error. Verify the ID is correct.
- Malformed JSON: The "Request Body" must be valid JSON. Invalid JSON syntax will cause parsing errors.
- Permission Errors: Ensure the API credential has rights to update PIX accounts.
- API Endpoint Issues: Confirm that the environment (production vs sandbox) matches your intended target.
- Additional Fields Format: If using "Additional Fields", ensure the JSON structure is correct and supported by the API.
Common error messages usually come from the Kobana API and should be interpreted according to their content, e.g., "Not Found" for invalid IDs or "Bad Request" for malformed input.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- PIX Payment System Overview (for understanding PIX context)
If you need further details about other operations or resources, feel free to ask!
