Splivo for developers
An overview of the integration surface and how Pro-tier developers can request API early access. Honest about pre-v1.0 status.
1. Premise
Splivo is in current beta. The integration story today is simpler than a fully-fledged API surface — we have deep-link routing into payment rails, deterministic pay-link tokens, and a public web pay-link page. Authenticated programmatic access (proper REST/GraphQL endpoints) is on the roadmap but not yet GA. We don’t want to advertise programmatic access we haven’t shipped.
This page exists for developers who want to understand what is wired today and how to get on the list when API access becomes available.
2. Integrations available today
Splivo routes into payment rails, chat surfaces, and wallet apps via deep-links. The full per-vendor data-handling list lives at integrations. At a glance:
- Payment rails: Venmo, PayPal, Cash App, Zelle, Apple Pay, Google Pay, plus Stripe (subscription billing on web). Splivo generates the deeplink; the recipient pays in the app they already trust.
- Chat surfaces: iMessage, SMS, WhatsApp via system share-sheet deep-links. Splivo doesn’t post on your behalf; you tap, system share-sheet opens, you pick the channel.
- Wallets: Phantom, MetaMask via wallet-connect deep-links for the optional crypto-rail path.
- Sub-processors: Supabase (database + realtime), Cloudflare Pages (web hosting), Resend (transactional email; env-gated), RevenueCat (iOS/Android in-app purchase routing), Sentry (error tracking; opt-in).
Honest note: “Integrations” here means deep-link routing only — not authenticated API access. We don’t hold OAuth tokens for these vendors; we don’t move funds; we don’t programmatically read account state. The list above is what we hand off to, not what we control.
3. API early access path
Pro-tier customers can request API early access at [email protected]. The current state of API readiness:
- Read-only API (status): planned for v0.5.0+; signed-payload pattern under consideration.
- Webhook surface (status): planned for v0.5.0+; HMAC signing under consideration; cross-link security for current sub-processor list.
- Write API (create expense / send invoice / generate pay-link): post-v1.0 evaluation; no committed timeline.
If you have a use case (personal automation, integration with bookkeeping software, internal tooling), reply to [email protected] with what you’re trying to build. We’ll respond within 48h on weekdays. We don’t make promises we haven’t shipped, but the input shapes the priority order.
4. Open-source posture
Splivo is built in public. The verifiable narrative of what shipped when lives at changelog. The brand-and-public-honesty surface lives at about. The pre-v1.0 launch readiness gates (Apple Developer Program signup, production credentials drop, release keystore generation, real OCR shipped, trademark TESS clean, entity decision finalized) are tracked openly.
The product code itself is not currently open-source. We may revisit that decision post-v1.0 once the entity decision (sole-prop vs LLC) is finalized and the trademark is verified.
5. Webhook + dispatch surface (future)
Webhook infrastructure is planned for v0.5.0+. The intended pattern: signed payloads (HMAC-SHA256 over raw body), retry-on-failure with exponential backoff, and a developer-managed allow-list for destination URLs. Cross-link security for the current sub-processor list and data-handling posture; the webhook surface will inherit those constraints.
This is not yet wired. The current dispatch path is the public web pay-link card at getsplivo.com/p/<token>; recipients without the Splivo app see a clean web view with payment options.
6. Want API early access?
Reply to [email protected] with your use case. We’ll respond within 48h on weekdays. No timers. No scarcity framing. No dark-pattern nudges. If your use case fits what we’re building, we’ll add you to the early-access list and notify you when the API surface is ready for evaluation.
For the full list of services Splivo connects to and what each one sees, see integrations. For the verifiable narrative of what shipped when, see changelog.