Tripletex

Connect to Tripletex API v2
Join our community

Actions15

Overview

This node connects to the Tripletex API v2 and allows users to manage orders among other resources. Specifically, for the Order - Delete operation, it deletes an existing order identified by its Order ID. This is useful in scenarios where an order was created by mistake or needs to be removed from the system due to cancellation or error.

Practical examples:

  • Automatically deleting orders that fail validation in a workflow.
  • Removing test or duplicate orders during data cleanup processes.
  • Integrating with external systems to synchronize order deletions.

Properties

Name Meaning
Order ID The unique identifier of the order to delete

Output

The output JSON contains the response from the Tripletex API after attempting to delete the specified order. Typically, this will include confirmation of deletion or details about any errors encountered.

No binary data output is produced by this operation.

Example output JSON might look like:

{
  "message": "Order deleted successfully"
}

or, in case of failure:

{
  "error": "Order not found"
}

Dependencies

  • Requires an API key credential for authenticating with the Tripletex API.
  • The node uses the Tripletex API base URL which switches between a test environment and production based on the credential configuration.
  • HTTP requests are made with JSON content type and Basic Authentication using a session token derived from the API key.

Troubleshooting

  • Validation errors: If the Order ID is missing or empty, the node will throw a validation error before making the API call.
  • Authentication failures: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Order not found: If the provided Order ID does not exist, the API will return an error; verify the ID is correct.
  • Network issues: Check connectivity to the Tripletex API endpoints and proxy/firewall settings if applicable.
  • API limits: Be aware of any rate limits imposed by Tripletex to avoid request throttling.

Links and References

Discussion