Skip to main content

What’s Supported

Supported actions

This connector supports:
  • Read Actions, including full historic backfill. Please note that incremental read is supported only for email_tracking, person_events and sms currently. For all other objects, a full read of the Loxo instance will be done per scheduled read.
  • Write Actions.
  • Proxy Actions, using the base URL https://{{.domain}}/api/{{.agency_slug}}.

Supported Objects

The Loxo connector supports writing and reading from the following objects:

Example integration

For an example manifest file of an Loxo integration, visit our samples repo on Github.

Using the connector

This connector uses API Key authentication, so you do not need to configure a Provider App before getting started. (Provider Apps are only required for providers using the OAuth2 Authorization Code grant type.)
Note:
  • To get the domain, log in to your Loxo account and check the URL in your browser’s address bar. It usually follows this pattern: https://[your-domain-here].
  • To get the agency_slug, go to Settings > General under Workspace. In the Agency Info section, look at the Resume Forwarding Address — the part before the @ symbol is the agency_slug value.
To integrate with Loxo:
  • Create a manifest file similar to the example above.
  • Deploy it using the amp CLI.
  • Embed the InstallIntegration UI component, which will prompt the customer for an API key.
  • Start using the connector!
    • If your integration has Read Actions, you’ll start getting webhook messages.
    • If your integration has Write Actions, you can start making API calls to our Write API.
    • If your integration has Proxy Actions, you can start making Proxy API calls.

Creating an API key for Loxo

  1. Log in to your Loxo account.
  2. Navigate to settings and click API Keys under Workspace.
  3. Click Add Button.
Generate Token