Skip to main content
For conceptual background, see Configurations. Configurations control how Leaf syncs data from providers, processes machine files, creates field operations, and generates images. You set configurations at the API owner level (applies to all Leaf users by default) or override them for individual Leaf users.
Leaf uses API owner settings as the runtime defaults for Leaf users. The public GET /configs/{leafUserId} endpoint, however, returns only the stored custom configuration for that Leaf user. If no Leaf-user-specific config exists, that endpoint returns 404.

Base URL

Endpoints

Common configuration properties

This table lists common properties only. The full response object includes many more configuration fields.

Get API owner’s configuration

GET /configs Returns the configuration for your API owner account.

Request

Response


Get Leaf user’s configuration

GET /configs/{leafUserId} Returns the stored custom configuration for a specific Leaf user. If the Leaf user has no custom configuration, this endpoint returns 404.

Path parameters

Request

Response


Create Leaf user’s configuration

POST /configs/{leafUserId} Creates a custom configuration for a Leaf user. Include only the properties you want to override. Omitted properties remain unset on the stored Leaf-user config and continue to resolve from the API owner at runtime.

Path parameters

Request body

All fields are optional. Only include the properties you want to set.

Request

Response

The response includes the stored Leaf-user configuration object. Omitted properties are not filled in with inherited values in this response.

Update API owner’s configuration

PATCH /configs Updates specific fields of the API owner’s configuration. Only include the properties you want to change.
Configuration changes are not retroactive. Existing data is not reprocessed. If you need existing data regenerated, choose the reprocess endpoint that matches the pipeline stage affected by the setting: use file reprocessing for machine-file processing settings, and operation reprocessing for operation-generation settings.

Request body

All fields are optional.

Request

Response


Update Leaf user’s configuration

PATCH /configs/{leafUserId} Updates specific fields of a Leaf user’s configuration. Only include the properties you want to change.

Path parameters

Request body

All fields are optional.

Request

Response

The response includes the stored Leaf-user configuration object after the update. Omitted properties are not filled in with inherited values in this response.

Delete Leaf user’s configuration

DELETE /configs/{leafUserId} Deletes the custom configuration for a Leaf user. After deletion, the Leaf user inherits all settings from the API owner.

Path parameters

Request

Last modified on March 24, 2026