What happened
What this says
Current to 13 Oct 26Claims connector stopped syncing after customer upgraded system to token-based authentication. BB-Demo updated connector configuration; sync restored with fresh data flowing.
Problem: Connector stopped loading data following a claims system upgrade that changed authentication method from the previous approach to token-based API authentication. Handling: BB-Demo updated the connector configuration to use the new credentials and API documentation provided by the customer. Sync resumed successfully with fresh data loading through.
Details
Updated 9 Oct 26Prioritynormal
Statusclosed
Categoryconnector_sync
Channelemail
First response (min)441
Helpdeskmade from
Trail
- created · Cian Farrell 5 Feb 2026 15:24Our claims system connector has stopped loading data. We've recently upgraded our claims system and changed the authentication method, which I think is causing the issue. Can you help us get it reconnected?
- public_reply · Bethan Lister 5 Feb 2026 22:45Thanks for reporting this. Just so I've got this right, the connector's stopped working after you changed the auth setup on your end, is that correct? Can you tell me what the new authentication method is, and I'll update our side?
- public_reply · Cian Farrell 6 Feb 2026 14:59Yes, that's right. We've switched to token-based API authentication. I'll send the new credentials and our updated API documentation over.
- public_reply · Bethan Lister 9 Feb 2026 13:19Cheers for that. I've found the issue in the logs. Your claims system was upgraded on 9 February 2026 and changed its API authentication method. I've updated our connector to use the new credentials. Can you test it and let me know what happens?
- public_reply · Cian Farrell 11 Feb 2026 09:53Great, the sync is working again. Fresh data is coming through. Thanks for sorting it.
- status_change · 21 Feb 2026 23:59
Helpdeskmade from