Climate FieldView Platform APIs
Official vendor OpenAPI document · agent-readyIOTSensor 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.
Use for: I want to pull field boundaries for a connected grower, Upload a variable-rate prescription file to a FieldView field, List all operations a partner has access to across resource owners, Retrieve as-harvested yield data for the most recent season
Not supported: Does not handle weather forecasting, commodity pricing, or carbon accounting - use for Climate FieldView field, operation, and agronomic data exchange only.
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.
Install Jentic One Beta
Connect the Climate FieldView Platform APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Climate FieldView Platform APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fclimate.com%2Fclimate" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fclimate.com%2Fclimate" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Climate FieldView Platform APIs.
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
Read planting activity summaries and customer insights metrics for a resource owner
Fetch CNH machine diagnostic events tied to FieldView-connected equipment
List operations across all resource owners a partner has been authorized to access
Use Cases
Patterns agents use Climate FieldView Platform APIs 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
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Climate FieldView Platform APIs by hand means running the OAuth 2.0 authorization-code flow, also sending the API-key request header partner header on every call to platform.climate.com, and chaining upload and export polling yourself. Through Jentic you install once, import the Climate FieldView Platform APIs from the API Directory, store the OAuth credentials and partner key once, and your agent calls it.
Permission scoping
FieldView puts resource ids in the URL path (/fields/{fieldId}, /uploads/{uploadId}/status), so a rule can pin your agent to a specific field and read its upload status. You choose the operations it may call, so writes like creating boundaries or exports are not included unless you add them.
Credential isolation
Your FieldView OAuth credentials and API-key request header partner header are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'upload a prescription to FieldView' or 'list field operations', and Jentic returns the matching FieldView operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Climate FieldView Platform APIs 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 with Jentic One, the self-hosted execution layer.
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.
Can I limit what my agent is allowed to do with the Climate FieldView API?
Yes. Because you run Jentic One yourself, your own rules decide which FieldView operations and credentials the agent may use, so you can allow read-only calls like GET /v4/fields and GET /v4/uploads/{uploadId}/status while excluding writes such as POST /v4/boundaries or POST /v4/exports. FieldView puts resource IDs in the URL path, so a rule can pin the agent to a specific field or upload and let it read only that record's status. Anything you do not explicitly grant stays off limits to the agent.
GET STARTED