Skip to main content
Leaf connects to Climate FieldView using OAuth 2.0. Once connected, Leaf syncs farms, fields, machine files, and field operations for the Leaf user. Climate FieldView does not have a grower-level hierarchy, so data syncs at the farm and field level.

Prerequisites

  1. A Climate FieldView developer account. Become a partner.
  2. Your application’s clientId, clientSecret, and apiKey from Climate FieldView.
  3. A grower’s refreshToken obtained through the Climate FieldView OAuth 2.0 consent flow.

Setup steps

  1. Complete the Climate FieldView OAuth 2.0 flow to obtain a refreshToken for the grower’s account.
  2. POST the credentials to Leaf:
  1. Leaf validates the token and begins syncing. Check credential status with GET /users/{leafUserId}/climate-field-view-credentials.

Credentials schema

Create request body: Response:

Endpoints

Base URL: https://api.withleaf.io/services/usermanagement/api

Troubleshooting

Use the events endpoint to inspect credential health:
Event logs are retained for 30 days. Once the credential is deleted or disassociated from the Leaf user, the logs are no longer available.
Common issues:
  • Status changes to invalid: The grower may have revoked access in Climate FieldView, or the refresh token expired. Have the grower re-authorize.
  • No grower hierarchy: Climate FieldView does not expose a grower level in its FMIS structure. Data is organized by farms and fields only.

What to do next

Last modified on March 19, 2026