Integrating with ZenKey is Easy

Whether you need to register first or are ready to access documentation right away, you’ll find everything you need here to quickly integrate ZenKey and enhance your customer experiences.

Here’s how to get started:
register
Register your Company
Register your company, configure your services, and obtain your client credentials.
sdk
Get the SDK
Download the SDKs and sample code for your platform (Android, iOS, and Web).
integration
Integrate your App
Start creating your ZenKey solution (Android, iOS, and Web)

trust
Need additional help to prevent fraud?
Add Trust Services to your ZenKey solution.
trust
Need additional help to prevent fraud?
Add Trust Services to your ZenKey solution.

Trust Services Guide

This document introduces Service Providers to ZenKey Trust Services. ZenKey Trust Services offers fraud prevention services to ZenKey's Service Providers; protecting users and application resources. ZenKey Trust Services are a collection of APIs and Event Alerts that help Service Providers obtain important notifications from participating ZenKey wireless carriers. These notifications provide Service Providers with actionable information that helps protect their users and prevent fraud.

ZenKey is a joint venture of three major US Participating ZenKey Wireless Carriers. The platform leverages technologies in a user's mobile phone and mobile network, and packages multiple factors of authentication into a streamlined experience for app and website providers. It takes advantage of the unique capabilities and insights of the Participating ZenKey Wireless Carriers, and applies an easy and secure way to register, login, and perform other types of authorizations within apps and services. The result for Service Providers is a better user experience for users. ZenKey makes integration easy by following the OpenID Connect (OIDC) authentication protocol.

Updated 4 months ago



Trust Services Guide


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.