API Key Authentication
All API requests require authentication using a Partner API Key. Credzu uses a simple, secure key-based authentication that’s consistent with systems like Shape, TotalExpert, and Velocify.Header Format
Include your API key in theAuthorization header:
Example Request
Getting Your API Key
Each referral partner receives:- Production API key - For live transactions
- Sandbox API key (optional) - For testing
Environments
| Environment | Base URL | Purpose |
|---|---|---|
| Production | https://credzu.com/wp-json/credzu/v1 | Live data, real credit scans, actual escrow transactions |
| Sandbox | https://sandbox.credzu.com/wp-json/credzu/v1 | Test data, simulated events, mock score updates |
Always use the sandbox environment for initial integration testing before going live.
Security Requirements
Transport Security
- HTTPS required - All API requests must use HTTPS
- TLS 1.2+ - Minimum TLS version supported
Data Protection
Partners must protect:- API keys
- Returned lead IDs
- Any score or milestone data received via webhooks
No full credit reports are exchanged via API. All sensitive credit data remains inside Credzu’s secure environment.
Authentication Errors
If the API key is invalid or missing, requests will fail with anAUTH_FAILED error:
- Missing
Authorizationheader - Incorrect key format (must use
Credzu-Keyprefix) - Expired or revoked API key
- Using production key on sandbox or vice versa