> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Request fields and types

> Each reference page lists its method, path, parameters, JSON body, response, and error behavior. The server remains authoritative for permissions and semantic rules.

How-to guideApplies to: Unified engine deployments

Each reference page lists its method, path, parameters, JSON body, response, and error behavior. The server remains authoritative for permissions and semantic rules.

## Paths, query values, and bodies

Path values select a resource. Query values filter or page a response. JSON bodies define an operation's input. The reference describes each field and its location.

Identifiers returned by the engine belong in later path fields. Encode each path component in your client. For catalog discovery, `namespace` is a JSON array encoded as a query string, such as `["analytics", "daily"]`; a dot inside a component is not a separator.

Send JSON bodies with `Content-Type: application/json`. Do not add fields from a response object unless the request schema accepts them. Many request types reject unknown fields.

## Shared types

| Type | Wire representation |
| - | - |
| UUID identity | A UUID string. Use the exact returned value. |
| Timestamp | Often `{ "unix_millis": 1767225600000 }`; some domain fields contain the integer directly. |
| Duration | `{ "secs": 30, "nanos": 0 }`. |
| Decimal parameter | A string such as `"12.50"` to preserve precision. |
| Nullable value | JSON `null`, where allowed. Omission can have different semantics. |
| String array | A JSON array such as `["Books", "Games"]`. |
| Schedule | A tagged JSON shape. See the workload create reference. |
| Arbitrary document | A JSON object whose internal shape follows its document format or provider. |

Read units and bounds on the specific field. Do not assume every timestamp or duration uses the same representation. Large integer handling also depends on the domain: typed workload parameter values can preserve supported integers as strings; arbitrary integer fields are not automatically string-valued.

## Example values

Complete examples use `{{name}}` placeholders. Replace each one in your client before sending a request. Preserve the field's JSON type when substituting a number, object, or string.

Successful responses supply named values for later requests. Record these IDs and use them in the later path fields or request bodies. UUID placeholders need a fresh UUID for new work; preserve the original UUID when recovering the same request.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.