ChiliPiper

​

What’s supported

​

Supported actions

This connector supports:

• Read Actions, including full historic backfill. Please note that incremental read is not supported, a full read of the Chilipiper instance will be done for each scheduled read.
• Write Actions.
• Proxy Actions, using the base URL https://fire.chilipiper.com.

​

Supported Objects

The Chilipiper connector supports reading from the following objects:

• workspace
• team
• distribution
• workspace/users

The Chilipiper connector supports writing to the following objects:

• distribution
• user/invite
• user/licenses
• team/users/add
• team/users/remove
• workspace/users/add
• workspace/users/remove
• workspace/users/remove-from-all

​

Example integration

To define an integration for ChiliPiper, create a manifest file that looks like this:

# amp.yaml
specVersion: 1.0.0
integrations:
  - name: chilipiper-integration
    displayName: My ChiliPiper Integration
    provider: chilipiper
    proxy:
      enabled: true

​

Using the connector

This connector uses API Key auth, which means that you do not need to set up a Provider App before getting started. (Provider Apps are only required for providers that use OAuth2 Authorization Code grant type.)

To start integrating with ChiliPiper:

• Create a manifest file like the example above.
• Deploy it using the amp CLI.
• Embed the InstallIntegration UI component. The UI component will prompt the customer for an API key.
• Start making Proxy Calls, and Ampersand will automatically attach the API key supplied by the customer. Please note that this connector’s base URL is https://fire.chilipiper.com.

​

Creating an API key for ChiliPiper

• Log in to your chilipiper instance
• Go to Integrations
• Click on the API Access Tokens
• Click On Generate Token