Chameleon's API allows you to accomplish a few key things:
- Send user properties --
chmln.identify- add or remove data attributes stored for users and companies. This data can then be used in targeting / segmenting users by who they are.
- Send events --
chmln.track- add an "action that a user took". Events are used in targeting / segmenting users by what they did.
- Listen to interval events --
chmln.on- register a callback to certain state changes and events, useful for custom integrations with Chameleon.
- Download Tour data -- access the historical record of Chameleon tours that users interacted with.
- Download user data -- get information about which tours a particular user has engaged with
- Show / hide a Launcher using our JS API. Also query whether a user has completed items within a checklist.
- Permanently delete a user when you want to 'forget' a specific user that you previously identified to Chameleon.
- Personalize style or content within tour steps, based on who the user (or user group) is.
Ideas for how the API be used
- Send data about whether a user has completed a specific tour to your marketing automation tool, so you can send emails accordingly.
- Download data about a tour's performance to your database so you can track this in your BI reporting tool.
- Update user records in Chameleon when users take key actions in your product, in order to target them with relevant tours.
- Update user records in Chameleon with data from other data sources that we don't yet integrate with, such as a Customer Support tool or NPS provider.
- Start a tour when a user completes uploading some key data to their account, to congratulate them and show them next steps.
- Change the branding of Chameleon tours based on the brand settings for any particular customer account.
Send a header (
X-Account-Secret) or parameter (
account_secret) with your admin-specific secret token found here (click "Get your API key") when you are logged in.
curl -H 'X-Account-Secret: YOUR ACCOUNT SECRET' https://observe.trychameleon.com/..."
At a high level, all responses include the resource name in either singular or plural. Singular when object is an individual item (a hash) and plural when there are multiple items (an array).
- 403 - when the secret you're using does not resolve to a Chameleon account.
- 404 - when a resource cannot be found. This can happen when requesting information on a profile that has not been added to the system yet.
- 422 - when a resource is missing required information. This can happen when creating a profile and the request omitted the
- 500 - an unhandled error (Chameleon engineers will be alerted)
- 503 - Application timeout.
Next: Dive into the specific docs
For specific API methods, read more here:
- Download tour data - Rest API for accessing tour performance aggregately and per user.
- Download user data - Rest API to get user attributes and data
- Show / hide a Launcher - JS API to open / close Launcher Menu
- Permanently delete a user - API to remove a user forever.
- Personalize content or style using the custom helpers API.