Climate FieldView Platform APIs

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

★ Only Publicly Available SpecIOTSensor Dataoauth2,apiKey28 EndpointsREST

For Agents

Manage agricultural fields, boundaries, and asPlanted/asHarvested data for digital agriculture, with chunked uploads and OAuth2 plus API-key auth across 28 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:
"list farm fields"

# → 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 records and resolve boundaries by ID for crop planning

Upload agronomic asPlanted, asHarvested, and asApplied data via chunked transfers

Query batches of boundaries and upload statuses in single calls

List operations accessible to a granted user across farm organisations

GET STARTED

Start building with Climate FieldView Platform APIs API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Climate FieldView Platform APIs, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Climate FieldView Platform APIs, keeping it validated and agent-ready. The Climate FieldView Platform APIs expose 28 endpoints for managing fields, boundaries, farm organisations, resource owners, agronomic uploads, exports, and operations for digital agriculture workflows. Authentication combines OAuth2 with a per-partner X-Api-Key header that determines a custom usage plan, with throttling enforced as 429 responses. Large agronomic data files are handled via chunked uploads in 5MiB segments up to 500MiB total, and pagination uses X-Limit and X-Next-Token headers.

Use Cases

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

★ Agronomic Data Upload Pipeline

Build an agronomic ingestion pipeline that uploads asPlanted, asHarvested, and asApplied files from farm machinery into Climate FieldView. The API uses POST /v4/uploads to initiate, PUT /v4/uploads/{uploadId} for chunked transfer in 5MiB segments, and GET /v4/uploads/{uploadId}/status for completion checks. Required for partners syncing field operations data, with file sizes commonly 50-500MiB per harvest.

POST /v4/uploads to initiate, PUT each 5MiB chunk to /v4/uploads/{uploadId} with the correct Content-Range, then poll /v4/uploads/{uploadId}/status until complete

Field Boundary Management

Manage field boundaries for connected agriculture applications by uploading polygon definitions and querying them in batches. The API exposes POST /v4/boundaries for upload, GET /v4/boundaries/{boundaryId} for single retrieval, and POST /v4/boundaries/query for batch lookup. Critical for prescription-map workflows where dozens of fields must be resolved per planning session.

POST /v4/boundaries with a GeoJSON polygon for a new field, then verify with GET /v4/boundaries/{boundaryId}

Multi-Grower Operations Aggregation

Aggregate operations across multiple grower accounts where a partner has been granted access. GET /v4/operations/all returns operations available to the calling user across all farm organisations they have rights on, supporting partner integrations like agronomy advisory tools. This replaces per-grower polling with a single aggregated call.

GET /v4/operations/all and group results by farmOrganizationId to summarise activity per grower

AI Agent Field Lookup via Jentic

Through Jentic, an agent can answer natural-language questions like which fields are above a size threshold or which uploads are still pending. Jentic exposes Climate FieldView's field, boundary, and upload operations as discoverable tools, letting a Claude or GPT agent generate ad-hoc agronomy reports without bespoke integration code.

Search Jentic for 'list fields', call GET /v4/fields, and return the 10 largest fields by area for a specified farmOrganizationId

Key Endpoints

28 endpoints — jentic publishes the only available openapi specification for climate fieldview platform apis, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v4/fields

List fields

GET

/v4/fields/{fieldId}

Get a field by ID

POST

/v4/boundaries

Upload a boundary

POST

/v4/boundaries/query

Batch query boundaries

POST

/v4/uploads

Initiate chunked upload

PUT

/v4/uploads/{uploadId}

Upload a chunk

GET

/v4/uploads/{uploadId}/status

Get upload status

GET

/v4/fields

List fields

GET

/v4/fields/{fieldId}

Get a field by ID

POST

/v4/boundaries

Upload a boundary

POST

/v4/boundaries/query

Batch query boundaries

POST

/v4/uploads

Initiate chunked upload

PUT

Why though Jentic?

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

Credential isolation

Climate FieldView X-Api-Key and OAuth2 tokens are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped access — neither the partner key nor the OAuth refresh token enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'upload a field boundary') and Jentic returns the matching POST /v4/boundaries operation with its schema, so the agent calls it without reading the platform.climate.com docs.

Time to first call

Direct FieldView integration: 1-2 weeks for OAuth setup, partner-key onboarding, chunked uploads, and pagination handling. Through Jentic: under 2 hours — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Farmbrite API

Farm management alternative for smaller mixed-operation growers

Choose Farmbrite for diversified small farms; pick FieldView for row-crop precision agriculture data.

Complementary

Agrimetrics API

UK agronomic data layers that complement FieldView field records

Pair with FieldView when UK growers need supplementary soil and weather context.

Complementary

Ambient Weather API

On-farm weather station data to enrich FieldView field operations

Use to layer microclimate readings onto FieldView field records during planting decisions.

FAQs

Specific to using Climate FieldView Platform APIs API through Jentic.

Why is there no official OpenAPI spec for Climate FieldView Platform APIs?

Climate (Bayer) does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Climate FieldView Platform APIs via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Climate FieldView API use?

FieldView combines OAuth2 (authorization code) for user delegation with an X-Api-Key header that determines the partner's usage plan. Both must be present on calls. Through Jentic the X-Api-Key and OAuth tokens are stored encrypted in MAXsystem.

How do chunked uploads work in the FieldView API?

Files larger than 5MiB must be split into 5MiB chunks and sent via PUT /v4/uploads/{uploadId} with a Content-Range header per chunk. The maximum upload size is 500MiB. Initiate via POST /v4/uploads and poll status via GET /v4/uploads/{uploadId}/status.

What are the rate limits for the FieldView API?

Rate and quota limits are per-partner usage plans set when onboarded. Throttling violations return HTTP 429 with a Retry-After header. The exact burstLimit and rateLimit values are configured per X-Api-Key, not in the OpenAPI spec.

How do I upload a field boundary through Jentic?

Search Jentic for 'upload field boundary', load the POST /v4/boundaries schema, and execute with the polygon payload. Run pip install jentic to get started.

Can I query multiple boundaries in one request?

Yes. POST /v4/boundaries/query accepts a list of boundary IDs and returns all matching records, avoiding per-ID GET calls and helping stay under usage-plan quotas.

How does pagination work in FieldView?

Pagination uses headers: X-Limit (1-100, default 100) sets page size, and X-Next-Token in the response feeds back into the request to fetch the next page. A 304 indicates no results, 206 indicates more results remain.