Climate FieldView Platform APIs

Name: Climate FieldView Platform APIs API
Brand: Climate FieldView Platform APIs
Availability: InStock

✓ Official Vendor SpecIOTSensor Dataoauth2, apiKey28 EndpointsREST

For Agents

Read field boundaries, farm organizations, and as-planted/as-harvested data from Climate FieldView, and upload imagery, prescriptions, or boundaries on behalf of growers. Supports OAuth 2.0 scoped access to 28 v4 endpoints.

Quickstart

Get started with Climate FieldView Platform APIs in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"pull field boundaries from climate fieldview"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Climate FieldView Platform APIs API.

Retrieve field metadata and boundary geometries for a grower's farm organization

Upload field boundaries and request boundary queries by location or owner

Stream chunked uploads of imagery, prescriptions, and soil sample results via the /v4/uploads multipart flow

Request asynchronous exports of as-planted, as-applied, and as-harvested agronomic layers and poll their status

GET STARTED

Start building with Climate FieldView Platform APIs API

Explore with Jentic

View OpenAPI Spec

The Climate FieldView Platform APIs give partners programmatic access to agronomic data captured by Climate FieldView, including field boundaries, farm organizations, planting and harvest operations, scouting observations, soil samples, and machine diagnostics. Partners can upload imagery, prescriptions, and as-applied or as-planted data, and request asynchronous exports of agronomic layers for downstream analytics. Authentication uses OAuth 2.0 authorization code grant with scoped permissions (for example fields:read, asHarvested:write) plus an X-Api-Key header that controls throttling. The platform exposes 28 endpoints anchored at platform.climate.com/v4 covering field, boundary, upload, and export workflows.

Use Cases

Patterns agents use Climate FieldView Platform APIs API for, with concrete tasks.

★ Agronomy Platform Field Sync

Pull field boundaries, farm organization metadata, and resource owner records from Climate FieldView so a third-party agronomy platform can mirror a grower's operation. The /v4/fields and /v4/boundaries endpoints return geometry and identifiers that map cleanly onto the partner's own field schema, and OAuth scopes (fields:read, farmOrganizations:read) keep access narrowly bounded to what the grower has approved.

Authenticate with fields:read scope, list all fields for the connected farm organization, and fetch boundary geometry for each field returned

Prescription and Imagery Upload

Send variable-rate prescriptions, scouting imagery, and soil sample results back to FieldView so they appear in the grower's mobile app and equipment displays. The /v4/uploads flow accepts multi-part PUTs with status polling, and dedicated scopes (rx:write, imagery:write, soil:write) gate each upload type so partners cannot write data they were not authorized for.

Initiate a /v4/uploads session for a prescription file, PUT the file in chunks, then poll /v4/uploads/{uploadId}/status until the upload reports completed

As-Applied and As-Harvested Export

Request bulk exports of as-applied, as-planted, and as-harvested layers for analytics, benchmarking, or reporting workflows. The export flow is asynchronous: POST /v4/exports kicks off a job, GET /v4/exports/{exportId}/status reports readiness, and /v4/exports/{exportId}/contents returns the data once available. This avoids holding open long-running connections for what can be gigabytes of agronomic data.

POST /v4/exports for asHarvested data on a list of field IDs, poll the export status every 30 seconds, and download contents once status is ready

Agent-Driven Field Operations Lookup

An AI agent embedded in a farm management copilot uses Jentic to search for FieldView operations endpoints by intent (for example pull recent harvest operations) and execute them with grower-scoped OAuth tokens. Jentic isolates the OAuth refresh tokens in its vault so the agent never sees raw credentials, and routes responses back as structured JSON the agent can summarize.

Use Jentic to search for retrieve field operations, load the schema for /v4/operations/all, and execute the call with the grower's scoped access token

Key Endpoints

28 endpoints — the climate fieldview platform apis give partners programmatic access to agronomic data captured by climate fieldview, including field boundaries, farm organizations, planting and harvest operations, scouting observations, soil samples, and machine diagnostics.

METHOD

PATH

DESCRIPTION

GET

/v4/fields

List fields accessible to the partner

GET

/v4/fields/{fieldId}

