Integrations · Adata
Adata integration: counterparty checks on the deal card
Client:
sattar.kz
Category: Integrations
Stack: Bitrix24 D7, Adata API, PHP, request cache
Timeline: 1–2 weeks
sattar.kz
Category: Integrations
Stack: Bitrix24 D7, Adata API, PHP, request cache
Timeline: 1–2 weeks
Problem
At sattar.kz, before handling a case or releasing money, a counterparty was checked by hand: open a third-party site, search by tax/business ID, copy the status back into the CRM.
Constraints
The external service rate-limited requests, and counterparty data had to be stored with a check date rather than re-queried every time.
What I did
- Counterparty check by tax/business ID right from the deal card, no trip to a third-party site
- Risk markers and check status saved in the CRM with the query date
- Request caching to avoid duplicate calls to the service
- Handling external API errors and timeouts without breaking the deal card
Screenshots
Screenshot coming soon
Counterparty-check button on the deal card
Screenshot coming soon
Risk markers and check status after the request
Architecture
Deal card
→ Adata API client
→ Result cache
→ Risk markers in the CRM
Result
Checking a counterparty took seconds right inside the deal instead of a trip to a third-party site and manual copy-pasting.
What can be reused
Adata API client with caching
Counterparty-check pattern on the deal card
Storing risk markers with a freshness date