Configuring Concierge EDGE API

The Edge API is one of the available triggers for Concierge routers. Use it when Concierge is not launched using the Chili Piper JavaScript snippet — for example, in server-side or hybrid environments where data must be sent directly to the Edge endpoint.

To configure the Edge API trigger, generate an API token in the Admin Center and include it in requests sent to the Edge endpoint.

Table of Contents

• Prerequisites
• Step 1: Generate an API Token
• Step 2: Configure the API Endpoint
• Step 3: Make a POST Request
• Share Instructions with Your Developer
• Good to Know

Prerequisites

Before setting up the Edge API, confirm the following:

• You have a Concierge router created in Chili Piper
• The Concierge Router uses a Button is clicked in-app trigger
• A user with the Admin role in Chili Piper is available to generate the API token in Admin Center

Step 1: Generate an API Token

1. Go to Admin Center and navigate to the Credentials page
2. Click Generate Token
3. Select the Concierge.route permission
4. Name the token to match the router you are using (for example, Demo Request Router)
5. Copy the token immediately — it is only shown once and cannot be retrieved later

Step 2: Configure the API Endpoint

In your Concierge router settings, open the Booking Page tab and expand the On a Website and/or Web App section. Select the Edge API tab.

The endpoint URL and request body are displayed on this page.

Endpoint URL (POST):

https://fire.chilipiper.com/api/fire-edge/v1/org/concierge/routers/[routerSlug]/rest/ADD_TOKEN_HERE

Replace [routerSlug] with your router’s slug and ADD_TOKEN_HERE with the API token generated in Step 1.

You can click Copy to copy the URL and Copy Code to copy the request body template.

Step 3: Make a POST Request

Send a POST request to the endpoint URL using the following JSON body structure:

{
  "form": {

  },
  "options": {

  }
}

In the form object, include the fields your router expects (for example, email, first name, last name).

In the options object, you can pass additional configuration parameters.

For a full list of available fields and options, see the Edge API References article.

Share Instructions with Your Developer

If another team member is implementing the API integration, you can use the Share Instructions button at the bottom of the Edge API tab.

This generates a pre-written message containing:

• The endpoint URL
• Token generation steps
• A link to Admin Center
• A link to this support article

You can copy and send this message directly to your developer.

[Screenshot: Share Instructions modal]

Good to Know

• The Edge API option is only available for routers using the Button is clicked in-app trigger
• API tokens are shown only once at the time of creation and cannot be retrieved afterward
• Only users with the Admin role can generate API tokens
• Each token should be scoped to a single router for security and traceability
• In-page token generation is not available — tokens must be created in Admin Center