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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Open Geospatial Consortium (OGC)

OGC API - Records

The approved standard OpenAPI description OGC itself publishes for OGC API - Records. This is the STANDARD'S contract, not any one deployment of it — the servers block is a template, so it describes what a conformant implementation must offer rather than a callable host.

Documentation Provider Profile APIs.io OpenAPI GitHub

OGC API - Records is one of 10 APIs that Open Geospatial Consortium (OGC) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include OGC, OGC API, OGC API Records, Geospatial, and Specification. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 7 operations across 7 paths, organized into 7 resource areas, and defines 35 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against 2 base URLs: https://example.org/data, https://example.org/data-dev.

7 operations 7 paths 35 schemas 7 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Servers
https://example.org/data
https://example.org/data-dev
Authentication
OpenID Connect
Contact
CubeWerx Inc.
License
CC-BY 4.0 license
Resource Areas
7

Authentication & Security 1

OGC API - Records declares 1 security scheme for authenticating requests. It supports OpenID Connect (openIdConnect) discovered at https://accounts.google.com/.well-known/openid-configuration. By default, every request must be authenticated.

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 7 GET. They span 7 resource areas: Capabilities, Conformance, Collections, Collection, Sortables, Records, Record. Each is listed below with its method, path, parameters, and response codes.

Capabilities 1

essential characteristics of this API

GET
/
landing page
getLandingPage 2 params → 2004XX4065XX
Conformance 1

list of conformance classes implemented by this API

GET
/conformance
information about specifications that this API conforms to
getConformanceDeclaration → 2004XX4065XX
Collections 1

list of catalogs offered by this API

GET
/collections
the record collections
getCollections 10 params → 2004XX4065XX
Collection 1

description of a catalog offered by this API

GET
/collections/{catalogId}
describe the record collection with id catalogId
describeCollection 3 params → 2004XX4044065XX
Sortables 1

list of record properties by which responses can be sorted

GET
/collections/{catalogId}/sortables
get the list of sortable properties
getSortables 3 params → 2004XX4044065XX
Records 1

access to records

GET
/collections/{catalogId}/items
fetch records
getRecords 11 params → 2004XX4044065XX
Record 1

access to a single record

GET
/collections/{catalogId}/items/{recordId}
fetch a single record
getRecord 4 params → 2004XX4044065XX

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are recordCommonProperties (15 properties), contact (12 properties), recordGeoJSON (8 properties), linkBase (8 properties). Each schema is shown below with its type and property counts.

f-collections
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/collections.yaml
2 properties 2 required
f-collection
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/collection.yaml
7 properties 2 required
f-extent
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/extent.yaml The extent of the featur…
2 properties
featureCollectionGeoJSON
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/featureCollectionGeoJSON.yaml
6 properties 2 required
featureGeoJSON
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/featureGeoJSON.yaml
5 properties 3 required
geometryGeoJSON
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/geometryGeoJSON.yaml
pointGeoJSON
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/pointGeoJSON.yaml
2 properties 2 required
multipointGeoJSON
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/multipointGeoJSON.yaml
2 properties 2 required
linestringGeoJSON
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/linestringGeoJSON.yaml
2 properties 2 required
multilinestringGeoJSON
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/multilinestringGeoJSON.yaml
2 properties 2 required
polygonGeoJSON
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/polygonGeoJSON.yaml
2 properties 2 required
multipolygonGeoJSON
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/multipolygonGeoJSON.yaml
2 properties 2 required
geometrycollectionGeoJSON
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/geometrycollectionGeoJSON.yaml
2 properties 2 required
exception
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/exception.yaml
2 properties 1 required
format
object
2 properties
f-landingPage
object
Imported from OGC API - Features - Part 1: Core See: https://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/schemas/landingPage.yaml
3 properties 1 required
confClasses
object
1 property 1 required
catalogCommonProperties
catalogs
catalog
contact
object
Identification of, and means of communication with, person responsible for the resource.
12 properties
defaultSortOrder
array
landingPage
language
object
The language used for textual values in this record.
4 properties 1 required
license
string
A legal document under which the resource is made available. If the resource is being made available under a common license then use an SPDX license id (https:…
linkBase
object
8 properties
linkTemplate
link
object
recordCollectionGeoJSON
recordCommonProperties
object
15 properties
recordGeoJSON
object
8 properties 4 required
roles
array
The list of duties, job functions or permissions assigned by the system and associated with the context of this member.
scheme
object
3 properties 2 required
theme
object
2 properties 2 required
time
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ogc-records-part1-1-0-openapi-ogcapi-records-1-example-all-in-one.yaml Raw ↑

Other APIs Open Geospatial Consortium (OGC) publishes across the network.

OGC API - Common
AE Profile APIs.io
OGC API - Connected Systems
AE Profile APIs.io
OGC API - DGGS
AE Profile APIs.io
OGC API - EDR
AE Profile APIs.io
OGC API - Features
AE Profile APIs.io
OGC API - Maps
AE Profile APIs.io
OGC API - Moving Features
AE Profile APIs.io
OGC API - Processes
AE Profile APIs.io
OGC API - Tiles
AE Profile APIs.io
#OGC#OGC API#OGC API Records#Geospatial#Specification
← Back to O APIs
API Details
ID
ogc:ogc-api-records
Server
https://example.org/data
Docs
https://ogcapi.ogc.org/records/
Provider
Open Geospatial Consortium (OGC)
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=ogc-api-records&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/ogc-api-records"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of OGC API - Records, 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.