REST API for Latepoint icon

REST API for Latepoint

Consume REST API for LatePoint on Tools
Join our community

Actions40

Overview

This node interacts with the LatePoint REST API to manage payment records within a booking system. Specifically, the Payments - Get operation retrieves detailed information about a single payment by its unique identifier. This is useful when you need to fetch payment details such as status, amount, method, and related booking or customer information.

Common scenarios include:

  • Retrieving payment details for verification or reporting.
  • Fetching payment info to update downstream systems or trigger workflows.
  • Auditing payment statuses or transaction IDs.

Example: You have a payment ID from a previous step or external source and want to get all associated data about that payment to display in a dashboard or send a notification.

Properties

Name Meaning
Description A text field where you can describe the purpose or context of this API call (optional).
ID The unique identifier of the payment record to retrieve. This is required for the "Get" operation on Payments resource.

Output

The output is a JSON object representing the payment record retrieved from the LatePoint API. It typically includes fields such as:

  • id: Unique payment identifier.
  • booking_id: Associated booking's ID.
  • customer_id: Customer who made the payment.
  • amount: Payment amount.
  • payment_method: Method used (e.g., cash, credit card, PayPal).
  • status: Payment status (pending, completed, failed, refunded).
  • transaction_id: External transaction reference from payment processor.
  • notes: Additional notes related to the payment.
  • Other metadata fields depending on the API response.

If multiple payments were returned (not applicable for single "Get"), each would be an item in the output array.

No binary data is output by this node.

Dependencies

  • Requires connection to the LatePoint REST API.
  • Must configure credentials containing the API base URL and an API key token.
  • The API key is sent as a Bearer token in the Authorization header.
  • Network access to the LatePoint API endpoint is necessary.

Troubleshooting

  • No credentials configured!
    Ensure you have set up the required API authentication credentials in n8n before running the node.

  • Invalid JSON in body:
    This error occurs if you provide malformed JSON in any JSON body input fields (not typical for "Get" but relevant for other operations). Validate JSON syntax carefully.

  • Resource or ID not found:
    If the payment ID does not exist or is incorrect, the API may return a 404 or empty response. Verify the ID value.

  • API connectivity issues:
    Check network connectivity and API endpoint correctness if requests fail.

  • Permission errors:
    Make sure the API key has sufficient permissions to read payment data.

Links and References

Discussion