CRS Credit Monitoring API (v3)
Welcome to the CRS Credit Monitoring API — the platform for embedding credit monitoring, identity verification, score improvement, and pre-screening into your product. CRS handles the parts you don't want to build: credit-bureau enrollment, secure consumer-data storage, regulatory compliance, identity verification, and the day-to-day operational machinery of running a credit product.
You focus on the product surface your users see; we power the credit infrastructure underneath. Whether you ship our pre-built widget, build a fully custom UI on our API, or mix the two, the same set of products, flows, and lifecycle events is available to you.
How to integrate. Five steps from sign-up to live traffic:
- Find the implementation type you need. Browse the Products section to see what we offer (Credit Scores, Reports, Alerts, Identity Verification, Score Up, Optimal Path, Offers IQ, Push Notifications). Pick the products that match your product roadmap.
- Request credentials. Contact your account manager to provision a customer + host and issue API credentials. You'll receive an API key and API secret for the development environment.
- Integration. Build against the development environment. Most integrations land somewhere on the spectrum from "drop the Widget into a page" (zero backend) to "use the Direct API + your own UI" (full control). Test scenarios are in Test Cases; error codes in Errors.
- Get Approved. Once your integration is working in development, request production credentials. We review the integration for compliance, security, and feature configuration before issuing prod keys.
- Go live. Switch to production credentials, point your hosts at the production base URL, and start serving real users.
Test credentials. While you're waiting on your own credentials in step 2, pre-provisioned hosts on the DEV environment let you start exploring the API right away. The two credit hosts have all features enabled — one configured for Equifax 1-bureau coverage, the other for the Equifax 3-bureau product — so you can compare response shapes and behavior between the two.
Redocly Documentation — EFX 1B With All Features
- Host ID:
89070aac-9542-44c4-bd58-0abe444edfea - API Key:
dd12e2b3-7504-461b-be48-fe6ef5ae7c1b - Secret:
4fc8400b-4024-4ef6-8e80-f7797583a5c2
Redocly Documentation — EFX 3B With All Features
- Host ID:
fdf44557-815d-462d-b3fa-23561e4d4be8 - API Key:
68f7e668-78ab-4d17-97e6-4139f6c0069a - Secret:
d6b53763-0798-40dd-b6ec-abfa56a0236f
Redocly Documentation — Offers IQ
- API Key:
f66fccbd-4cf7-4915-9850-09f00fccc7d0 - Secret:
a9f0241f-f3e8-4c71-a842-90521da87afb - Rule Set ID:
PROD_0E28CFE2
Use the API Key and Secret with POST /direct/login to obtain a host token, then pass the Rule Set ID in the POST /direct/credit-pre-screening request body to exercise the Offers IQ flow against the pre-configured test rule set.
Redocly Documentation — Prefill Products
- Host ID:
ca0266eb-7fcb-44eb-81b6-103793880b74 - API Key:
7c7d4228-c9dc-491b-93b3-09541b8dc8f9 - Secret:
a07686de-9f1b-4c95-8b19-6b21ae6a34d2
Use the API Key and Secret with POST /direct/login to obtain a host token, then call the Prefill Products endpoints (e.g. POST /direct/address-prefill).
Redocly Documentation — All 3 Bureaus
- Host ID:
f0e7f995-e080-4d0a-9d60-d270e2739435 - API Key:
4fc5bb84-a389-49ff-888c-e953f5271c36 - Secret:
bdc8a319-0984-45a5-b1bf-2d094d843453
A host enrolled with Equifax, TransUnion and Experian together. Credit data comes back merged, one key per bureau — read it from GET /users/latest-report / GET /users/latest-scores (user token) or GET /direct/latest-report/{id} / GET /direct/latest-scores/{id} (host token), not the efx-* endpoints.
These credentials are for DEV-environment exploration only — do not use them in production code. Authenticate with POST /direct/login, then use the test SSNs and scenarios to exercise the full identity-verification and credit-data flows.
Support. Questions, integration issues, or anything not covered in these docs — email support@crscreditapi.com.
For deeper integration patterns, see Getting Started. API spec last updated 2026-10-16.