Hey @panos_supersell_club 
You’re right,. read_own_subscription_contracts is scoped strictly to contracts your app created, and there’s no broader Admin API scope that gives cross-app visibility. Subscription webhooks (subscription_contracts/create, /update, /cancel, etc.) follow the same ownership model, so a non-subscription app won’t receive events from Shopify Subscriptions or any other subscription provider.
If you’re building on Hydrogen or a Headless storefront, the Customer Account API has a customer_write_subscription_contracts scope that provides access to all subscription contracts regardless of which app created them.
For the Admin API path, the most practical pattern is using Shopify Flow as a bridge. Flow has “Subscription contract created” and “Subscription contract updated” triggers that fire for any subscription app, including the 1P Shopify Subscriptions app. The “updated” trigger fires on status changes (active, paused, cancelled), so you’d add a condition checking the contract status and then use the “Update customer metafield” action to write something like custom.subscription_status. Your app can then read that metafield with the read_customers scope. It requires the merchant to set up the Flow, but it does get you a near-real-time, app-agnostic subscription states.
I covered this same limitation in a similar thread where the workarounds are discussed in more detail.