canonical: https://jentic.com/apis/experian.com/experian # Experian Data Quality API Jentic publishes the only available OpenAPI specification for Experian Data Quality API, keeping it validated and agent-ready. Experian is a global information services company best known for credit data; this spec covers a focused subset of their data quality and consumer services: OAuth2 token issuance, address validation, address search, and consumer credit profile retrieval. The API is intended for regulated workflows such as KYC, credit decisioning, and address verification at point of capture. ## For AI agents Validate and search postal addresses, exchange OAuth2 credentials for an access token, and retrieve a consumer credit profile through the Experian data quality and consumer services APIs. ## Scope Does not handle business credit, fraud scoring, marketing audiences, or full Experian One platform features - use for OAuth2 token, address validation and search, and consumer credit profile retrieval only. ## Capabilities - Exchange client credentials for an Experian OAuth2 access token - Validate a postal address against Experian's reference data and return a standardised result - Search for candidate addresses by partial input for type-ahead address capture - Retrieve a consumer credit profile for a verified individual under permissible-purpose rules - Support both US and international address formats through the validate and search endpoints - Use a single base URL for token, address, and consumer service operations ## Use cases ### Address Verification at Point of Capture Use POST /address/validate/v1 to verify a postal address as a user submits a checkout or registration form, and GET /address/search/v1 to power type-ahead suggestions. Standardised output reduces failed deliveries and downstream data quality issues. Suitable for ecommerce, fintech onboarding, and any flow where address fidelity matters. Example prompt: Call POST /address/validate/v1 with the user's submitted address and country=US, then accept the standardised result if Confidence is Verified. ### Consumer Credit Decisioning POST /consumerservices/credit-profile/v2 returns a consumer credit profile for a verified applicant, used in lending and account-opening decisions. This must be invoked under a permissible purpose under FCRA in the US (or equivalent regulation elsewhere) and the requesting party must be onboarded by Experian. Example prompt: After exchanging credentials at POST /auth/oauth/v2/token, call POST /consumerservices/credit-profile/v2 with the consumer's verified PII and a permissible-purpose code. ### Token Lifecycle Management POST /auth/oauth/v2/token issues short-lived OAuth2 access tokens via the client_credentials grant. A scheduled refresh keeps long-running agents authenticated without requiring per-call token requests. The same token authorises both the address and consumer-services endpoints. Example prompt: Call POST /auth/oauth/v2/token with grant_type=client_credentials, store the returned access_token, and refresh it before its expiry. ### AI KYC Agent via Jentic An AI onboarding agent uses Jentic to call Experian's address validation and credit profile endpoints in sequence. Jentic resolves intents like "validate this address" and "pull credit profile" to the correct Experian operation and supplies OAuth2 tokens from the vault, keeping client_id and client_secret out of agent context. Example prompt: Through Jentic, search 'validate an address with experian', load POST /address/validate/v1, execute it for the applicant, then load and call POST /consumerservices/credit-profile/v2 if the address is verified. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /auth/oauth/v2/token | Exchange client credentials for an access token | | POST | /address/validate/v1 | Validate a postal address | | GET | /address/search/v1 | Search for candidate addresses | | POST | /consumerservices/credit-profile/v2 | Retrieve a consumer credit profile | ## Key resources - **OAuth Token** — Issue and refresh OAuth2 access tokens - **Address Validate** — Validate a postal address against reference data - **Address Search** — Type-ahead address candidate search - **Credit Profile** — Retrieve a consumer credit profile under permissible purpose ## Why Jentic - **Setup:** Wiring the Experian Data Quality API by hand means running its OAuth2 token flow against /auth/oauth/v2/token, refreshing tokens, and tracking the address and credit-profile endpoints yourself. Through Jentic you install once, import Experian from the API Directory, store the client credentials once, and your agent calls it. - **Permission scoping:** Experian carries its targets in the request body, so scope the agent to the operations it needs, such as address validation or address search. The consumer credit-profile operation stays out of the allowed set unless you add it. - **Credential handling:** Your Experian client id and secret are stored once, encrypted, by your own Jentic One instance, which mints OAuth2 tokens on demand and injects them at execution time. The long-lived secret never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'validate an address with experian' or 'pull a credit profile', and Jentic returns the matching Experian operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Smarty US Autocomplete API** — Smarty is a US-focused address validation and rooftop-geocoding alternative to Experian - **Melissa Data API** — Melissa offers global address verification, identity, and data quality services - **Plaid API** — Plaid covers bank-account verification alongside Experian's credit and address data ## FAQ ### Why is there no official OpenAPI spec for Experian Data Quality API? Experian does not publish a unified OpenAPI specification covering this combination of address and consumer services. Jentic generates and maintains this spec so that AI agents and developers can call Experian Data Quality API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Experian Data Quality API use? The API uses OAuth2 with the client_credentials grant. POST /auth/oauth/v2/token exchanges your client_id and client_secret for a short-lived access token, which is then sent as Authorization: Bearer on the address and credit endpoints. Through Jentic, client credentials sit in the vault and tokens are minted on demand. ### Can I use POST /consumerservices/credit-profile/v2 without onboarding? No. Consumer credit endpoints require Experian onboarding and a documented permissible purpose under FCRA in the US (or equivalent regulation in other regions). The address endpoints can typically be used by any client with credentials, but the credit profile endpoint is gated. ### How do I add type-ahead address search? Call GET /address/search/v1 with the partial input the user has typed and the target country code. The endpoint returns ranked candidate addresses, and once the user selects one you call POST /address/validate/v1 to lock the standardised result. ### How do I validate an address through Jentic? Run pip install jentic, then search 'validate an address with experian', load the POST /address/validate/v1 operation, and execute it with the address payload. Jentic obtains and refreshes the OAuth2 access token automatically using the client credentials in the vault. ### What are the rate limits for the Experian Data Quality API? Rate limits are not published in this spec. They are governed by the contract you sign with Experian and vary by product (address vs credit) and tier. Treat 429 responses with Retry-After as authoritative and back off accordingly. ### Can I limit what my agent is allowed to do with the Experian Data Quality API? Yes. Because you run Jentic One yourself, your own rules decide which Experian operations your agent may call, so you can allow only what a given workflow needs, such as POST /address/validate/v1 and GET /address/search/v1 for address capture. Since Experian carries its targets in the request body, the sensitive POST /consumerservices/credit-profile/v2 operation stays outside the allowed set unless you explicitly add it. The OAuth2 token exchange at POST /auth/oauth/v2/token runs with credentials your instance holds, and those credentials are injected only for the operations you have permitted.