4.screen Mobility Experience Cloud API

The production 4.screen API. Automakers and mobility service providers integrate it into infotainment and navigation systems to render 4.screen content in the vehicle, and the 4.screen customer portal calls the same host for campaign management. The surface is OAuth 2.0 / OpenID Connect protected by a self-hosted Keycloak realm mounted at /auth on the same host, and a GraphQL endpoint is referenced by the portal application at /graphql. No OpenAPI, GraphQL SDL or public reference is published — every anonymous request to api.4screen.com returns HTTP 401 AUTHENTICATION_FAILED.

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/mobility-experience-cloud"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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

API entry from apis.yml

apis.yml Raw ↑
aid: 4screen:mobility-experience-cloud
name: 4.screen Mobility Experience Cloud API
description: The production 4.screen API. Automakers and mobility service providers integrate it into
  infotainment and navigation systems to render 4.screen content in the vehicle, and the 4.screen customer
  portal calls the same host for campaign management. The surface is OAuth 2.0 / OpenID Connect protected
  by a self-hosted Keycloak realm mounted at /auth on the same host, and a GraphQL endpoint is referenced
  by the portal application at /graphql. No OpenAPI, GraphQL SDL or public reference is published — every
  anonymous request to api.4screen.com returns HTTP 401 AUTHENTICATION_FAILED.
humanURL: https://4screen.com/4-automotives/
image: https://4screen.com/wp-content/uploads/2024/06/4screen_logo.svg
baseURL: https://api.4screen.com
tags:
- Advertising
- Automotive
- Mobility
- Navigation
- In-Car Commerce
properties:
- type: Authentication
  url: authentication/4screen-authentication.yml
- type: OAuthScopes
  url: scopes/4screen-scopes.yml
- type: OpenIDConnect
  url: well-known/4screen-openid-configuration.json