Connect our real-time ping-post call auction API to Ringba, Boberdoo, or your own dialer — sub-500ms latency, locked pricing, no obligation to post.
Connect with a single-shot real-time bidding endpoint built for Ringba. Map your call tags, configure auth headers, and go live in minutes.
Use an HTTP Buyer with a two-step ping/post flow — get a locked price quote first, then commit only if it clears your threshold.
Asterisk, FreePBX, Twilio, or your own system — implement the ping-post flow as a pre-dial hook using our documented REST endpoints.
The ping-post flow runs a real-time auction before any call is delivered, so you always know the price before you commit.
Send anonymized lead data to /api/cx/ping — zip, vertical, and any IVR answers you’ve already collected.
Receive a guaranteed price and a pingToken, valid for up to 300 seconds — no obligation to continue.
Send caller details to /api/cx/post to commit — you’ll get a dialNumber and bridge the caller instantly.
The ping-post API runs a real-time auction across eligible buyers before any call is delivered — here’s what’s built in.
The /ping endpoint responds in under 500ms at p95, fast enough for live IVR integration.
The price returned by /ping is guaranteed if you post before it expires.
The /post endpoint is safe to retry — it will never double-commit a call.
Caller ID is preserved end-to-end, required for call bridge resolution.
/ping allows 10 requests/second per publisher with a burst of 30, with clear 429 responses for backoff.
A staging environment is available for testing your integration before going live.
Have any questions? Don’t hesitate to contact us!
You first send anonymized lead data to /api/cx/ping and receive a locked price quote. If it works for you, you send caller details to /api/cx/post to commit and receive dial instructions — you're never obligated to post.
Every request needs two headers: X-Vendor-API-Key (starts with cx_) and X-Vendor-API-Secret, which should be treated like a password.
Yes, a single-shot endpoint (POST /api/cx/ringba/rtb) is built specifically for Ringba's real-time bidding, with call-tag token mapping.
/ping allows 10 requests/second per publisher with a burst of 30. If you exceed it, you'll get a 429 response and should retry with backoff. /post has no global cap since tokens only post once.
Yes — /post is idempotent, so retrying after a 5xx server error is safe and won't result in a duplicate commit.
A staging environment is available from your admin panel for testing, and our integrations team is reachable at integrations@proaxis.ai.
Tell us about your platform and volume, and we’ll get you access to the API and staging environment.
Takes about 2 minutes. We review every application personally.
