DaData
DATA · DATA & ANALYTICS
Address, company, and bank lookups with suggestions and standardization.
Acts as the person, not as itself
Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.
Credentials never touch the agent
Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.
Every call on the record
Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
dadata_get_api_v2_profile_balanceREADRead the connected DaData account's prepaid balance in rubles -- the balance the standardization tools spend. via GET /api/v2/profile/balance
dadata_get_api_v2_stat_dailyREADRead the connected DaData account's API usage for the current day: suggestions, standardization and merging request counts against their daily limits. via GET /api/v2/stat/daily
dadata_get_api_v2_versionREADRead the versions of the reference datasets DaData is currently serving (FIAS, EGRUL, banks and the rest) and the service versions behind them. via GET /api/v2/version
dadata_post_api_4_1_rs_findaffiliated_partyREADFind Russian companies affiliated with the queried INN through shared founders or managers (scope selects which relation is followed). via POST /api/4_1/rs/findAffiliated/party
dadata_post_api_4_1_rs_findbyemail_companyREADFind Russian companies that list the queried email address in their public registry details. via POST /api/4_1/rs/findByEmail/company
dadata_post_api_4_1_rs_findbyid_addressREADLook up a Russian address by FIAS or KLADR identifier: returns the full structured address with codes and coordinates. via POST /api/4_1/rs/findById/address
dadata_post_api_4_1_rs_findbyid_bankREADLook up a Russian bank by exact BIC, SWIFT, INN or registration number: returns the bank's registry record with payment details. via POST /api/4_1/rs/findById/bank
dadata_post_api_4_1_rs_findbyid_by_nameREADLook up a record of a named DaData reference directory by its identifier (path names the directory). Russian reference data. via POST /api/4_1/rs/findById/{name}
dadata_post_api_4_1_rs_findbyid_fiasREADLook up a Russian address in the FIAS registry by FIAS identifier: returns the full structured address record. via POST /api/4_1/rs/findById/fias
dadata_post_api_4_1_rs_findbyid_partyREADLook up a Russian company or sole proprietor by exact INN or OGRN: returns the registry record (name, status, addresses, management) for each matching branch. via POST /api/4_1/rs/findById/party
dadata_post_api_4_1_rs_geolocate_addressREADReverse geocoding: find the Russian addresses (down to individual buildings) nearest to a latitude/longitude point, ranked by distance. via POST /api/4_1/rs/geolocate/address
dadata_post_api_4_1_rs_geolocate_by_nameREADFind the entries of a named DaData directory nearest to a latitude/longitude point (path names the directory). Russian reference data. via POST /api/4_1/rs/geolocate/{name}
dadata_post_api_4_1_rs_iplocate_addressREADResolve an IPv4 address to the Russian city it belongs to, with the city's full structured address. Omitting the ip argument resolves the caller's own address, which through this integration is the gateway's, so pass ip explicitly. via POST /api/4_1/rs/iplocate/address
dadata_post_api_4_1_rs_suggest_addressREADAutocomplete Russian addresses from a free-form query: returns up to 20 ranked suggestions with structured components and FIAS/KLADR codes. Coverage is Russia only; queries are typically in Russian. via POST /api/4_1/rs/suggest/address
dadata_post_api_4_1_rs_suggest_bankREADFind Russian banks and their branches by name, BIC, SWIFT, INN or registration number: returns ranked suggestions with payment details. via POST /api/4_1/rs/suggest/bank
dadata_post_api_4_1_rs_suggest_by_nameREADAutocomplete over a named DaData reference directory (path names the directory, e.g. country, currency, okved2, fms_unit): returns ranked suggestions for a free-form query. Russian-language reference data. via POST /api/4_1/rs/suggest/{name}
dadata_post_api_4_1_rs_suggest_emailREADAutocomplete an email address as it is typed: completes the local part and popular mail domains. via POST /api/4_1/rs/suggest/email
dadata_post_api_4_1_rs_suggest_fiasREADAutocomplete Russian addresses against the FIAS state address registry: returns ranked suggestions with FIAS codes. Coverage is Russia only. via POST /api/4_1/rs/suggest/fias
dadata_post_api_4_1_rs_suggest_fioREADAutocomplete Russian personal names (surname, given name, patronymic): returns ranked FIO suggestions with gender and name-part breakdown. via POST /api/4_1/rs/suggest/fio
dadata_post_api_4_1_rs_suggest_partyREADFind Russian companies and sole proprietors by name fragment, INN, OGRN or address: returns ranked suggestions with registry (EGRUL) details. Queries and results are Russian-centric. via POST /api/4_1/rs/suggest/party
dadata_post_api_v1_cleanWRITEStandardize records with several fields at once: `structure` names the column types and `data` carries the rows. Russian-centric data. PAID per record from the account's prepaid balance (~0.20 RUB each; 20 requests/second limit); on an unfunded account DaData answers with its payment-required error. via POST /api/v1/clean
dadata_post_api_v1_clean_by_typeWRITEStandardize an array of raw strings of one declared type (path names it: NAME, ADDRESS, PHONE, EMAIL, BIRTHDATE, PASSPORT, VEHICLE, AS_IS, SIMPLE_PARTY_NAME): DaData cleans, normalizes and enriches each value. Russian-centric data. PAID per record from the account's prepaid balance (~0.20 RUB each; 20 requests/second limit); on an unfunded account DaData answers with its payment-required error. via POST /api/v1/clean/{type}
Often connected alongside
Put DaData behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.