# Commversion API Bad Request

**URL:** <https://community.hubspot.com/t/commversion-api-bad-request/125202>\
**Category:** APIs & Integrations\
**Tags:** professional\
**Created:** [January 31, 2025, 12:05pm UTC](https://community.hubspot.com/t/commversion-api-bad-request/125202 "2025-01-31T12:05:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Will-Hopkins](https://avatars.discourse-cdn.com/v4/letter/w/96bed5/32.png) [@Will-Hopkins](https://community.hubspot.com/u/Will-Hopkins)\
**Post date:** [January 31, 2025, 12:05pm UTC](https://community.hubspot.com/t/commversion-api-bad-request/125202/1 "2025-01-31T12:05:39Z")

</div>

Hi, We have livechat using Commversion on our website and this is integrated into our Hubspot using an API.

It has been working fine until December when now the below happens.

It creates the contact fine, but when it tries to add the live chat transcript into the notes it fails with the error below

{“status”:“error”,“message”:“one or more associations are not valid”,“correlationId”:“f6ae2d2e-5bfb-4689-8c4a-0fef027a7104”,“errors”:[{“context”:{“validationResult”:[“USER\_DOES\_NOT\_HAVE\_PERMISSIONS”]}}],“category”:“BAD\_REQUEST”}

We can’t seem to identify why this is not working, we have looked into permissions.

Each contact and note is assigned to a contact owner in hubspot who will then follow up on the contact. We have reached out to hubspot but they have not been able to help.

Any ideas appreciated!

---

<div class="post-metadata">

**Author:** ![Jaycee\_Lewis](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jaycee_lewis/32/61352_2.png) [@Jaycee\_Lewis](https://community.hubspot.com/u/Jaycee_Lewis)\
**Post date:** [January 31, 2025, 10:16pm UTC](https://community.hubspot.com/t/commversion-api-bad-request/125202/2 "2025-01-31T22:16:45Z")

</div>

Hi there, @Will-Hopkins ! It’s challenging to know exactly what changed, but I do have a suggestion to try to isolate the issue. Occasionally, this occurs if the Private App was created by a user who is no longer active in your portal. If you are using OAuth and not a Private App, please let us know.

Steps:

- create a fresh Private App in HubSpot with these required scopes:  
— `crm.objects.contacts.write`  
— `crm.objects.contacts.read`
- Update your app to use the new Private App credentials and test if the error persists
- You could set this up using a [**Developer Test Account**](https://developers.hubspot.com/docs/getting-started/account-types#developer-test-accounts) if you would rather not affect your production portal

Could you share a sample of your API request (with sensitive data removed)? This would help us verify the request structure.

Talk soon! — Jaycee

---

<div class="post-metadata">

**Author:** ![Jaycee\_Lewis](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jaycee_lewis/32/61352_2.png) [@Jaycee\_Lewis](https://community.hubspot.com/u/Jaycee_Lewis)\
**Post date:** [February 4, 2025, 9:52pm UTC](https://community.hubspot.com/t/commversion-api-bad-request/125202/3 "2025-02-04T21:52:46Z")

</div>

Hey, @Will-Hopkins Thanks for catching that. I edited my post to remove the incorrect scope detail. — Jaycee

---

<div class="post-metadata">

**Author:** ![Will-Hopkins](https://avatars.discourse-cdn.com/v4/letter/w/96bed5/32.png) [@Will-Hopkins](https://community.hubspot.com/u/Will-Hopkins)\
**Post date:** [February 3, 2025, 8:54am UTC](https://community.hubspot.com/t/commversion-api-bad-request/125202/4 "2025-02-03T08:54:45Z")

</div>

Hi Jaycee,

Thank you for your reply.

I will do this - although there is no options to add crm.objects.notes.write under scopes - it does not appear as an option.

Thanks

Will

---

<div class="post-metadata">

**Author:** ![Will-Hopkins](https://avatars.discourse-cdn.com/v4/letter/w/96bed5/32.png) [@Will-Hopkins](https://community.hubspot.com/u/Will-Hopkins)\
**Post date:** [February 6, 2025, 9:42am UTC](https://community.hubspot.com/t/commversion-api-bad-request/125202/5 "2025-02-06T09:42:05Z")

</div>

Hi Jaycee,

Thank you so much, our integration is now working under the new private app, so it seems something went wrong in the permissions of the old one.

Thanks again

Will