Skip to main content
A Leaf user represents an end user of your application (for example, a grower). Each Leaf user keeps provider credentials and farm data organized under your API owner account. You create a Leaf user, attach provider credentials, and Leaf begins syncing field boundaries, machine files, and field operations from those providers. For conceptual background — what a Leaf user represents, account structure patterns, and configuration inheritance — see Leaf Users overview.

Base URL

Endpoints

Example resource shape

This is an example resource shape, not an exhaustive list of every credential object that may appear on a Leaf user.

Get all Leaf users

GET /users Returns a paginated list of Leaf users belonging to your API owner account.

Query parameters

Request

Response


Get a Leaf user

GET /users/{id} Returns a single Leaf user by ID, including all linked provider credentials.

Path parameters

Request

Response


Create a Leaf user

POST /users Creates a new Leaf user. After creation, you can attach provider credentials to start syncing data.

Request body

You can also attach provider credentials in the same request by including the credentials ID. For example, to link John Deere credentials:

Request

Response


Partially update a Leaf user

PATCH /users/{id} Updates specific profile fields on an existing Leaf user without replacing the entire object. Only the fields you include in the request body are changed; everything else — including provider credentials — is left untouched.
To update provider credentials or replace the full Leaf user object, use PUT /users instead.

Path parameters

Request body

All fields are optional. Include only the fields you want to change.

Request

Response

Returns the full Leaf user object with the updated fields.

Update a Leaf user

PUT /users Replaces an existing Leaf user with the provided object. You must include the id field in the request body.
This is a full replacement. If the existing Leaf user has provider credentials and you omit them from the request body, those credentials are removed. Always include credentials you want to keep.

Request body

To keep or update linked credentials, include them in the body:

Request

Response


Delete a Leaf user

DELETE /users/{id} Deletes a Leaf user by ID. Returns HTTP 204 No Content on success.

Path parameters

Deleting a Leaf user removes all associated provider credentials and stops data syncing for that user. This action cannot be undone.

Request

Last modified on April 17, 2026