Arun
UX Case Studies02 / 05

UX case study · Enterprise platform

Tekion OpenAPI

Tekion is a US cloud-based automotive platform that brings dealerships, OEMs and customers into one ecosystem. OpenAPI is how internal teams and third-party developers build services on top of it.

Open API — Figma file
CompanyTekion
ProductOpenAPI developer console
DomainAutomotive cloud, US
Timeline2022 — 2024
Tekion OpenAPI — API selection screen where a developer picks which APIs to build against
Fig. 01The API catalogue — a developer picks which domains to build against
“
Discover an API, get scoped access, prove you're safe, go to production — then stay healthy there.

01Modules I worked on

End to end

The developer console spans the full lifecycle — discover an API, get scoped access, prove you're safe, go to production, stay healthy there. I designed across it end to end.

01Access & credentials

The path from a sandbox key to trusted production access.

Digital CertificateProduction CredentialsIP Whitelisting
02Security & review

The gate an integration passes before it can go live.

Certification tab
03Partner administration

Who on a partner team can act, and for which dealerships.

Admin ControlsMultiple User RolesDealer Management
04Operations & health

What a developer watches once they're in production.

API HealthSupport DashboardWebhooks
05Platform

The foundations under every module.

Basic Feed SubscriptionAPI IconsDesign V2.0

The API catalogue lets a developer pick which domains to build against, with each API's scope and access model visible before a key is ever issued.

Tekion OpenAPI — API selection detail with scopes and access
Fig. 02Each API with its scope and access model, before a key is ever issued

02Support Dashboard & API Health

Once a partner is in production, the question shifts from "can I get access" to "is it working right now."

Support Dashboard

One place to monitor the API endpoints an integration depends on: request volume, error rates, and where a failing call is coming from. Drill into one endpoint for volume, errors and source.

API Health

The live status of each API, so a developer can tell a Tekion-side incident apart from a bug in their own code before they open a ticket.

OpenAPI Support Dashboard — endpoint monitoring overview
Fig. 03Support Dashboard — endpoints an integration depends on, at a glance
OpenAPI Support Dashboard — per-endpoint detail
Fig. 04Drill into one endpoint: volume, errors, source
OpenAPI API Health — live status of each API
Fig. 05API Health — live status of every API
OpenAPI API Health — incident detail view
Fig. 06Is it us or is it them — answered before a ticket is filed

03The through-line

The same publishing-and-lifecycle spine as Hike — discover, get scoped access, prove you're safe, widen exposure — but at enterprise scale and with contracts attached.

Next case study

03 / 05