I suspect given the 404 error that the error is not specific to the manual association API call, but to connecting in general. Have you tried using other API endpoints to confirm that API token etc. is valid?
I hit the https://api.gong.io/v2/calls/manual-crm-associations endpoint in a test environment and got
{
"requestId": "cedvhq2p85dhophnfq",
"records": {
"totalRecords": 2,
"currentPageSize": 2,
"currentPageNumber": 0
},
"associations": s
{
"callId": "963656233271923412",
"userId": "5163858753368344694",
"created": "2021-10-20T14:18:20.45992-04:00",
"associatedCrmObjects": s
{
"accountCrmId": "0014W00002b38vPQAQ",
"dealCrmId": "0064W000017bR2zQAE"
}
]
},
{
"callId": "8662336506672475103",
"userId": "1342930387683404098",
"created": "2021-11-02T13:38:21.268773-04:00",
"associatedCrmObjects": s
{
"accountCrmId": "0014W00002b38vPQAQ",
"dealCrmId": null
}
]
}
]
}
Thanks for the reply! Yes, I can hit all other APIs successfully. Regarding the token issue, is this the only additional permission (beyond permissions to pull call transcripts):
api:crm-calls:manual-association:read
Is your integration with HubSpot? Did you manually associate the objects inside the Gong UI?