Hi,
using the COS blog posts API I could create blog posts till last week.
From then on we only got the HTTP code 403 with the error message CONTENT_SCOPE_RESTRICTED back.
I checked the access token and it has nearly all available scopes (including files and content).
What’s confusing is the endpoint is located at /content/api/v2/blog-posts but the error message mentions /blogs/v3/blog-posts as request url.
If I try /blogs/v3/blog-posts as endpoint I get another error message (PARENT_BLOG_DOES_NOT_EXIST)
The only thing changed was our blog domain. I tried a new domain for blog posts, but deleted that domain after some time.
{
"correlationId": "xxxx",
"errorTokens": {
"action": [
"create"
],
"contentId": [
"xxxx"
],
"contentType": [
"blog post"
]
},
"errorType": "CONTENT_SCOPE_RESTRICTED",
"message": "User does not have permission to create the blog post with id xxx. ",
"requestId": "xxxx",
"status": "error"
}
Yes, we are able to do it via the hapikey. Not so much deprecated, but isn’t an optimal solution, as only professional and enterprise users have access to hapikey. Email API for instance also seems to only support the hapikey and not oAuth. I mean, the Email API for creating an email, not the one listed in the help docs.
I don’t get an error. I get a response 200, the following header and no response body {'Date': 'Wed, 22 Mar 2017 21:57:35 GMT', 'Content-Length': '0', 'Connection': 'keep-alive', 'Access-Control-Allow-Credentials': 'false'}
At this stage all I am sending is this JSON { "name": "My first API blog post","content_group_id": 4308079277 }
to this URL: https://api.hubapi.com/content/api/v2/blog-posts?hapikey=xxx-xx-xx-xx