A Company that does not yet exist by
uid will first be created and then updated with the other data included in this request.
Company data updates are processed synchronously on the application server.
Create/Update a Company
- When you are creating the Company, simply send the
uidand any other properties pertinent to that company. - When you are updating the Company, simply send the Chameleon
idfield or use theuidand any other properties pertinent to that 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) |
| *others | optional | All other properties will be stored on the Company |
HTTP Response
Limits
- Up to a total of 768 bytes are stored for each scalar value where each Array item and each Hash value can reach this limit.
- See the full page on Normalization for more information on these limits.
Normalization
- Property names are normalized to lower case and underscored i.e.
companyName=>company_name. - See the full page on Normalization for more information on how properties are normalized.
Bulk Create/Update Companies
- When sending a bulk create/update, send an array of Company objects as the
companiesparameter - For each Company, send the Company ID as
uidand any other properties pertinent to that Company.
HTTP Request
| param | - | description |
|---|---|---|
companies | array<Company> | The list of Companies to update; each item has the same schema as the Single Company update |
on_model_missing | optional m | The treatment of Companies not previously sent to Chameleon. Defaults to create. One of create, ignore |
HTTP Response
HTTP Response error
When the 930th item had no value for theuid key
Note: The status code will be the normal 202 for (Accepted for processing)
Limits
- The size of each batch request is limited to 16mb
- As with the Single Company update, up to a total of 768 bytes are stored for each scalar value where each Array item and each Hash value can reach this limit.
- See the full page on Normalization for more information on these limits.
Examples
Either set the number of items per batch to 10,000 OR to approximate the number of items per batch (based on the average payload size), divide (16777216 / “Average characters in JSON payload per item”) * 0.95With the following update, you can send approximately 257,000 Companies per batch request

