403 Access Denied while making manual call logs in Freshworks CRM

We are receiving a 403 Access Denied error while trying to create manual call logs using our Freshworks CRM credentials. Even after attempting with account admin credentials, the issue still persists.

Here is the API path and request body:

Path: crm/sales/api/phone_calls

Body:
{
“phone_call”: {
“call_direction”: true,
“targetable_type”: “contact”,
“targetable”: {
“id”: “402107382049”,
“first_name”: “jegdish”,
“last_name”: “raja”,
“mobile_number”: “13056974350”
},
“note”: {
“description”: “Sample note”
}
}
}

Hi @jagadeesh,

Greetings!

It looks like you may not have the correct access. Is the API key you’re using the admin API key?

Could you also confirm if you’re facing this issue within the SDK? Have you tried making this call in Postman? If so, kindly share the cURL URL.

Thanks,
Anish

Yes, we are using an admin access key.

We have attempted the POST calls using both the SDK and Postman but are still encountering a 403 error.

curl --location 'https://arbaanchat.myfreshworks.com/crm/sales/api/phone_calls' \
--header 'Authorization: Token token=iKC2_EWMqp0uVRijqKWAlg' \
--header 'Content-Type: application/json' \
--data '{
    "phone_call": {
        "call_direction": true,
        "targetable_type": "contact",
        "targetable": {
            "id": "402107382049",
            "first_name": "jegdish",
            "last_name": "raja",
            "mobile_number": "13056974350"
        },
        "note": {
            "description": "Sample note"
        }
    }
}'

Thanks

Hi @jagadeesh ,

Please ensure that your credentials are not exposed. Also, have you tried removing the targetable attribute during your check?

We need to post the targetable attribute to create call logs. However, we also attempted the POST call without the targetable attribute, and it still resulted in a 403 Access Denied error.

I’m following up on the 403 Access Denied error when creating call logs. I’m still facing the issue, even when I try without the targetable attribute. However, I need to attach the targetable attribute to make the POST calls.