Have the Dibcase team check the key, its connection and the affected client mapping. Do not paste API keys into support messages.
Use the Dibcase integration
Use the partner-managed Dibcase connection for Chronicle client data and events in Dibcase. Complete Connect Dibcase to Chronicle first.
What syncs
Available capabilities and enabled settings are different. Review the options your firm wants to use.
Capability | Direction | What it does |
|---|---|---|
Client data | Chronicle to Dibcase | Dibcase pulls Chronicle client data using the configured partner connection. |
Events | Chronicle to Dibcase | Dibcase pulls Chronicle event data through the partner connection. |
Client data
The Dibcase team maintains the destination mapping and sync schedule.
Open a client that the Dibcase team confirmed is linked correctly.
Compare the client data in Dibcase with the corresponding Chronicle client.
Ask the Dibcase team to adjust the destination mapping if your firm needs different fields.
Events
Event syncing is managed by Dibcase through the Chronicle API.
Check a known Chronicle event on the corresponding Dibcase client.
If it is missing or out of date, ask the Dibcase team to check the connection, mapping and latest pull.
Check status, retry or correct a link
Use Dibcase's support workflow for partner sync status, retries and client-link corrections. The shared Chronicle Resync and Change link controls do not manage this API-key connection.
Identify the affected client and event or field in your own systems.
Confirm the source information exists in Chronicle.
Ask the Dibcase team to check its client mapping and retry the affected data.
Manage the API key
Keep the key limited to the authorized Dibcase team. A lost or compromised key should be revoked in Settings > API and replaced with the partner team; revocation stops calls using that key.
Use the API explains key creation and revocation.
Usage troubleshooting
Client data or events stopped updating
The wrong client is linked
Ask the Dibcase team to correct its mapping before retrying. A Chronicle native-integration re-match does not change the partner's link.