Retrieve a single field record

POST

/v4/boundaries

Upload a new field boundary

POST

/v4/boundaries/query

Query boundaries by criteria

POST

/v4/uploads

Initiate an upload session for imagery, prescriptions, or sample data

GET

/v4/uploads/{uploadId}/status

Check the status of an upload

POST

/v4/exports

Request an asynchronous export of agronomic data

GET

/v4/operations/all

List all field operations across resource owners

GET

/v4/fields

List fields accessible to the partner

GET

/v4/fields/{fieldId}

Retrieve a single field record

POST

/v4/boundaries

Upload a new field boundary

POST

/v4/boundaries/query

Query boundaries by criteria

POST

/v4/uploads

Initiate an upload session for imagery, prescriptions, or sample data

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

FieldView requires both an OAuth 2.0 refresh token and an X-Api-Key partner header. Jentic stores both encrypted in the MAXsystem vault and injects them at execution time, so the agent only sees scoped access tokens for the current call.

Intent-based discovery

Agents search Jentic by intent (for example upload a prescription to fieldview) and Jentic returns the matching FieldView operation with its OAuth scope requirements and request schema, so the agent calls /v4/uploads with the right scope on the first try.

Time to first call

Direct FieldView integration: 1-2 weeks to handle OAuth authorization code flow, scope-by-scope consent, X-Api-Key threading, and the asynchronous upload and export polling. Through Jentic: under an hour to search, load schema, and execute the first authenticated call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Climate Tracker Initiative

Climate-related dataset API with a different focus (climate finance vs. on-farm agronomy)

Choose this when the agent needs climate finance or transition risk data rather than grower field operations

Complementary

Climatiq

Carbon emissions calculation API that pairs with on-farm activity data

Use Climatiq when the agent needs to convert FieldView operation records into greenhouse gas estimates for sustainability reporting

Alternative

NLM Clinical Tables

Different domain reference data API; included as a contrast, not a true alternative

Not a real substitute for FieldView; agents should not select this for agronomic workflows

FAQs

Specific to using Climate FieldView Platform APIs API through Jentic.

What authentication does the Climate FieldView Platform API use?

FieldView requires two credentials on every call: an OAuth 2.0 access token in the Authorization header (obtained via the authorization code grant at api.climate.com/api/oauth/token) and a partner X-Api-Key header that controls request throttling. OAuth scopes are fine-grained (fields:read, asHarvested:write, rx:write, etc.) and the grower must approve each scope at consent. Through Jentic, both the OAuth refresh token and the X-Api-Key are stored encrypted in the vault so an agent never holds raw credentials in its context.

Can I upload variable-rate prescriptions through the FieldView API?

Yes. Initiate a session by POSTing to /v4/uploads with the prescription metadata and rx:write scope, PUT the file content in chunks to /v4/uploads/{uploadId}, then poll /v4/uploads/{uploadId}/status until completion. The same multi-part flow handles imagery (imagery:write) and soil samples (soil:write).

What are the rate limits for the FieldView API?

Each partner X-Api-Key is assigned a custom usage plan with a burst limit, a steady-state rate limit, and a monthly quota. When exceeded the API returns a 429 with an optional Retry-After header. Specific numeric limits are negotiated per partner during onboarding and are not published in the spec.

How do I export as-harvested yield data through Jentic?

Use the Jentic search query process a credit card payment style natural-language search export as-harvested data fieldview, load the schema for POST /v4/exports, execute the call with asHarvested:read scope and the field IDs you need, then poll GET /v4/exports/{exportId}/status until ready and download from /contents. Get started at https://app.jentic.com/sign-up.

Why are FieldView exports asynchronous?

Agronomic exports often span gigabytes of point data across many fields and seasons, so the API returns an exportId immediately and processes the job in the background. Clients poll the status endpoint and download from a signed URL once ready, which is more reliable than holding open a long HTTP connection.

Does FieldView support reading machine diagnostics?

Yes, with the diagnostics:read scope you can retrieve CNH machine diagnostic events tied to equipment that has been paired to a FieldView account. This is useful for fleet health monitoring alongside the agronomic data layers.