Axix OWL
Integrate with Developer integrations
Engineering teams wiring lead intelligence into CRMs, enrichment workers, or Market-Xora-style clients. Use JWT for account and key management, X-API-Key for data, and handle 401, 402, 403, 422, and 429 with Retry-After like any disciplined REST consumer.
Integrations fail when auth and errors are folklore
Developer integrations standardize on JWT for keys, X-API-Key for data, and the 401–429 set including Retry-After — so Market-Xora-style clients and custom workers behave the same.
Products in this path
REST API
Public base URL at api.axixowl.com — data via X-API-Key, account via JWT.
API keys
Create, list, and revoke keys — keep data calls off human sessions.
Usage history
See which calls spent credits — Search, emails, and company lookups.
Dashboard
Account home for credits, keys, usage, and plan status.
Recommended motion
Account
Sign up; obtain JWT for key management.
Key
Create and store an X-API-Key for the client.
Call
Hit Search and related data endpoints.
Harden
Handle 402 and 429 with backoff.
In practice
A REST contract engineering can finish
Base URL, auth split, credit costs, and error semantics — the four pages every integration PR should link.
Developer integrations checklist
- Base URL pinned to api.axixowl.com
- Secrets store for API keys
- Structured handling for 401/402/403/422/429
- Usage history hooks for ops dashboards
- Revoke runbook for leaked keys
Capacity context
“Once Retry-After was documented next to 429, our worker stopped thrashing the Free rate limit.”
Axix OWL
See Developer integrations beside a live credit balance
Open Developer integrations next to remaining credits so every returned lead, email, or successful company lookup is visible before it lands in CRM or outreach.
