Climate FieldView

​

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:

curl -X POST \
    -H 'Authorization: Bearer YOUR_TOKEN' \
    -H 'Content-Type: application/json' \
    -d '{
      "clientId": "your-client-id",
      "clientSecret": "your-client-secret",
      "apiKey": "your-api-key",
      "refreshToken": "grower-refresh-token"
    }' \
    'https://api.withleaf.io/services/usermanagement/api/users/{leafUserId}/climate-field-view-credentials'

3. Leaf validates the token and begins syncing. Check credential status with GET /users/{leafUserId}/climate-field-view-credentials.

​

Credentials schema

{
  "id": "uuid",
  "status": "str",
  "createdTime": "yyyy-MM-dd'T'HH:mm:ss.SSSSSS'Z'",
  "tokenMetadata": {"scopes": ["str"]},
  "clientId": "str",
  "clientSecret": "str",
  "apiKey": "str",
  "refreshToken": "str",
  "accessToken": "str"
}

​

Endpoints

​

Troubleshooting

curl -X GET \
    -H 'Authorization: Bearer YOUR_TOKEN' \
    'https://api.withleaf.io/services/usermanagement/api/users/{leafUserId}/climate-field-view-credentials/events'

• 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

• Connect Climate FieldView Tutorial — Step-by-step walkthrough.
• Provider Authentication Overview — How provider credentials work across all providers.
• API Reference: Providers — Full endpoint reference for provider credentials.