{"@context": "https://schema.org", "@type": "WebAPI", "name": "Climate FieldView Platform APIs API", "description": "**Last Modified**: Wed Jan 4 12:47:29 UTC 2023 All endpoints are only accessible via HTTPS. * All API endpoints are located at `https://platform.climate.com` (e.g. `https://platform.climate.com/v4/fields`). * The authorization token endpoint is located at `https://api.climate.com/api/oauth/toke", "provider": {"@type": "Organization", "name": "climate.com"}, "documentation": "https://dev.fieldview.com/openapi/platform.yaml"}
Index / APIs / climate.com

Climate FieldView Platform APIs API

**Last Modified**: Wed Jan 4 12:47:29 UTC 2023 All endpoints are only accessible via HTTPS. * All API endpoints are located at `https://platform.climate.com` (e.g. `https://platform.climate.com/v4/fields`). * The authorization token endpoint is located at `https://api.climate.com/api/oauth/toke

Every row below was read from the vendor's own OpenAPI document. The summary text is theirs. What this registry adds is that each operation is indexed with its method, path, base URL and auth scheme, so a search for a capability can answer with a call rather than a name, and that the endpoint is probed on a schedule.

Specifications as held by the APIs.guru corpus, whose newest record is 2023-04-21. Operations the vendor has added since are not listed here; the origin links above are the vendor's own current documents.

base URLs: https://platform.climate.com

auth: a p i k e y

find it by capability: POST /search {"query":{"text":"..."}} returns these operations with their invocation detail. Connect any agent client.

Climate FieldView Platform APIs v4.0.11

**Last Modified**: Wed Jan 4 12:47:29 UTC 2023 All endpoints are only accessible via HTTPS. * All API endpoints are located at `https://platform.climate.com` (e.g. `https://platform.climate.com/v4/fields`). * The authorization token endpoint is located at `https://api.climate.com/api/oauth/token`. ## Troubleshooting `X-Http-Request-Id` response header will be returned on every call, success

methodpathwhat the vendor says it does
POST/v4/boundariesUpload a boundary Upload a **Boundary** entry by passing the geometry of the boundary. This will store the bou
POST/v4/boundaries/queryRetrieve Boundaries in batch Retrieve multiple **Boundaries** (up to 10 per request). Boundaries
GET/v4/boundaries/{boundaryId}Retrieve a Boundary by ID Retrieve a **Boundary** by ID. Boundaries
POST/v4/exportsInitiate a new export request. Step one in requesting a data product. The method will return an **Export** ID
GET/v4/exports/{exportId}/contentsRetrieve the binary contents of a processed export request. Downloads larger than `5MiB` (`5242880 bytes`) in
GET/v4/exports/{exportId}/statusRetrieve the status of an Export. Check the status of an **Export** by ID. Exports
GET/v4/farmOrganizations/{farmOrganizationType}/{farmOrganizationId}Retrieve a specific farm organization by organization type and ID Retrieve a given **farm organization** by or
GET/v4/fieldsRetrieve list of Fields Retrieve list of **Fields**. Filter the results by field name if the `fieldName` query
GET/v4/fields/allRetrieve list of all Fields the user has access to. Retrieve all fields the authenticated user has access to,
GET/v4/fields/{fieldId}Retrieve a specific Field by ID Retrieve a given **Field** by ID. Fields
GET/v4/layers/asAppliedRetrieve a list of application activities Retrieve a list of application activities. The id in the response is
GET/v4/layers/asApplied/{activityId}/contentsRetrieve the raw application activity Retrieve an individual application activity by id. Ids are retrieved vi
GET/v4/layers/asHarvestedRetrieve a list of harvest activities Retrieve a list of harvest activities. The id in the response is used fo
GET/v4/layers/asHarvested/{activityId}/contentsRetrieve the raw harvest activity Retrieve an individual harvest activity by id. Ids are retrieved via the /
GET/v4/layers/asPlantedRetrieve a list of planting activities Retrieve a list of planting activities. The id in the response is used
GET/v4/layers/asPlanted/{activityId}/contentsRetrieve the raw planting activity Retrieve an individual planting activity by id. Ids are retrieved via the
GET/v4/layers/scoutingObservationsRetrieve a list of scouting observations Retrieve a list of scouting observations created or updated by the us
GET/v4/layers/scoutingObservations/{scoutingObservationId}Retrieve individual scouting observation Retrieve an individual scouting observation by id. Ids are retrieved
GET/v4/layers/scoutingObservations/{scoutingObservationId}/attachmentsRetrieve attachments associated with a given scouting observation. Retrieve attachments associated with a give
GET/v4/layers/scoutingObservations/{scoutingObservationId}/attachments/{attachmentId}/contentsRetrieve the binary contents of a scouting observation’s attachment. Photos added to scouting notes in the Fie
GET/v4/operations/allRetrieve the operations accessible to a a given user. Retrieve the **operations** accessible to the authentica
GET/v4/resourceOwners/{resourceOwnerId}Retrieve a resource owner by ID Retrieve a resource owner for the given `resourceOwnerId`. ResourceOwners
POST/v4/uploadsInitiate a new upload Step one in uploading a data product. The method will return an **Upload** ID which the
POST/v4/uploads/status/queryRetrieve Upload statuses in batch Check the status of multiple **Uploads** (up to 100 per request). Uploads
PUT/v4/uploads/{uploadId}Chunked upload of data Send chunked data for an **Upload**. Uploads
GET/v4/uploads/{uploadId}/statusRetrieve Upload status Check the status of an **Upload** by ID. Uploads

specification origin: https://dev.fieldview.com/openapi/platform.yaml

nothing on this page is a rating, an endorsement or a claim about quality. Reachability is what our probes observed from one network; answering is a floor under usefulness, not a measure of it.