Starfish (CampingCare/HotelCare) icon

Starfish (CampingCare/HotelCare)

Interact with the Starfish API for CampingCare and HotelCare

Overview

This node interacts with the Starfish API for CampingCare and HotelCare, specifically supporting the 'Update Invoice' operation within the 'Invoices API' resource. It allows users to update invoice details such as the invoice ID, contact ID, reservation ID, and meta information. This node is useful for automating invoice management tasks, such as updating invoice metadata or associating invoices with specific contacts or reservations in a booking or hotel management system.

Use Case Examples

  1. Updating an invoice's metadata to reflect a new external exchange status.
  2. Associating an invoice with a specific contact or reservation by updating the respective IDs.

Properties

Name Meaning
Invoice ID Unique identifier of the invoice to update, required for the update operation.
Contact ID Optional identifier to associate the invoice with a specific contact.
Reservation ID Optional identifier to associate the invoice with a specific reservation.
Meta A collection of key-value pairs to add or update metadata on the invoice.
Request Options Settings for request behavior such as batching, SSL certificate validation, proxy usage, and timeout duration.

Output

JSON

  • invoice_id - The unique identifier of the updated invoice.
  • contact_id - The contact ID associated with the updated invoice, if provided.
  • reservation_id - The reservation ID associated with the updated invoice, if provided.
  • meta - An array of key-value pairs representing the updated metadata of the invoice.

Dependencies

  • Requires an API key credential for the Starfish API (CampingCare/HotelCare).

Troubleshooting

  • Ensure the 'Invoice ID' is provided and valid; missing or incorrect IDs will cause update failures.
  • Check API key credentials for authorization errors.
  • Verify network settings such as proxy and SSL options if requests fail or time out.
  • Batching settings should be configured properly to avoid request throttling issues.

Discussion