REST API for Latepoint icon

REST API for Latepoint

Consume REST API for LatePoint on Tools
Join our community

Actions40

Overview

This node enables bulk creation of multiple bookings in the LatePoint booking system via its REST API. It is designed to efficiently create many booking entries in a single API call by sending a JSON array of booking objects. This is particularly useful for scenarios such as migrating data from another system, batch scheduling appointments, or automating large-scale booking operations.

For example, a business could use this node to import dozens of customer appointments at once, specifying service IDs, agent assignments, start dates and times, and customer details all in one request, saving time compared to creating each booking individually.

Properties

Name Meaning
Bookings JSON A JSON string representing an array of booking objects to create in bulk. Each object must include service_id, agent_id, start_date, start_time, and nested customer information (e.g., first name, last name, email). Example: [{"service_id": "1", "agent_id": "1", "start_date": "2024-01-15", "start_time": "10:00", "customer": {"first_name": "John", "last_name": "Doe", "email": "john@example.com"}}]
Description Optional text describing the purpose or context of this bulk create operation, helping AI understand the intent behind the API call.

Output

The node outputs an array of JSON objects, each representing a created booking record returned from the LatePoint API. The structure corresponds to the API's booking object format, typically including identifiers, timestamps, service and agent details, customer info, status, and other metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires connection to the LatePoint REST API.
  • Must be configured with valid API credentials that provide:
    • Base URL of the LatePoint API instance.
    • An API key token for authorization.
  • The node sends authenticated HTTP POST requests with JSON payloads to the /bookings/bulk endpoint.

Troubleshooting

  • Invalid JSON in Bookings JSON: If the provided JSON string is malformed or not an array, the node will throw an error like Invalid JSON in bulk bookings. Ensure the JSON syntax is correct and represents an array of booking objects.
  • Missing Required Fields: Each booking object must include service_id, agent_id, start_date, start_time, and customer details. Omitting these may cause API errors or failed booking creation.
  • Authentication Errors: If API credentials are missing or invalid, the node will fail with a message indicating no credentials are configured or unauthorized access.
  • API Endpoint Issues: Network problems or incorrect base URL configuration can cause request failures. Verify connectivity and API endpoint correctness.
  • Partial Failures: If some bookings fail while others succeed, the node may return error messages per item if "Continue on Fail" is enabled.

Links and References

Discussion