Guru Digital Manager icon

Guru Digital Manager

Interact with Guru Digital Manager API

Actions39

Transaction → Delete

AI-generated

Overview

This node integrates with the Guru Digital Manager API to manage various resources such as contacts, transactions, subscriptions, and more. Specifically for the Transaction - Delete operation, it allows users to delete a transaction by its unique ID. This is useful in scenarios where a transaction needs to be removed from the system, for example, when a transaction was created by mistake or needs to be invalidated.

Practical examples:

  • Automatically deleting test transactions after running integration tests.
  • Removing canceled or fraudulent transactions from your records.
  • Cleaning up old or obsolete transactions based on business rules.

Properties

Name Meaning
Transaction ID The unique identifier of the transaction to delete (e.g., tr_043tzaioaeBMAxAnG). You can obtain valid IDs using the "Get All" operation first.

Output

The output JSON contains a simple confirmation object indicating whether the deletion was successful. It has the following structure:

{
  "success": true,
  "message": "Transaction deleted successfully"
}

No binary data is returned by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Guru Digital Manager API.
  • The base URL for the API is configurable via credentials but defaults to https://digitalmanager.guru/api/v2.
  • The node uses HTTP requests to communicate with the API endpoints.

Troubleshooting

  • Missing Credentials Error: If no API credentials are provided, the node will throw an error stating that credentials are required.
  • Invalid Transaction ID: If the transaction ID does not exist or is incorrect, the API may return a 404 error. Ensure the ID is correct and exists by using the "Get All" or "Get" operations first.
  • Permission Issues: If the API token lacks permission to delete transactions, the request will fail. Verify that the API token has appropriate permissions.
  • API Endpoint Issues: The node tries multiple alternative endpoints internally if the primary endpoint returns 404, but persistent failures indicate either an incorrect base URL or an invalid transaction ID.
  • Network or API Downtime: Network issues or API downtime can cause request failures. Check network connectivity and the status of the Guru Digital Manager API.

Links and References

Discussion