New: OpenID Connect for privacy-conscious authentication

We just launched OpenID Connect  (OIDC) support for the Planning Center API, giving you the most privacy-conscious way to authenticate users and verify their identity.OIDC lets you authenticate Planning Center users with minimal data access. By requesting only the openid scope, your application gets verified user identity (name, email, organization) without requiring broader permissions to church data. It's perfect for applications that need to know "who is this user?" without needing access to their Planning Center database.

Key features

• Standard OIDC discovery endpoint for automatic client configuration (https://api.planningcenteronline.com/.well-known/openid-configuration )

• ID tokens with essential user identity claims

• Fresh user data available via /oauth/userinfo endpoint

• Built-in support for security best practices (state, nonce, prompt parameters)

Getting started

Your existing OAuth 2.0 integrations work exactly as before—this is purely additive. For identity-only authentication, request the openid scope. You can still combine it with other scopes if your application needs broader data access.We've updated our developer documentation with code examples and integration patterns. As always, we recommend using established OIDC client libraries rather than rolling your own implementation.Questions? Hit reply or check out the full documentation here .