hey, u might need to check if the page is shered properly with your intgration. sometimes its not a coding error but permission issues so double-check your share settings and token rights.
The error might stem from a misconfiguration in how integrated pages handle embedded resources. Despite ensuring the primary page is shared properly, the integration can sometimes treat linked database objects as separate entities requiring explicit permissions. In my experience, even when all share settings appear to be in order, removing and re-establishing the connection for every embedded resource resolved similar issues. I suggest reviewing the sharing settings for all related databases, and if necessary, re-sharing them to ensure the API has access to all required components.
In troubleshooting a similar problem, I learned that the issue wasn’t always with the main page’s sharing settings. In one instance, my integration was working fine for the primary content but failing when attempting to retrieve data tied to a related database element. It turned out that certain permissions weren’t being passed along in the API call due to token configuration issues. I had to check the full integration setup, including updating the access tokens to ensure all embedded resources were recognized. Reviewing and aligning permission settings across all related components resolved that problem.
maybe your token is outdated? i had a simmiler problem and fixed it by refreshing my integration token. sometimes notion caches old session data causing these inconsistencies. try reauthenticating and ensure you re-share if needed.