Tweet
We are implementing a direct integration between our self-hosted n8n automation environment and the Blog2Social REST API. We have reached an authentication issue that appears to be occurring at the Blog2Social API layer, and I would appreciate your help determining whether there is an authorization or configuration issue with our API application.
Our Blog2Social API account is Active, currently has available post credits, and the application under My Apps displays an existing service token. We have confirmed that the service token configured in our n8n environment exactly matches the service token currently displayed in the Blog2Social API Console.
We are nevertheless receiving HTTP 403 Forbidden responses when making service-token authentication requests to the Blog2Social API.
We tested the following two endpoints independently:
1. List OAuth users
POST https://api.blog2social.com/rest/v1.0/user/list
The request contains the service token as specified in the API documentation.
2. User authentication
POST https://api.blog2social.com/rest/v1.0/user/auth
Again, the request contains the service token associated with our application.
Both requests return the same response:
{
"error": 1,
"b2s_error_code": "DEFAULT",
"error_code": 403,
"error_message": "forbidden"
}
We have also confirmed the following:
I also want to distinguish this issue from the WordPress 403/Hotlink Protection issue described in the Blog2Social FAQ.
This is not a 403 response from our WordPress site. The 403 is being returned directly by api.blog2social.com in response to the API authentication requests above. Neither test requires Blog2Social to retrieve an image, page, or other resource from our WordPress site.
Is there a way to check our API account/application and confirm:
I have intentionally not included our service token in this email. If you need the token or application identifier to investigate the account, please let me know the appropriate secure method for providing it.
Our objective is to use the Blog2Social API to submit approved LinkedIn content from n8n to the LinkedIn profiles and Company Page already associated with our Blog2Social environment. We have completed the upstream automation and have isolated the current failure specifically to API authentication.
Thank you for helping me to figure this out. So close. If you need the complete request configuration, timestamps, or n8n response details, I can provide those as well.
Our Blog2Social API account is Active, currently has available post credits, and the application under My Apps displays an existing service token. We have confirmed that the service token configured in our n8n environment exactly matches the service token currently displayed in the Blog2Social API Console.
We are nevertheless receiving HTTP 403 Forbidden responses when making service-token authentication requests to the Blog2Social API.
We tested the following two endpoints independently:
1. List OAuth users
POST https://api.blog2social.com/rest/v1.0/user/list
The request contains the service token as specified in the API documentation.
2. User authentication
POST https://api.blog2social.com/rest/v1.0/user/auth
Again, the request contains the service token associated with our application.
Both requests return the same response:
{
"error": 1,
"b2s_error_code": "DEFAULT",
"error_code": 403,
"error_message": "forbidden"
}
We have also confirmed the following:
- The API account is shown as Active in the Blog2Social API Console.
- The account currently has 74 post credits available.
- The service token configured in n8n matches the token displayed under My Apps.
- The requests are reaching api.blog2social.com successfully; Blog2Social is returning the 403 response.
- We are using a self-hosted n8n instance, currently version 2.39.8.
- The problem occurs even on the service-token-only requests, before LinkedIn account authorization or social publishing is involved.
I also want to distinguish this issue from the WordPress 403/Hotlink Protection issue described in the Blog2Social FAQ.
This is not a 403 response from our WordPress site. The 403 is being returned directly by api.blog2social.com in response to the API authentication requests above. Neither test requires Blog2Social to retrieve an image, page, or other resource from our WordPress site.
Is there a way to check our API account/application and confirm:
- Whether our application and service token are currently authorized for REST API access.
- Whether there is an additional activation, approval, permission, or account configuration required for the service token.
- Whether there are IP, origin, application, endpoint, or other restrictions that could cause api.blog2social.com to return this 403.
- Whether the existing service token needs to be regenerated or reauthorized.
- Whether there is anything different required in the authentication request from what is currently shown in your API documentation.
I have intentionally not included our service token in this email. If you need the token or application identifier to investigate the account, please let me know the appropriate secure method for providing it.
Our objective is to use the Blog2Social API to submit approved LinkedIn content from n8n to the LinkedIn profiles and Company Page already associated with our Blog2Social environment. We have completed the upstream automation and have isolated the current failure specifically to API authentication.
Thank you for helping me to figure this out. So close. If you need the complete request configuration, timestamps, or n8n response details, I can provide those as well.
Comment