How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Microsoft Azure PlantingData API

The PlantingData API from Microsoft Azure — 5 operation(s) for plantingdata.

Microsoft Azure PlantingData API is one of 1667 APIs that Microsoft Azure publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include PlantingData. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, pricing, a JSON-LD context, and a getting-started guide.

This API exposes 8 operations across 5 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 2020-08-01-preview.

8 operations 5 paths 14 schemas 1 DELETE4 GET1 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2020-08-01-preview
Resource Areas
1

Paths & Operations 8

Across 5 paths, the API surfaces 8 operations — 1 DELETE, 4 GET, 1 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

PlantingData 8
GET
/parties/{partyId}/planting-data
Microsoft Azure Get Parties Partyid Planting Data
microsoftAzurePlantingdataListbypartyid 28 params → 200default
GET
/parties/{partyId}/planting-data/{plantingDataId}
Microsoft Azure Get Parties Partyid Planting Data Plantingdataid
microsoftAzurePlantingdataGet 3 params → 200default
PATCH
/parties/{partyId}/planting-data/{plantingDataId}
Microsoft Azure Patch Parties Partyid Planting Data Plantingdataid
microsoftAzurePlantingdataCreateorupdate 3 params body → 200201default
DELETE
/parties/{partyId}/planting-data/{plantingDataId}
Microsoft Azure Delete Parties Partyid Planting Data Plantingdataid
microsoftAzurePlantingdataDelete 3 params → 204default
GET
/planting-data
Microsoft Azure Get Planting Data
microsoftAzurePlantingdataList 27 params → 200default
PUT
/planting-data/cascade-delete/{jobId}
Microsoft Azure Put Planting Data Cascade Delete Jobid
microsoftAzurePlantingdataCreatecascadedeletejob 4 params → 202default
GET
/planting-data/cascade-delete/{jobId}
Microsoft Azure Get Planting Data Cascade Delete Jobid
microsoftAzurePlantingdataGetcascadedeletejobdetails 2 params → 200default
POST
/planting-data:search
Microsoft Azure Post Planting Data:search
microsoftAzurePlantingdataSearch 3 params body → 200default

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are SearchPlantingDataQuery (27 properties), PlantingData (22 properties), PlantingDataMetaData (21 properties), CascadeDeleteJob (12 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
An error response from the Azure AgPlatform service. See https://github.com/Microsoft/api-guidelines/blob/vNext/Guidelines.md7102-error-condition-responses for…
2 properties
PlantingDataMetaDataListResponse
object
Paged response contains list of requested objects and a skipToken to get the next set of results.
3 properties 1 required
GeoJsonObjectType
string
GeoJSON object type.
PlantingData
object
Schema of planting data resource.
22 properties
Error
object
An error from the Azure AgPlatform service.
5 properties 2 required
CascadeDeleteJob
object
Schema of cascade delete job.
12 properties 3 required
PlantingDataListResponse
object
Paged response contains list of requested objects and a URL link to get the next set of results.
3 properties 1 required
Measure
object
Schema for storing measurement reading and unit.
2 properties
SearchPlantingDataQuery
object
SearchPlantingDataQuery.
27 properties
GeoResource
object
Schema for storing resource type and resource id.
2 properties
GeoJsonObject
object
GeoJSON (For more details: https://geojson.org/). Note: Coordinates are expected in [Longitude, Latitude] format.
1 property 1 required
InnerError
object
Inner error containing list of errors.See https://github.com/Microsoft/api-guidelines/blob/vNext/Guidelines.mdinnererror--object for InnerError reference docum…
2 properties
PlantingDataMetaData
object
Schema of planting data resource.
21 properties
PlantingProductDetail
object
Schema for Planting product detail.
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-azure-plantingdata-api-openapi.yml Raw ↑

Other APIs Microsoft Azure publishes across the network.

Microsoft Azure AI Search API
Microsoft Azure Communication Services API
Microsoft Azure Event Grid API
Microsoft Azure Functions API
Microsoft Azure DevOps REST API
Microsoft Azure AI Foundry API
Microsoft Azure Resource JSON Schema
Microsoft Azure JSON-LD Context
Microsoft Azure AccessConnector API
Microsoft Azure AccessControlRecords API
Microsoft Azure AccessPolicies API
Microsoft Azure AccessReviewInstanceAcceptRecommmendations API
Where this information came from

This is an independent, third-party profile of Microsoft Azure PlantingData API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.