Waiteraid

Waiteraid is a restaurant reservation and table management platform. Its API exposes bookings, guests, restaurants, meal periods, and availability, letting you read reservation data and create or update bookings and guest profiles programmatically. Nexla connects to the Waiteraid API to ingest this operational data and to push new or updated records back into your Waiteraid account.

Power end-to-end data operations for your Waiteraid API with Nexla. Our bi-directional Waiteraid connector is purpose-built for Waiteraid, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Waiteraid or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Waiteraid workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Waiteraid credential, you need a Waiteraid account with API access and an auth_hash token. Waiteraid uses token-based authentication: you exchange your account credentials for an auth_hash, which is then included with every subsequent API request.

To obtain your auth_hash, follow these steps:

1. Confirm that your Waiteraid account has API access enabled. If you are unsure, contact your Waiteraid administrator or Waiteraid support.

2. Gather the credentials required by the authentication endpoint: your Waiteraid username, your password, and the restaurant name associated with your account.

3. Call the Waiteraid authentication endpoint at /wa-api/auth, passing your username, password, and restaurant name as request parameters.

4. On success, the endpoint returns an auth_hash value. Copy this token and store it securely, as you will provide it to Nexla when creating your credential.

5. Note your base URL. For most accounts this is https://app.waiteraid.com.

The auth_hash is included with each API call to authenticate your requests against the Waiteraid API. Keep it confidential and rotate it if you suspect it has been compromised. For details on authentication, request parameters, and available methods, refer to the Waiteraid API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Base URL	Yes	No	The base URL for the Waiteraid API.
Auth Hash	Yes	Yes	The authentication hash token obtained from the Waiteraid /wa-api/auth endpoint.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter the Waiteraid API base URL in the Base URL field. For most accounts this is https://app.waiteraid.com.

4. Enter the auth_hash token you obtained in Prerequisites in the Auth Hash field. This token authenticates all requests to the Waiteraid API and must be kept confidential.

   If your auth hash is compromised, generate a new one by re-authenticating against the Waiteraid /wa-api/auth endpoint, and update your Nexla credential with the new value.

   For detailed information about authentication and available methods, see the Waiteraid API documentation.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Waiteraid connector tile, then select the credential that will be used to connect to Waiteraid, and click Next; or, create a new Waiteraid credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Waiteraid endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] Search Booking

Search for bookings and reservation slots by restaurant, date range, or guest details.

• Use this template to retrieve bookings that match your search criteria, such as a restaurant, a date range, or specific guest details. This is useful for syncing reservation data into your analytics or downstream systems.

For details on search parameters and the booking response structure, see the Waiteraid API documentation.

[Rest API] Get Booking

Retrieve details of a specific restaurant booking by booking ID.

• Use this template when you need the full details of a single booking identified by its booking ID.

For details on the booking response structure and required parameters, see the Waiteraid API documentation.

[Rest API] Get Restaurants

Retrieve all restaurants associated with the authenticated account.

• Use this template to list every restaurant your account can access, which is useful for discovering restaurant identifiers used by other endpoints.

For details on the restaurants response structure, see the Waiteraid API documentation.

[Rest API] Get Meals

Retrieve all meal/service periods configured for a restaurant.

• Use this template to fetch the meal or service periods defined for a restaurant, which are used when interpreting bookings and availability.

For details on the meals response structure and required parameters, see the Waiteraid API documentation.

[Rest API] Search Guest

Search for guests by name, email, phone, or booking ID.

• Use this template to find guest profiles that match your search criteria, such as a name, email address, phone number, or booking ID.

For details on guest search parameters and the response structure, see the Waiteraid API documentation.

[Rest API] Get Availability Status

Retrieve meal availability status for a restaurant for a given date.

• Use this template to check whether meal or service periods are available at a restaurant on a specific date.

For details on availability parameters and the response structure, see the Waiteraid API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Waiteraid data sources can also be manually configured to ingest data from any valid Waiteraid API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Waiteraid data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Waiteraid destination, and select the Send to Destination option from the menu. Select the Waiteraid connector from the list of available destination connectors, then select the credential that will be used to connect to Waiteraid, and click Next; or, create a new Waiteraid credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Waiteraid endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Booking

Create a new restaurant booking/reservation.

• This endpoint sends data as JSON in the request body to create new bookings in Waiteraid. Each record from your Nexset is sent as a separate API request to create a booking. The request body should contain the booking data in the format required by the Waiteraid API.

For details on booking creation, required fields, and request body formats, see the Waiteraid API documentation.

[Rest API] Update Booking

Update an existing restaurant booking/reservation.

• This endpoint sends data as JSON in the request body to update existing bookings in Waiteraid. Each record from your Nexset should identify the booking to update and include the fields to change.

For details on booking updates, required identifiers, and request body formats, see the Waiteraid API documentation.

[Rest API] Set Booking Status

Update the status of a booking (arrived, guest_left, paid, all_seated, deleted, undelete).

• This endpoint updates the status of an existing booking. Each record from your Nexset should identify the booking and the new status to apply.

For details on the supported status values and required parameters, see the Waiteraid API documentation.

[Rest API] Add Guest

Create a new guest profile with contact and address details.

• This endpoint sends data as JSON in the request body to create new guest profiles in Waiteraid. Each record from your Nexset is sent as a separate API request to create a guest, including contact and address details.

For details on guest creation, required fields, and request body formats, see the Waiteraid API documentation.

[Rest API] Delete Booking

Delete/cancel an existing restaurant booking/reservation.

• This endpoint deletes or cancels an existing booking in Waiteraid. Each record from your Nexset should identify the booking to delete.

For details on booking deletion and required identifiers, see the Waiteraid API documentation.

Manual configuration

Waiteraid destinations can also be manually configured to send data to any valid Waiteraid API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Waiteraid endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Waiteraid endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.