Every on demand app requires integrations across six core API categories: maps and geolocation (Google Maps Platform), payment processing (Stripe Connect), SMS and OTP (Twilio), push notifications (Firebase Cloud Messaging), identity verification (Jumio or Persona), and analytics (Firebase Analytics or Mixpanel). Beyond these essentials, in-app communication APIs and social login integrations are standard additions. Each API adds development time, ongoing monthly cost, and a dependency that must be managed — plan all integrations during the product scoping phase.
- Third-party APIs are not optional extras — they are the infrastructure layer that makes on demand platforms function. No serious platform builds maps, payments, or SMS from scratch.
- Every API adds development time, monthly running cost, and vendor dependency — all of these must be scoped and budgeted before development begins.
- Google Maps Platform is the most critical and most cost-variable API in an on demand stack — usage costs scale with volume and can become significant as the platform grows.
- Firebase Cloud Messaging provides a free push notification infrastructure that scales to any volume — there is no reason to build or buy an alternative for most on demand platforms.
- Identity verification APIs are mandatory before first payout to any provider — skipping them exposes the platform to fraud and regulatory compliance failure.
- Category 1: Maps and Geolocation
- Category 2: Payment Processing
- Category 3: SMS and OTP
- Category 4: Push Notifications
- Category 5: In-App Communication
- Category 6: Identity Verification
- Category 7: Analytics
- Category 8: Social Login
- API Integration Planning: What to Do Before Development
- Frequently Asked Questions
Category 1: Maps and Geolocation
Primary provider: Google Maps Platform
Maps and geolocation are the most visible and most cost-variable APIs in an on demand platform. The Google Maps Platform covers every geolocation requirement through a suite of APIs:
- Maps SDK for Android/iOS: Renders the interactive map in the customer and provider apps.
- Places API: Enables address search and autocomplete for customer location entry.
- Directions API: Calculates routing from the provider’s current location to the customer address.
- Distance Matrix API: Calculates travel time and distance between multiple origins and destinations — used for ETA calculation and provider matching.
- Geocoding API: Converts addresses to coordinates and coordinates to addresses.
2026 pricing overview: Google provides a monthly $200 credit. Platforms with moderate volume (1,000–5,000 daily active bookings) typically spend $300–$2,000 per month on Maps APIs.
Alternative: Mapbox is a lower-cost alternative with good map quality and routing capabilities. For consumer-facing on demand platforms, Google Maps data quality and routing accuracy remain stronger in most markets.
Category 2: Payment Processing
Primary provider: Stripe Connect
Stripe Connect handles the full payment lifecycle for on demand platforms — customer payment collection, platform commission deduction, provider fund transfer, automated payouts, and compliance. Standard processing fee: 2.9% + $0.30 per successful card charge (US standard rate). Payout fee: 0.25% per payout, capped at $25.
Regional alternatives: Razorpay (India), Paystack (Africa), Braintree (global PayPal integration) for markets with limited Stripe availability.
Category 3: SMS and OTP
Primary provider: Twilio
SMS is used in on demand platforms for OTP (One-Time Password) verification during user registration and login, booking confirmation messages, and provider arrival alerts where push notifications may not be reliable. Twilio is the standard choice due to its global carrier coverage, reliable delivery rates, and developer-friendly API.
Pricing: Approximately $0.0075–$0.05 per SMS message depending on destination country. Phone numbers cost $1–$3/month.
Alternative: AWS SNS (Simple Notification Service) is a lower-cost alternative for high-volume SMS. MSG91 and Vonage are alternatives with strong regional coverage.
Use case prioritisation: OTP verification is the critical use case. Most platforms rely on push notifications for transactional messages and use SMS as a fallback for users who have disabled notifications.
Category 4: Push Notifications
Primary provider: Firebase Cloud Messaging (FCM)
Push notifications are the primary communication channel between the platform and users for booking status updates, provider assignment, arrival alerts, and promotional messages. Firebase Cloud Messaging delivers push notifications to both Android and iOS apps, and its free tier covers unlimited notifications — there is no cost-per-notification for FCM.
Alternative for advanced segmentation: OneSignal provides a higher-level push notification management layer with segmentation, A/B testing, and analytics on top of FCM/APNs. It has a generous free tier and is useful for marketing push campaigns in addition to transactional notifications.
Category 5: In-App Communication
Primary providers: Twilio (voice/SMS), SendBird or Stream (in-app chat)
In-app communication between customers and providers during active bookings enables customers to give specific instructions, providers to notify customers of their arrival, and both parties to resolve minor issues without calling the platform’s support team.
- In-app chat: SendBird and Stream are the leading providers for real-time in-app messaging. Both offer SDKs for Flutter and React Native and handle message persistence, read receipts, and push notification triggers for new messages.
- Masked calling: Twilio Proxy provides number masking — customers and providers can call each other through the app without either party seeing the other’s real phone number. This protects privacy and prevents off-platform relationship building.
Cost: SendBird starts at $399/month for production use. Twilio Proxy charges per masked call minute. For MVP builds, implement chat first and add masked calling in version 2.0 if demand justifies it.
Category 6: Identity Verification
Primary providers: Jumio, Persona, Onfido
Provider identity verification is a compliance and safety requirement for any on demand platform that dispatches service providers to customer locations or pays out earnings. Before a provider can go active on the platform or receive their first payout, their identity must be verified against a government-issued document.
- Jumio: Automated ID verification and liveness detection. Enterprise-grade compliance coverage. Pricing is typically per-verification ($1–$5 per check depending on volume and tier).
- Persona: Developer-friendly identity verification with flexible workflow configuration. Pricing is per-verification.
- Onfido: Strong European compliance coverage; good for GDPR-regulated markets.
Do not skip identity verification to save on integration time. A platform that dispatches unverified providers to customer homes or pays out to unverified accounts faces fraud risk, safety liability, and potential regulatory consequences that far exceed the verification API cost.
Category 7: Analytics
Primary providers: Firebase Analytics (free), Mixpanel (freemium), Amplitude (freemium)
Analytics APIs provide the data needed to understand user behaviour, track platform performance, and make informed product decisions. For on demand platforms, critical metrics include booking completion rate, provider acceptance rate, session duration, funnel drop-off, and user retention by cohort.
- Firebase Analytics: Free and deeply integrated with the Firebase ecosystem. Suitable for most on demand platforms at early and mid scale.
- Mixpanel: Better event-tracking granularity and funnel analysis than Firebase for product analytics. Freemium pricing covers most early-stage platforms.
- Amplitude: Similar to Mixpanel; strong for cohort analysis and retention tracking.
Category 8: Social Login
Primary providers: Google Sign-In, Apple Sign-In, Facebook Login
Social login reduces registration friction by allowing users to create accounts using their existing Google, Apple, or Facebook credentials. This is particularly effective for on demand apps where customers want to book quickly without completing a lengthy registration form.
- Google Sign-In: Most widely used; mandatory to include on Android. Free to implement.
- Apple Sign-In: Required by Apple for iOS apps that include other social login options. Free to implement.
- Facebook Login: Optional; includes additional implementation complexity around Meta’s developer policies.
API Integration Planning: What to Do Before Development
| API Category | Decision to Make Before Development | Budget Consideration |
|---|---|---|
| Maps and geolocation | Google Maps vs Mapbox; which specific API services are needed | $200–$2,000+/month at moderate volume — factor into unit economics |
| Payment processing | Stripe Connect vs regional gateway; payout schedule; wallet architecture | 2.9% + $0.30 per transaction; plus 0.25% payout fee |
| SMS / OTP | Twilio vs AWS SNS vs regional provider | $0.007–$0.05 per SMS depending on country |
| Push notifications | FCM (free) vs OneSignal for advanced segmentation | FCM is free; OneSignal paid tiers from $9/month |
| In-app chat | SendBird vs Stream; MVP (chat only) vs V2 (masked calling) | $399+/month for production; defer to v2.0 if budget constrained |
| Identity verification | Jumio vs Persona vs Onfido; verification workflow design | $1–$5 per verification — volume discount at scale |
| Analytics | Firebase vs Mixpanel vs Amplitude; events to track from day one | Free tiers available; paid from $25–$400+/month depending on volume |
Frequently Asked Questions
Maps (Google Maps Platform), payment processing (Stripe Connect), SMS/OTP (Twilio), push notifications (Firebase Cloud Messaging), and identity verification for providers are the five essential API categories for a functional on demand MVP.
A typical single-service on demand platform at early scale (500–1,000 bookings per day) spends approximately $500–$3,000 per month on APIs — primarily Google Maps ($300–$1,500), Stripe fees (~2.9% of GMV), Twilio ($50–$200), and identity verification ($50–$500 depending on onboarding volume).
Mapbox is a credible alternative at lower cost. OpenStreetMap provides free map tiles but requires additional engineering for routing and search quality. For consumer-facing platforms where map accuracy directly affects user experience, Google Maps remains the recommended choice.
Yes — Firebase Cloud Messaging has no per-notification charge. It is free to send unlimited notifications to Android and iOS devices. There are usage limits within Firebase’s free tier for other Firebase services, but FCM itself has no cost ceiling.
No. Identity verification for providers who receive payouts is a compliance requirement in most markets and a safety necessity for customer-facing service apps. It must be in place before the first provider goes live.
