RunningSales Partner API

Connect your platform to RunningSales and turn your merchants' lost checkouts, failed payments and cold leads into phone-closed sales.

What RunningSales does

RunningSales is a sales-recovery platform: trained human agents call a merchant's leads — abandoned order forms, failed or missed payments, subscription rebills that didn't go through, and past buyers — and close the sale over the phone. Behind the agents sits a full CRM: real-time event ingestion, prioritized dial queues, a power-dialer, and a results dashboard the merchant sees.

For a platform partner, the integration is deliberately small: send us an event when something happens — a new lead, an abandoned checkout, a failed payment, a sale. Within seconds it becomes a callable lead in the right dial queue. That's the whole surface.

RunningSales consumes the native webhooks of more than twenty checkout, storefront, subscription, telehealth, funnel and CRM platforms in production today. Whatever your platform emits, we adapt to it; you do not change your payloads.

Integration models

Events API — you push →

Recommended. One HTTPS endpoint, plain JSON, one POST per event. Secret-URL auth, idempotent, retry-safe. Most partners are live the same day.

Feed API — we pull →

If exposing a read-only feed is easier than pushing, give us a URL and a bearer token — we poll it every few minutes.

Native integration →

For platforms with their own webhook system we consume your format as-is, and merchants enable RunningSales in one click via a connect flow or provisioning API.

The one hard requirement

Phone number. RunningSales campaigns exist to call. A lead without a dialable phone number cannot be worked and is skipped by design. Whatever else your payload contains, phone capture is the single biggest success factor of the integration.

How onboarding works

Say hello. Tell us what your platform is and roughly what your events look like — one sample payload is enough.
We issue credentials. You get your dedicated delivery URL (Events API) or we exchange feed credentials (Feed API). One connection per merchant, or one shared connection — your choice.
Fire test events. One of each event type. We confirm each landed end-to-end with a working phone number.
Go live. Every event becomes a callable lead within seconds.

There is no fee, no SDK and nothing to install — the integration is a webhook. Platforms that want to offer RunningSales to all of their merchants should read the native integration guide; for how deliveries are authenticated and what data we need, see Security & data.

Conventions used in these docs

{BASE_URL} — your dedicated ingest hostname, issued during onboarding.
{CONNECTION_ID} / {SECRET} — per-connection credentials we mint for you. The secret is part of the URL path; treat the full URL as a credential.
All endpoints are HTTPS-only. All timestamps are ISO 8601 UTC. Amounts are in major units (dollars, not cents) unless stated otherwise.

Contact

Partnership and technical questions: reach your RunningSales contact directly, or email integrations@runningsales.com.