For a full list of your User / Company Properties see the Properties API
Schema
Fully-expanded Company when listed directly or embedded with expand param specified properly
| Property | Type | Description |
|---|---|---|
id | ID | The Chameleon ID |
created_at | timestamp | When this happened or when this was added to the Database |
uid | string | The external ID that came from your backend system |
*any options | mixed | Any other options you have sent as Custom Properties will show up here too |
Non-expanded Company when embedded in another (i.e. Microsurvey response)
| Property | Type | Description |
|---|---|---|
id | ID | The Chameleon ID |
created_at | timestamp | When this happened or when this was added to the Database |
uid | string | The external ID that came from your backend system |
Create or Update a Company
See the Companies Webhook for sending User data to ChameleonRetrieve a Company
Retrieve a single Company.HTTP Request
| param | - | description |
|---|---|---|
id | optional | The Chameleon ID of the Company |
uid | optional | The Company identifier (typically the Database ID from your backend) |
List Companies
List all Companies.HTTP Request
| param | - | description |
|---|---|---|
limit | optional | Defaults to 50 with a maximum of 500 |
before | optional | Used when paginating, use directly from the cursor object from the previous response |
before | optional | Read as “created before” and can be given as a timestamp to get only limit items that were created before this time |
after | optional | Read as “created after” and can be given as a timestamp or ID to get only limit items that were created after this time |
expand | optional | Object that specifies relationships to include/exclude. Supported keys are company |
expand.company | optional | use values of all, min to control the properties present in the company. Defaults to all |
Using the expand parameter
HTTP Response
Search Companies
Searching Companies through the Chameleon API allows you to:- Search for a company by
idanduid
Note: Rate Limiting applies according to the table below.
| endpoint | Maximum concurrent requests |
|---|---|
/companies | 2 |
Examples
All of these examples are based directly on the full schema of Segmentation Filter Expressions. Each example below is showing the value for thefilters key in the JSON request body:
Companies that have a specific uid
Find the company with theuid of 123:
Delete a Company
When deleting a company, the company record itself is deleted and company is removed from all profiles associated with it. The associated profiles can also be removed by passingcascade=profiles with the request.
| param. | - | description |
|---|---|---|
id | optional | The Chameleon ID of the Company |
uid | optional | The Company identifier (typically the Database ID from your backend) |
HTTP Request
Eitherid or uid is required.
HTTP Response
The endpoint returnsid of the Deletion record.
The Deletion is an internal Chameleon record that can be referenced as proof of initiating this request.
Deleting a company and all profiles associated with it
Deleting a company and all profiles associated with it can be done by passingcascade=profiles:
HTTP Response
When cascade deletion is requested, the endpoint also returns deletion ids of all the profiles associated with the company underdeletions key.

