canonical: https://jentic.com/apis/fieldviewplatformapi/fieldview

# Fieldviewplatformapi Climate FieldView Platform APIs

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.

## For AI agents

Manage agricultural fields, boundaries, and asPlanted/asHarvested data for digital agriculture, with chunked uploads and OAuth2 plus API-key auth across 28 endpoints.

## Scope

Does not handle weather forecasting, crop pricing, or equipment telematics - use for FieldView fields, boundaries, agronomic uploads, and grower operations only.

## Capabilities

- 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
- Resolve resource owners and farm organisations linking growers and partners
- Track upload status with token-based pagination for large result sets

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

| 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 |

## Key resources

- **Fields** — List and retrieve field records
- **Boundaries** — Upload and query field boundary polygons
- **FarmOrganizations** — Resolve grower farm organisations
- **ResourceOwners** — Look up resource owner identities
- **Operations** — List operations accessible to the user
- **Uploads** — Chunked upload of agronomic data files
- **Exports** — Initiate and retrieve agronomic data exports
- **Layers** — Access agronomic layers tied to fields

## Why Jentic

- **Setup:** Wiring the Climate FieldView Platform APIs by hand means combining the partner API-key request header with an OAuth2 token, polling upload status, and threading field and upload ids through the v4 routes yourself. Through Jentic you install once, import the Climate FieldView Platform APIs from the API Directory, store the key and token once, and your agent calls it.
- **Permission scoping:** FieldView puts the field id and upload id in the URL path (/v4/fields/{fieldId}, /v4/uploads/{uploadId}), so a rule can pin your agent to the fields and uploads you allow. You choose the operations it may call, so a write like posting a boundary or starting an upload is not included unless you add it.
- **Credential handling:** Your Climate FieldView partner key and OAuth2 token are stored once, encrypted, by your own Jentic One instance and injected at execution time. Neither the key nor the refresh token enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'upload a field boundary' or 'check an upload status', and Jentic returns the matching FieldView operation with its input schema, so the agent calls it without reading the platform.climate.com docs.

## Related APIs

- **Farmbrite API** — Farm management alternative for smaller mixed-operation growers
- **Agrimetrics API** — UK agronomic data layers that complement FieldView field records
- **Ambient Weather API** — On-farm weather station data to enrich FieldView field operations

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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 your Jentic One instance.

### 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.

### 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 your agent may use. You choose the operations it can call, so a write such as POST /v4/boundaries or starting an upload with POST /v4/uploads is excluded unless you add it. Since FieldView puts the field id and upload id in the URL path (/v4/fields/{fieldId}, /v4/uploads/{uploadId}), a rule can pin the agent to only the fields and uploads you permit.