REST API for LatepointInstall

Overview

This node provides integration with the LatePoint REST API, specifically enabling management of booking-related data. The "Delete" operation for the "Bookings" resource allows users to delete a specific booking by its unique identifier. This is useful in scenarios where appointments or reservations need to be canceled and removed from the system.

Practical examples include:

• Automatically deleting a booking when a customer cancels an appointment.
• Cleaning up test or dummy bookings created during development or testing.
• Removing outdated or erroneous bookings from the scheduling system.

Properties

Output

The output of the delete operation returns JSON data representing the result of the deletion request. Typically, this will be a confirmation object indicating success or failure of the deletion. If multiple items were deleted (not applicable here), it would return an array of such objects.

No binary data is output by this operation.

Dependencies

• Requires an API key credential for authenticating requests to the LatePoint REST API.
• The base URL for the LatePoint API must be configured in the credentials.
• Network access to the LatePoint API endpoint is necessary.

Troubleshooting

• Missing Credentials: If no API key or base URL is configured, the node will throw an error "No credentials configured!" Ensure that the API key credential is properly set up.
• Invalid ID: Providing an invalid or non-existent booking ID may result in an error response from the API. Verify the booking ID before attempting deletion.
• API Errors: Any errors returned by the LatePoint API (e.g., authorization errors, rate limits) will be surfaced as error messages. Check API documentation and credentials if such errors occur.
• JSON Parsing Errors: Not applicable for delete operation since no body JSON is sent.

Links and References

• LatePoint REST API Documentation
• LatePoint API Authentication Guide