Feature request:
Add separate read and write scopes for “content” scope so that API access can be limited to only read blog posts without the write access
Current:
- The private app access token with scope “content” can make both of these API calls:
- GET/cms/v3/blogs/posts
- POST/cms/v3/blogs/posts
Expected:
- The private app access token has separate read and write “content” scope so that:
- read: can only make this API call GET/cms/v3/blogs/posts (without the POST access)
- write: can only make this API call POST/cms/v3/blogs/posts
This is based on the community topic here
Thanks.