Shop SDK lead capture now supports Rich Authorization Requests
Source: Shopify Dev Changelog
What Changed
Shopify has updated Shop SDK lead capture to support Rich Authorization Requests (RAR), a specification that lets apps request specific profile data fields from users during the lead capture flow. Previously, lead capture relied on a fixed set of fields tied to the user’s Shop profile. With this update, developers can now request data points that aren’t necessarily stored in that profile.
The implementation adds a new authorizationDetails attribute to the lead capture configuration. This attribute accepts a serialized JSON array specifying which fields are required for the app to function and which ones users can choose to skip. RAR is opt-in, meaning existing lead capture integrations continue to work without any code changes unless developers explicitly adopt the new attribute.
Why This Matters for Shopify App Developers
Lead capture is commonly used by apps to collect customer information during onboarding, checkout extensions, or marketing flows built on Shop SDK. The previous fixed-field model often forced developers to either request more data than needed or build custom workarounds to collect additional fields outside the standard flow. RAR support addresses this by giving developers granular control over data requests at the authorization layer, aligning with the OAuth-adjacent Rich Authorization Requests standard used in broader identity and authorization contexts.
Practical Implications
Developers building or maintaining Shop SDK lead capture integrations should review which profile fields their app actually requires and consider migrating to authorizationDetails to reduce friction for users who can skip optional fields. Since adoption is opt-in, there’s no immediate action required for existing implementations, but apps that currently work around missing fields with custom logic may be able to simplify their integration using this new attribute. Developers should consult the Shopify Dev documentation for the specific field schema and JSON structure expected by authorizationDetails.