Getting Started
FAQ
Frequently asked questions about the LeadX API.
How do I authenticate my requests?
Include your API key in the X-API-KEY header with every request. Requests without a valid key are rejected with a 401 Unauthorized error. See Authentication for examples in cURL, Python, and Node.js.
Can I test the API without writing code?
Yes. Every endpoint page in this documentation includes an interactive playground. Enter your API key, experiment with parameters, and view live JSON responses directly in your browser.
What happens if I exceed the rate limit?
The API responds with a 429 Too Many Requests error, and further requests are temporarily blocked until the time window resets. Rate limits are tracked by client IP address. See Rate Limiting for details.
How are errors returned?
Most endpoints return errors in a standardized format with error.code, error.message, error.status, and an error.request_id you can reference when contacting support. See Troubleshooting and Error Codes for the full reference.
Can I look up records in bulk?
Yes. LeadX supports file-based email, mobile, and validation jobs, plus a JSON email-job workflow for application integrations. See Run a bulk enrichment workflow.
Does success mean a result was found or a credit was charged?
No. success: true means the request completed. Inspect the endpoint's result fields and credits_debited separately. See Results and billing.
Which requests can I retry safely?
Retry read requests and received transient responses with bounded backoff. Use an Idempotency-Key for JSON bulk email submission, and reconcile ambiguous file uploads before replaying them. See Reliability and retries.
How do I get support?
Email info@leadx.com or book a demo to talk with the team. Include the request_id from any error response to help us troubleshoot faster.