​
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 Dixa instance will be done for each scheduled read.
  • Write Actions.
  • Proxy Actions, using the base URL https://dev.dixa.io.

​
Supported Objects

The Dixa connector supports reading from the following objects: The Dixa connector supports writing to the following objects:

​
Example integration

To define an integration for Dixa, create a manifest file that looks like this: 
# amp.yaml 
specVersion: 1.0.0
integrations:
  - name: dixa-integration
    displayName: My Dixa Integration
    provider: dixa
    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 Dixa:
  • 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://dev.dixa.io.

​
Creating an API key for Dixa

Click here for more information about generating an API key for Dixa. The UI components will display this link, so that your users can successfully create API keys.