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

HERE Authorization Server Metadata API

The Authorization Server Metadata API from HERE — 2 operation(s) for authorization server metadata.

HERE Authorization Server Metadata API is one of 139 APIs that HERE publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authorization Server Metadata. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.2.0.

Requests are made against a single base URL, https://account.api.here.com.

2 operations 2 paths 2 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2.0
Base URL
https://account.api.here.com
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

HERE Authorization Server Metadata API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (OAuth). It accepts HTTP bearer tokens (JWT) (Bearer).

  • OAuth — OAuth [OAuth 1.0 Signing Process](http://oauth.net/core/1.0/signingprocess). Used for clientcredentials grant when NOT using JWT assertion authentication.
  • Bearer — A token obtained from one of the supported OAuth 2.0 authorization flows. For more information on how to get a bearer token, see the [https://developer.here.co…

Paths & Operations 2

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

Authorization Server Metadata 2
GET
/.well-known/oauth-authorization-server
Get OAuth Authorization Server Metadata
OAuth2.0AccessTokenGetAuthServerMetadata → 200
GET
/.well-known/oauth-authorization-server/mcp
Get MCP OAuth Authorization Server Metadata
OAuth2.0AccessTokenGetMcpAuthServerMetadata → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are MCPAuthServerMetadata (9 properties), AuthServerMetadata (6 properties). Each schema is shown below with its type and property counts.

AuthServerMetadata
object
6 properties
MCPAuthServerMetadata
object
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

here-authorization-server-metadata-api-openapi.yml Raw ↑

Other APIs HERE publishes across the network.

HERE Geocoding and Search API
HERE Autosuggest API
HERE Tour Planning API
HERE Public Transit API
HERE Destination Weather API
HERE Map Tile API
HERE Map Image API
HERE Tracking API
HERE Positioning API
HERE Parking API
HERE Platform Data API
HERE HD Live Map
Where this information came from

This is an independent, third-party profile of HERE Authorization Server Metadata 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.