REST API for Latepoint icon

REST API for Latepoint

Consume REST API for LatePoint on Tools
Join our community

Actions40

Overview

The node provides integration with the LatePoint REST API, specifically enabling management of bookings among other resources. The Update Booking operation allows users to modify existing booking records by specifying the booking ID and the fields to update. This is useful in scenarios such as rescheduling appointments, changing assigned agents, updating customer details, or modifying booking status.

Practical examples include:

  • Changing the start date/time of a booking.
  • Updating the assigned agent for a service appointment.
  • Modifying the booking status (e.g., from "pending" to "approved").
  • Adding notes or additional metadata to an existing booking.

This operation supports sending updates either via individual fields or by providing a custom JSON or form data body, offering flexibility depending on user needs.

Properties

Name Meaning
ID The unique identifier of the booking to update. Required to specify which booking record will be modified.
Send Body Whether to send a custom request body (JSON or form data) instead of using individual input fields. Useful when you want full control over the update payload.
Body Content Type When sending a custom body, choose between JSON or Form Data format for the request body.
JSON Body A JSON object representing the entire request body to send when Send Body is enabled and Body Content Type is JSON. Example structure includes service ID, agent ID, start date/time, customer info, status, etc.
Form Data Form data parameters to send in the request body when Send Body is enabled and Body Content Type is Form Data. Allows specifying multiple name-value pairs.
Additional Fields Collection of individual fields to update when not sending a custom body. Includes:
• Service ID — Identifier of the service booked.
• Agent ID — Assigned staff member.
• Customer ID — Customer making the booking.
• Start Date — Booking start date (YYYY-MM-DD).
• Start Time — Booking start time (HH:MM 24-hour).
• End Time — Booking end time.
• Status — Booking status (e.g., approved, pending).
• Notes — Additional notes about the booking.

Output

The output is a JSON object representing the updated booking record returned from the LatePoint API after a successful update operation. It contains all relevant booking details including identifiers, dates, times, status, assigned agent, customer information, and any other fields supported by the API.

If multiple items are returned (not typical for update), each item is output separately.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the LatePoint REST API.
  • The base URL for the LatePoint API must be configured in the credentials.
  • The node uses HTTP methods (PUT) to communicate with the LatePoint API endpoints.
  • Proper permissions on the API key are necessary to perform update operations on bookings.

Troubleshooting

  • Error: No credentials configured!
    Ensure that the API key credential for LatePoint is properly set up in n8n before executing the node.

  • Invalid JSON in body:
    When using the custom JSON body option, ensure the JSON syntax is valid. Use a JSON validator if needed.

  • Booking ID missing or invalid:
    The ID property is required. Verify that the booking ID provided exists and is correct.

  • API errors related to permissions or invalid fields:
    Check that the API key has sufficient rights and that the fields being updated conform to the API schema.

  • Network or connectivity issues:
    Confirm that the base URL is reachable and that there are no firewall or network restrictions blocking access.

Links and References

These links provide detailed information on API endpoints, authentication, and data formats used by the LatePoint API.

Discussion