Request an OAuth 2.0 access token that identifies your identity

post

https://Use API Lookup for a base URL/oauth2/token

Grant Types:

Request a client token that identifies your application by providing your client credentials.
- Use grant type - client_credentials
- An optional scope can be added to the request body to request a project scoped access token
- This API requires clients to use certain OAuth Core signature headers. The request must be signed with the provisioned client access key secret (here.access.key.secret) as documented in Signing Requests
- Developers may wish to try out the sample Java code in documentation demonstrating this API

Create a new HERE access token via exchange of an existing trusted OpenID Connect Identity Provider access token.
- Use grant type - urn:ietf:params:oauth:grant-type:token-exchange
- Client authentication via the Authorization header is not required
- The subject_token identifies the access context in the third-party issuer's identity namespace, and the "sub" claim within that token uniquely identifies the security principal within that identity provider's namespace
- If used with a IdentityProvider that is configured for accountType=device, and a "sub" claim is present, a DeviceAccount is created upon first token exchange and re-used for subsequent tokens with the same "sub" claim value
- See also OAuth 2.0 Token Exchange

Sign In with OpenID Connect compliant OEM token
- Use grant type - jwtIssNotHERE
- The OEM access token is used in the authorization header

Body Params

grantType

string

enum

required

Always "client_credentials" for this operation.

Allowed:

expiresIn

integer

Number of seconds before token expires, must number zero or more. Ignored if greater than default expiration of the application.

tokenFormat

string

enum

Supported token formats are hN, jwt, jwt+header and jws.

'hN' produces a HERE proprietary-formatted access token.
'jwt' produces a Nested JWT-formatted access token with a JWE enclosed in a JWS.
'jwt+header' produces a Nested JWT-formatted access token with a JWE enclosed in a JWS with additional claims copied into the JOSE header.
'jws' produces a JWS-formatted access token with a JWS Payload containing the plaintext JWT Claims Set.

Allowed:

scope

string

Requested scope of the access token. Must be an HRN identifying a project that the identified client has access to.

deviceId

string

Anonymous Device id. Supported only if client has deviceTokenCreationEnabled flag enabled. On success, token will contain 'did' claim.

Headers

content-type

string

enum

Defaults to application/json

Generated from available request content types

Allowed:

Responses