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

GEMS Informatics Exchange APIs

Ten agricultural, climate and geospatial data APIs operated by GEMS Informatics at the University of Minnesota — biotic risk, climate, crop calendar, elevation, hydrology, land cover, market accessibility, pedigree tools, soils and weather. Each is a separately versioned FastAPI deployment behind one gateway, and nine of the ten publish a live OpenAPI 3.1 document anonymously. Data paths require an `apikey` header obtained from the GEMS portal; the contracts do not declare that requirement. This is the only surface where the University publishes machine-readable contracts of its own.

GEMS Informatics Exchange APIs is one of 10 APIs that University of Minnesota publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Geospatial, Agriculture, Climate, Weather, and Soils. The published artifact set on APIs.io includes API documentation, an API reference, an OpenAPI specification, and 1 JSON Schema.

This API exposes 20 operations across 14 paths, and defines 14 schemas. It is described by OpenAPI 3.1.0, at version 2.0.

Requests are made against a single base URL, https://exchange-1.gems.msi.umn.edu/soil/v2.

20 operations 14 paths 14 schemas 14 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0
Base URL
https://exchange-1.gems.msi.umn.edu
Contact
Resource Areas
1

Paths & Operations 20

Across 14 paths, the API surfaces 20 operations — 14 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

dataset 20
GET
/grid
Get All Grids
get_all_grids_grid_get 1 param → 200422
GET
/grid/{id}
Get Grid
get_grid_grid__id__get 2 params → 200422
GET
/datasets
Get Datasets
get_datasets_datasets_get 1 param → 200422
GET
/{keyname}/object/search
Get Search Object
get_search_object__keyname__object_search_get 7 params body → 200422
POST
/{keyname}/object/search
Post Search Object
post_search_object__keyname__object_search_post 6 params body → 200422
GET
/{keyname}/object/{id}
Get Object Metadata
get_object_metadata__keyname__object__id__get 3 params → 200422
GET
/{keyname}/object/{id}/point
Get Object Point
get_object_point__keyname__object__id__point_get 5 params → 200422
GET
/{keyname}/object/{id}/envelope
Get Object Envelope
get_object_envelope__keyname__object__id__envelope_get 3 params → 200422
GET
/{keyname}/object/{id}/raster
Get Object Spatial
get_object_spatial__keyname__object__id__raster_get 5 params → 200422
POST
/{keyname}/object/{id}/raster
Post Object Spatial
post_object_spatial__keyname__object__id__raster_post 4 params body → 200422
GET
/{keyname}/object/{id}/stats
Get Object Stats
get_object_stats__keyname__object__id__stats_get 4 params → 200422
POST
/{keyname}/object/{id}/stats
Post Object Stats
post_object_stats__keyname__object__id__stats_post 3 params body → 200422
GET
/{keyname}/object/{id}/histogram
Get Object Hist
get_object_hist__keyname__object__id__histogram_get 5 params → 200422
POST
/{keyname}/object/{id}/histogram
Post Object Hist
post_object_hist__keyname__object__id__histogram_post 4 params body → 200422
GET
/{keyname}/object/{id}/quantiles
Get Object Quantiles
get_object_quantiles__keyname__object__id__quantiles_get 5 params → 200422
POST
/{keyname}/object/{id}/quantiles
Post Object Quantiles
post_object_quantiles__keyname__object__id__quantiles_post 4 params body → 200422
GET
/{keyname}/object/{id}/valuecount
Get Object Value Count
get_object_value_count__keyname__object__id__valuecount_get 4 params → 200422
POST
/{keyname}/object/{id}/valuecount
Post Object Value Count
post_object_value_count__keyname__object__id__valuecount_post 3 params body → 200422
GET
/{keyname}/layer
Get All Layers
get_all_layers__keyname__layer_get 2 params → 200422
GET
/{keyname}/layer/{id}
Get Layer
get_layer__keyname__layer__id__get 3 params → 200422

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are ObjectOut (9 properties), GridDetails (7 properties), StatsOut (6 properties), LayerOut (5 properties). Each schema is shown below with its type and property counts.

Body_get_search_object__keyname__object_search_get
object
2 properties
CompressEnum
string
DatasetOut
object
5 properties 5 required
GridDetails
object
7 properties 7 required
HTTPValidationError
object
1 property
Histogram
object
4 properties 4 required
LayerOut
object
5 properties 5 required
ObjectOut
object
9 properties 9 required
Quantile
object
2 properties 2 required
StatsOut
object
6 properties 6 required
TimeRangeOut
object
2 properties 2 required
ValidationError
object
3 properties 3 required
ValueCount
object
2 properties 2 required
ValueOut
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-minnesota-gems-exchange-soil-openapi.yml Raw ↑

Other APIs University of Minnesota publishes across the network.

Common Good APIs
UMedia Digital Collections JSON API
UMN Digital Conservancy — OAI-PMH and DSpace REST
InCommon Identity Federation — University of Minnesota Shibboleth IdP
DataCite membership — University of Minnesota
Crossref membership — University of Minnesota
ROR registration — University of Minnesota
Boomi API Developer Portal (UMN tenant)
UMedia IIIF image delivery (OCLC CONTENTdm tenant)
Where this information came from

This is an independent, third-party profile of GEMS Informatics Exchange APIs, 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.