Limits and constraints
To provide high performance, data integrity, and predictable behavior, the following limits and constraints apply:
| Limit | Value | Description |
|---|---|---|
| Maximum number of schemas per workspace | 10 | You can create up to 10 schemas per workspace, regardless of whether they are simple or versioned. This limit applies universally. |
| Maximum number or records for a simple schema | 10 | You can add up to 10 records to a simple schema. |
| Maximum number or records for a versioned schema | 10,000 | You can add up to 10,000 records to a versioned schema. |
| Nesting depth of one-to-many relation | 2-level deep | Only one level of nesting (2 levels deep) is supported. |
| Size of fetched records for one-to-many relation | 50 | In one-to-many relations, a maximum of 50 records is fetched. |
| Enabling value uniqueness and searching for a schema field | Only for primitive field types | Only for the following field types, you can enable Enable search & filtering and Unique values only options: string, boolean, number. |
| Maximum number of searchable fields per schema | 10 | Up to 10 top-level primitive fields—fields with basic data types like string, number, or boolean that are defined directly within the main schema and not nested inside objects or arrays—can have the Enable search & filtering option enabled. |
| Maximum unique fields per schema | 5 | A schema can have up to 5 top-level primitive fields—those not nested within objects or arrays and directly defined in the main schema—marked as unique. |
| Available HTTP methods for creating a connection to an external source | GET and POST |
You can connect to the external sources using only GET or POST methods. |
| Authentication method for external source connections | API key; login and password; SHA256-based authentication | While creating an external source, you can authenticate only with the API key of the external source, login and password, or SHA256 (recommended for authenticating with Eagle Eye) |
| Profile data cache TTL | 60 seconds | After generating an object from a record, profile data is cached. The cache is used for subsequent requests even if the profile was updated |
| External source response cache TTL | Configured per External Source | After generating an object from a record, responses from external sources are cached. The cache is used when the external source, headers, query parameters, and request are the same in subsequent requests. |
