HERE

HERE List Apps for an Identity Provider API

List the Apps that have the specified Identity Provider attached.

Documentation GitHub OpenAPI

Operations 1

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /realms/{realm}/identityProviders/{identityProvider}/apps List apps using an identity provider · List the Apps which have attached the specified Identity Provider #

Ask an LLM

“Which applications have attached a particular identity provider in my realm?”

“Can I choose which app fields come back when listing apps for an identity provider?”

Tell an agent

List the apps attached to identity provider {identityProvider} in realm {realm}.

Show which apps in my realm {realm} use identity provider {identityProvider}, returning fields {fields}.

Documentation

https://docs.here.com/identity-and-access-management/docs

https://docs.here.com/identity-and-access-management/reference

https://docs.here.com/data-api/docs

https://docs.here.com/data-api/reference

https://docs.here.com/usage/docs

https://docs.here.com/usage/reference

https://docs.here.com/destination-weather/docs

https://docs.here.com/destination-weather/reference

https://docs.here.com/ev-products/docs

https://docs.here.com/ev-products/reference

https://docs.here.com/fuel-prices/docs

https://docs.here.com/fuel-prices/reference

https://docs.here.com/geocoding-and-search/docs

https://docs.here.com/geocoding-and-search/reference

https://docs.here.com/routing/docs

https://docs.here.com/routing/reference

https://docs.here.com/positioning/docs

https://docs.here.com/positioning/reference

https://docs.here.com/indoor-map/docs

https://docs.here.com/indoor-map/reference

https://docs.here.com/transit/docs

https://docs.here.com/transit/reference

https://docs.here.com/map-attributes/docs

https://docs.here.com/map-attributes/reference

https://docs.here.com/map-rendering/docs

https://docs.here.com/map-rendering/reference

https://docs.here.com/workspace/docs

https://docs.here.com/workspace/reference

https://docs.here.com/tour-planning/docs

https://docs.here.com/tour-planning/reference

https://docs.here.com/tracking/docs

https://docs.here.com/tracking/reference

https://docs.here.com/traffic-api/docs

https://docs.here.com/traffic-api/reference

https://docs.here.com/wego-pro/docs

https://docs.here.com/wego-pro/reference

Specifications

https://artifacts.apis.io/here/openapi/here-list-apps-for-an-identity-provider-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/here:here-list-apps-for-an-identity-provider-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: Authentication API v1.1 List Apps for an Identity Provider…
  version: 1.1.x
  description: 'This specification describes the Authentication v1.1 APIs.

    NOTE: Swagger UI automatically URL encodes parameters when required.

    If/when the APIs are called elsewhere make sure to URL encode the parameters when required.'
servers:
- url: Use API Lookup for a base URL
tags:
- name: List Apps for an Identity Provider
  description: List the Apps that have the specified Identity Provider attached.
paths:
  /realms/{realm}/identityProviders/{identityProvider}/apps:
    parameters:
    - $ref: '#/components/parameters/Realm'
    - $ref: '#/components/parameters/IdentityProvider'
    - $ref: '#/components/parameters/XRequestId'
    - $ref: '#/components/parameters/XCorrelationId'
    - $ref: '#/components/parameters/PageToken'
    - $ref: '#/components/parameters/Limit'
    get:
      tags:
      - List Apps for an Identity Provider
      summary: List the Apps which have attached the specified Identity Provider
      operationId: listAppsForProvider
      description: 'List the Apps that have attached the specified Identity Provider.


        Access Control:

        * The calling principal must have either **"read"** or **"readIdentityProviders"** action permission for the resource **"{app}"** in the **"account"** service.

        * The calling principal MUST NOT include a project scope.'
      parameters:
      - in: query
        required: false
        name: fields
        schema:
          type: string
        description: "Comma-separated list of fields to return, for each App.  \nBy default, only the App \"hrn\" is returned for each App. \nAdditional supported fields also include \"id\" and \"name\".\n"
        example: hrn,id,name
      responses:
        '200':
          description: OK
          headers:
            X-Correlation-ID:
              $ref: '#/components/headers/XCorrelationId'
            X-Request-ID:
              $ref: '#/components/headers/XRequestId'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AppList'
              example:
                count: 1
                total: 1
                items:
                - hrn: hrn:here:account::org123456789:app/AfRcv675i2zYubYTe17D
                  id: AfRcv675i2zYubYTe17D
                  name: My IdP Federation Application
        '400':
          description: 'Bad Request.

            * E110000 - Missing required field, etc.

            '
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorMessage'
          headers:
            X-Correlation-ID:
              $ref: '#/components/headers/XCorrelationId'
            X-Request-ID:
              $ref: '#/components/headers/XRequestId'
        '401':
          description: 'Missing or invalid Authorization header.

            '
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorMessage'
          headers:
            X-Correlation-ID:
              $ref: '#/components/headers/XCorrelationId'
            X-Request-ID:
              $ref: '#/components/headers/XRequestId'
        '403':
          description: 'An error has occurred.

            * E110000 - Subject does not have the required "manageIdentityProviders" access to the Realm.

            '
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorMessage'
          headers:
            X-Correlation-ID:
              $ref: '#/components/headers/XCorrelationId'
            X-Request-ID:
              $ref: '#/components/headers/XRequestId'
      security:
      - Bearer: []
