Mileiq Authentication

generated: '2026-07-20'
method: searched
source: https://developer.mileiq.com/api-reference/getting-started.md
docs: https://developer.mileiq.com/api-reference/getting-started
oidc_discovery: https://oauth2.mileiq.com/.well-known/openid-configuration
summary:
  types: [oauth2, openIdConnect]
  api_key_in: []
  oauth2_flows: [authorizationCode, clientCredentials, refreshToken, implicit]
  token_type: Bearer
  header: 'Authorization: Bearer <access_token>'
  note: >-
    The MileIQ External API OpenAPI does not declare securitySchemes; every operation
    takes an optional Authorization header. Authentication is documented in the developer
    portal as OAuth 2.1 (Authorization Code grant) against the oauth2.mileiq.com server,
    with the access token sent as a Bearer token. Client ID/Secret and redirect URI are
    issued by MileIQ on approved API-access requests.
schemes:
  - name: OAuth2
    type: oauth2
    description: >-
      OAuth 2.1 Authorization Code flow. Redirect the user to the authorization
      endpoint with response_type=code, client_id, scope, state; exchange the returned
      code at the token endpoint using the client credentials; call the API with the
      access token as a Bearer token; refresh with the refresh token.
    flows:
      - flow: authorizationCode
        authorizationUrl: https://oauth2.mileiq.com/oauth2/auth
        tokenUrl: https://oauth2.mileiq.com/oauth2/token
        refreshUrl: https://oauth2.mileiq.com/oauth2/token
    sources: [https://developer.mileiq.com/api-reference/getting-started]
  - name: OpenIDConnect
    type: openIdConnect
    openIdConnectUrl: https://oauth2.mileiq.com/.well-known/openid-configuration
    description: >-
      Full OIDC provider. grant_types_supported: authorization_code, implicit,
      client_credentials, refresh_token. code_challenge_methods_supported: plain, S256.
      token_endpoint_auth_methods_supported: client_secret_post, client_secret_basic,
      private_key_jwt, none. userinfo, revocation, and front/back-channel logout endpoints.
    endpoints:
      issuer: https://oauth2.mileiq.com/
      authorization_endpoint: https://oauth2.mileiq.com/oauth2/auth
      token_endpoint: https://oauth2.mileiq.com/oauth2/token
      userinfo_endpoint: https://oauth2.mileiq.com/userinfo
      jwks_uri: https://oauth2.mileiq.com/.well-known/jwks.json
      revocation_endpoint: https://oauth2.mileiq.com/oauth2/revoke
      end_session_endpoint: https://oauth2.mileiq.com/oauth2/sessions/logout
    sources: [https://oauth2.mileiq.com/.well-known/openid-configuration]
client_registration: >-
  Not self-service. A Client ID and Client Secret are issued by MileIQ per approved
  application; request access at https://mileiq.com/en-ca/for-business/api. The API is
  currently available on a request basis.