I use Manychat for several customers. And to update fields in manychat, I send a request to ActivCampaign. Since this morning, I’ve had the same error on my 6 customer accounts. I’ve tried regenerating the API key on Activcampaign and updating it, but it doesn’t change anything. If anyone has any ideas, I’d love to hear them!
I’m having the same issue with 403 forbidden errors since this morning on the V1 API so not just your account.
Same issue — the fix is to move the api_key from the body of the request into the header of the request as API-KEY API-TOKEN.
We are experiencing this same issue since 3:17 PM EST yesterday (Aug 15, 2023). I’ve tried calling a v1 endpoint via curl and I get errors with the API-KEY in the body (403 Forbidden) and the header (400 Bad Request).
Sorry!! That should have said “API-TOKEN” in the header.
@allcampus-fatpanda try:
curl -v -X GET
“https://YOUR-DOMAIN.api-us1.com/admin/api.php?api_action=message_list&ids=all”
-H “API-TOKEN: YOUR-API-TOKEN”
-H “Accept: application/json”
No problem, lbpost! We’re doing the same thing. I realized my 400 Bad Request response was because of my own mistake with a curl command, but once we proved that we could hit the API this way, my team was able to add the header in our code and we’re testing the fix in a non-prod environment right now.
headers = {
"Content-type": "application/x-www-form-urlencoded",
"Api-Token": f"{key}",
}
1 Like
Cool, glad to hear it!
Hi this is Pat from the product team here at ActiveCampaign. Just here to confirm that both v1 and v3 endpoints should be referencing api token within the header of requests (following the example here).
Thanks for the confirmation, Pat. Please note that all of us were using v1 without the API token in the header before some unconfirmed change occurred on Wed, 8/16. While adding the token to the header fixed the issue, my team lost a full day and half to this issue. Something changed and nothing was communicated to us, and we only got through it thanks to help from this community (and in Slack).