components:
  schemas:
    App1:
      type: object
      properties:
        hrn:
          type: string
          description: HRN for the App
          example: hrn:here:account::org123456789:app/AfRcv675i2zYubYTe17D
        id:
          type: string
          description: ID for the App
          example: AfRcv675i2zYubYTe17D
        name:
          type: string
          description: Human readable name of the client. This field is required unless a clientId is provided.
          example: My IdP Federation Application
    ErrorMessage:
      type: object
      required:
      - title
      - status
      - code
      - cause
      - action
      - correlationId
      example:
        title: Input data failed validation
        status: 400
        code: E110000
        cause: The input data in question does not meet validation rules
        action: Actionable instructions for the user.
        correlationId: 6c1bce6d-d31f-4275-9d9f-6832d8ba2377
      properties:
        title:
          type: string
          description: Title of the error.
        status:
          type: integer
          minimum: 0
          maximum: 999
          description: HTTP status code of error message.
        code:
          type: string
          description: Identifier for the detailed error code for programmatic error handling.
        cause:
          type: string
          description: The cause of the error.
        action:
          type: string
          description: Actionable instructions for the user.
        correlationId:
          type: string
          description: The Correlation ID for the request for tracking purposes.
    AppList:
      type: object
      required:
      - count
      - total
      - items
      properties:
        count:
          type: integer
          description: The number of Apps in this page of the List.
        total:
          type: integer
          description: The total number of Apps in the List.
        items:
          type: array
          items:
            $ref: '#/components/schemas/App1'
          description: List of Apps.
        pageToken:
          type: string
          description: "A pointer to the next page of results, if any.  \nNot present if there are no more results after the current page.\n"
  parameters:
    XCorrelationId:
      in: header
      name: X-Correlation-ID
      schema:
        type: string
      required: false
      description: 'Correlates HTTP requests between a client and server. If not present in the incoming request, it will be generated. This header and value will be included in all loglines including access logs. It will also be propagated to downstream services and returned in the response.

        '
    XRequestId:
      in: header
      name: X-Request-ID
      schema:
        type: string
      required: false
      description: 'The unique for the request, used to track this request within the service. X-Request-ID value is NOT propagated to the downstream services.

        '
    IdentityProvider:
      in: path
      required: true
      name: identityProvider
      schema:
        type: string
      description: 'HRN identifying the IdentityProvider.

        '
      example: hrn:here:account::org123456789:identityProvider/example-op
    Limit:
      in: query
      name: limit
      required: false
      description: Number of records to return. Default is 100 records. Maximum is 100 records.
      schema:
        type: integer
        minimum: 0
        maximum: 100
        default: 100
    Realm:
      in: path
      required: true
      name: realm
      schema:
        type: string
      description: "HRN identifying the Realm.  You can also use the shorthand \"me\" to refer to the Realm HRN indicated by your \naccess token context.\n"
      example: hrn:here:account::org123456789:realm/org123456789
    PageToken:
      name: pageToken
      in: query
      required: false
      description: 'If there are more records than ''limit'' (between 1 and 100), and there are multiple pages of records, ''pageToken'' allows for retrieval of individual pages. In order to retrieve subsequent pages, the client should provide the pageToken returned in the result from the previous API call as input to the following API call.


        Example: If the result for a call to GET /items returns *{..., "pageToken": "abcdefg"}*, in order  to retrieve the next page of ''items'' the client should call GET /items?pageToken=abcdefg

        '
      schema:
        type: string
  headers:
    XRequestId:
      schema:
        type: string
      required: false
      description: The unique id for the request, used to track this request within the service. X-Request-ID value is NOT propagated to the downstream services.
    XCorrelationId:
      schema:
        type: string
      required: false
      description: The X-Correlation-ID for the request, used to track this request in the platform. X-Correlation-ID value is propagated throughout the platform.
  securitySchemes:
    UserOrClientBearerToken:
      type: http
      scheme: bearer
      description: Bearer Token issued to either User or Client.
    Bearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: 'A HERE access 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://www.here.com/docs/bundle/identity-and-access-management-developer-guide/page/README.html](Identity & Access Management Guide).

        '
externalDocs:
  description: The developer guide and related API references are available here.
  url: https://www.here.com/docs/category/identity-and-access-management