Third-Party Services
Housr integrates with a range of external services. This page maps which services are used by which repos and for what purpose.
Service Map
| Service | Used By | Purpose |
|---|---|---|
| Firebase | App, API v1, Portal | Auth, Realtime DB (chat), Push notifications |
| Finix | Webapp, API v1 | Payment processing (perk partners) |
| RyftPay | API v2 (new projects) | Payment processing (new features, split payments) |
| Stripe | Portal | Legacy payment processing |
| HubSpot | API v1, Portal | CRM, lead tracking, contact sync |
| Twilio | API v1 | SMS notifications |
| Mailgun | API v1 | Transactional email |
| DocuSign | Portal | E-signatures for contracts |
| Entrata | Property Feeds | US property data imports |
| Jupix | Property Feeds | UK property data imports |
| BLM | Property Feeds | UK property feed format |
| Mapbox | Webapp, App | Maps, geocoding, property location display |
| Sanity | Webapp | Headless CMS for blog posts and content |
| Mixpanel | App | Mobile analytics and event tracking |
| Google Analytics / GTM | Webapp | Web analytics (proxied via API routes) |
| Cookiebot | Webapp | Cookie consent management (proxied via API route) |
Firebase
Firebase is the most cross-cutting external service.
Housr-App:
- Push notifications via Firebase Cloud Messaging (FCM)
- Real-time chat via Firebase Realtime Database
- Firebase Auth (JWT verification)
API v1:
- Sends push notifications to users
- Writes chat messages to Firebase Realtime Database
- Firebase Admin SDK for server-side operations
API v2:
- Firebase JWT verification for auth (
firebaseguard)
Portal:
- Firebase admin operations
Payment Processing
Housr uses multiple payment providers due to historical evolution:
- Finix: Used by Webapp (perk partners checkout) and API v1. Tokenization on the client, processing on the server.
- RyftPay: The standard for all new payment features. Used in API v2. Supports split payments (e.g., Housr takes a percentage fee). PHP SDK:
ryft-php. iOS:ryft-ios. Android:ryft-android. No React Native SDK — requires native module bridge or WebView. - Stripe: Legacy usage in Portal only. Being phased out in favor of RyftPay.
Property Data Feeds
Housr-Property-Feeds imports property listings from external sources:
- Entrata (US): API integration for US property data
- Jupix (UK): Property feed integration for UK listings
- BLM format (UK): Standard UK property feed format
Imported data is written directly to the shared MySQL database.
CRM and Communication
- HubSpot: CRM integration. Contacts and leads are synced from API v1 and Portal. Used for sales pipeline management.
- Twilio: SMS notifications sent from API v1 (e.g., viewing confirmations, alerts).
- Mailgun: Transactional emails sent from API v1 (e.g., welcome emails, booking confirmations).
- DocuSign: E-signature workflows managed through Portal for tenancy agreements and contracts.
Analytics
- Mixpanel: Event tracking in the mobile app. Configured in
src/lib/mixpanel.ts. - GTM / Google Analytics: Web analytics on the Webapp. GTM and Cookiebot are proxied through API routes (
/api/assets/[resource]and/api/metrics/[script]) to avoid ad blockers. - Sanity: Not analytics per se, but the Webapp’s blog content comes from Sanity CMS, with a studio embedded at
/studio.
Adding a New Integration
When integrating a new third-party service:
- Add credentials to the relevant repo’s
.envfile - Document the service in this page
- For payment processing, use RyftPay (not Finix or Stripe)
- For new API integrations, build the integration in API v2 as a module
- Consider which repos need access — minimize the number of repos that depend on any single service
Last updated on