Embed messengers in your SaaS product through Teletype API

WhatsApp, Telegram, MAX, VK, Avito, Instagram, and live chat - for the users of your service. Ready API, documentation, sandbox environment, and a dedicated manager during integration. Earn from every connected user.

  • Documented REST API + ready SDKs
  • All key messengers, including WABA and MAX, through a single entry point
  • Accounting and legal documents (invoices, statements) handled on our side
  • 24/7 support for your users - we handle technical questions about channels
Open API documentation
Audience

Who it's for

Technical partner - owner of a SaaS product who adds communications to their offering

CRM systems

Custom or niche CRMs, ERPs, sales and support automation systems.

Medical systems (EMR/EHR)

Clinics, labs, telemedicine - appointments, reminders, patient communication.

Booking and scheduling services

Beauty, fitness, restaurants, services, education, sports.

Industry-specific SaaS

Real estate, logistics, e-commerce, B2B services, marketplaces.

Helpdesk and ticketing systems

Customer support, request handling, response automation.

1C configurations and ERP

Manufacturing, retail, services - embedded customer communications.

What's included

What you get

Ready solution for embedding messengers - without your own infrastructure, certifications, or channel support

Technical stack

  • REST API with detailed documentation
  • Ready SDKs for popular languages
  • Sandbox environment for development and testing
  • Webhooks for real-time event delivery
  • Demo account for presentations and testing with real connected channels

Integration support

  • Technical manager during integration - guides your team from first code to launch
  • API support: complex case review, optimization, architecture advice
  • End-user support - we handle technical questions about channels
  • Direct Telegram/Slack channel with Teletype's product team

Commerce and legal

  • All channels (including WABA) connected by us - without your own Meta certification
  • Invoices, statements, legal handling - on Teletype's side
  • Transparent billing analytics for each of your users
  • Flexible billing models: per-user, per-channel, or custom
Process

How integration works

From first message to launch - typically 2-4 weeks

  1. Week 1

    Application and discussion

    Fill the form, agree on commercial terms, sign NDA. Get sandbox and documentation access.

  2. Week 1-2

    Technical integration

    Your team works with the API. Teletype's technical manager helps with architecture and complex cases. Test scenarios in sandbox.

  3. Week 2-3

    Channel setup

    We connect all required channels (WhatsApp, Telegram, MAX, WABA, etc.) - without your provider certifications.

  4. Week 3-4

    Production launch

    Switch integration to live environment, train your team, set up monitoring. You start onboarding users.

FAQ

Frequently asked questions

How is technical partner different from regular integrator partner?
An integrator partner deploys Teletype to clients as a finished product. A technical partner embeds Teletype's functionality into their own SaaS product through API - for their own users. Different models, different commercial terms.
Do I need to go through Meta certification myself for WhatsApp Business API?
No. All certifications and channel connections are on Teletype's side. You get ready functionality through our API - without working with Meta, Telegram, or other providers directly.
Who handles end-user support?
Technical questions about channels - we handle them, we know messengers best. Product questions about your service - on you. The boundary of responsibility is fixed in the contract to avoid grey zones.
Can the fact that Teletype is under the hood be hidden?
Yes - for that, there's the White Label format with a dedicated page and terms. On the basic technical partner tier, Teletype branding remains visible in part of the interface (if you use ready UI components). Working through API only - Teletype is not visible to users.
How are payments structured and who pays whom?
We use a hybrid model - choose the optimal option per case: - Revenue share - Teletype invoices end users through your interface and pays you commission on subscriptions. - Direct billing - you pay Teletype based on usage (with volume-based partner discount), and set your own prices for users. The margin between your price and ours is your revenue. The specific model is determined in commercial discussions based on your product and user volume.
Is there a minimum volume below which you don't work?
For API integration - no minimum, you can start with a single user. For custom terms and White Label - we discuss at volumes from 100 users of your system.
How quickly can I get test API access?
Sandbox environment and documentation open after a brief initial application and NDA signing - typically within 1-2 business days.

Tell us about your SaaS - we'll suggest the optimal model

Fill the short form - a manager contacts you within one business day to discuss technical details, scale, and commercial terms.