---
source_url: "https://developer.pingidentity.com/orchsdks/index.html?utm_source=openai"
title: "Ping Orchestration SDKs | Orchestration SDKs"
mirrored_at: 2026-08-22T01:00:59.006Z
host: developer.pingidentity.com
cited_in_42a: true
mirror_canonical: "https://index.42a.ai/developer.pingidentity.com/orchsdks/index.html__q__utm_source_openai"
---

> **Original source:** https://developer.pingidentity.com/orchsdks/index.html?utm_source=openai

The Orchestration SDKs sit between your application and your identity platform.

They handle the orchestration loop, driving your app through each step of a DaVinci flow or Advanced Identity Cloud/PingAM journey all while abstracting away the underlying REST calls, token management, and protocol complexity.

Your server-side flows and journeys can evolve over time with new steps, new multi-factor authentication methods, risk decisions, and more, all without requiring a new app release.

Android, iOS, or JavaScript appIdentity PlatformClient AppPing Orchestration SDKIdentity PlatformClient AppClient AppPing Orchestration SDKPing Orchestration SDKIdentity PlatformIdentity PlatformIdentity Platform➊App initializes the SDK➋SDK connects and starts the flow or journeyloop\[Loop callbacks until success...\]➌Return callbacks➍Render callbacksCollect input from user or device➎Return completed callbacks➏Tokens returned to the app

Figure 1. How the Orchestration SDKs work

The overall authentication flow is as follows:

1 App initializes the SDK

Your app configures the Orchestration SDK with your environment, OAuth 2.0 client, and target orchestration platform.

2 SDK connects and starts the flow or journey

The Orchestration SDK opens a session with your authorization server and requests the first step of the configured flow or journey.

3 Platform returns callbacks

The platform responds with callbacks or collectors describing what is required to authenticate. For example, a username field or a FIDO assertion.

4 App renders the UI and collects input

Your app reads the callbacks and renders the appropriate UI to collect input from the user, or the device itself.

5 SDK advances repeat until complete

The Orchestration SDK submits responses and receives the next step.

If it contains new callbacks or collectors, it loops to collect the new input.

6 Tokens are surfaced to your app

On success, the Orchestration SDK surfaces OAuth 2.0 tokens to your app.

Your server-side flows can evolve at any time. No app re-release needed.