For integration, automation, SSO and external systems
API & integration for subscription management and billing
Integrate tebio with your existing frontends, CRM, ERP, Finance, provisioning, data warehouse, product and identity systems. API, Webhooks and identity features connect customers, subscriptions, orders, invoices, payments, documents, events and login processes with your system landscape.
Subscription processes don't end in a single system.
Recurring business models touch many systems: website, checkout, customer portal, CRM, ERP, Finance, provisioning, support, BI, product backends and identity providers. If customer, subscription, payment, billing and login data are not cleanly connected, the result is manual synchronization, inconsistent status information and error-prone downstream processes.
System integration and data exchange
Customer and subscription data must be available in multiple systems.
External frontends need access to products, orders, subscriptions or payment status.
Provisioning systems need to know when a subscription was activated, changed, paused or canceled.
Finance systems need invoice, payment and report data.
CRM and support teams need up-to-date customer and contract information.
Data warehouses or BI systems need structured events and billing data.
Identity and access concepts
Customers, partners or internal teams need suitable login and access concepts.
SSO and identity provider requirements must fit portal, customer and partner processes.
Process automation and reliability
Manual exports and imports cause delays and errors.
Status changes must be able to trigger external processes reliably.
tebio connects platform processes with your system landscape.
With API, Webhooks and identity features, tebio can be integrated with your existing systems. The API provides technical access to tebio resources and processes. Webhooks notify external systems about relevant events. Identity and SSO features support suitable login, authentication and access processes.
These integration building blocks complement the Business Portal and Hosted Pages. Internal teams work in the portal, customers and partners use digital ordering, Self-Care or partner processes, and external systems stay connected via interfaces, events and identity processes.
Three building blocks for integration
At tebio, integration means more than data exchange. Depending on the setup, API, Webhooks and identity processes can work together so that data, events and access stay consistent across systems.
API
The API lets you connect tebio from external systems — for example to process customers, subscriptions, orders, invoices, payments or other resources.
Typical for
Custom frontends
Product backends
CRM
ERP
Finance and provisioning integrations
Webhooks
Webhooks send events to external systems when relevant changes happen in tebio — for example for customers, subscriptions, invoices, payments, documents or support processes.
Typical for
Automation
Status synchronization
Provisioning
Reporting
Notifications and downstream processes
Identity & SSO
Identity and SSO features support login, authentication and access processes for internal teams, customers or partners — depending on setup and configuration.
Typical for
Single sign-on
External identity providers
Customer login
Partner login
Roles and access concepts
Typical workflows with API, Webhooks and identity
1. Connect your own frontend
An existing portal or your own website can integrate tebio via API, while tebio processes customers, subscriptions, billing, payments and downstream processes.
2. Complement Hosted Pages
Hosted Pages can be used for standardized checkout, Self-Care and partner processes. API and Webhooks complement these processes when external systems need to be notified or additional data needs to be synchronized.
3. Synchronize customers and subscriptions
CRM, ERP or product systems can align customer and subscription data with tebio so that operational and technical systems work with up-to-date information.
4. Trigger provisioning
When a subscription is created, changed, paused or canceled, connected systems can start downstream processes via Webhooks, for example granting or revoking access.
5. Process billing and payment events
External systems can react to invoice, payment, document or status events and use them for Finance, support, reporting or customer communication.
6. Provide data for reporting
Data warehouses, BI systems or reporting processes can further process relevant customer, subscription, billing or payment data from tebio.
7. Connect support and helpdesk
Customer, ticket and event data can be used to connect support processes with subscription and billing context.
8. Integrate SSO and existing identity providers
Depending on the setup, internal teams, customers or sales partners can be included in tebio-related access processes via existing identity providers or SSO processes.
9. Integrate industry processes
Publishers, telco providers, healthcare platforms, IoT providers or fitness providers can connect industry-specific systems with tebio.
What you can integrate via the API
Integrate customers
Customer data, addresses, contacts, properties and relevant customer information can be included in integrated processes.
Connect subscriptions
Subscriptions, status, terms, options, changes, pauses or cancellations can be connected with external systems.
Process orders
Order processes from your own frontends, Hosted Pages or internal workflows can be connected with tebio and processed further.
Take products, options and prices into account
Product, option and pricing logic can be included in external frontends, offer flows or internal processes.
Use invoices and documents
Invoice, receipt and document information can be processed further in customer portals, finance processes or support systems.
Integrate payments
Payment methods, payment status, open items, incoming payments and refunds can be used in the context of billing and subscription processes.
Connect helpdesk and customer context
Support processes can be linked with customer, subscription, invoice or event data.
Support configuration and technical processes
API keys, Webhooks, events and other integration features support technical setups and automated processes.
Use events as soon as something changes
Webhooks notify external systems about relevant events in tebio. This lets connected systems react to changes in customer, subscription, billing, payment, document or helpdesk processes.
Customer events
External systems can react when customers are created, changed or become relevant for further processes.
Subscription events
Systems can react when subscriptions are created, changed, paused, canceled or otherwise modified in their lifecycle.
Order events
Orders from Hosted Pages, the Business Portal or API processes can trigger downstream processes in external systems.
Billing and invoice events
Invoices, receipts, invoice corrections, cancellations (reversals) or billing-related documents can be relevant for Finance, support or customer portals.
Payment events
Payment status, incoming payments, open items, failed payments or refunds can trigger external processes.
Document and communication events
Generated documents or messages can be relevant for customer communication, archiving or external portals.
Partner and commission events
Partner-related orders, subscriptions or commission processes can be relevant for partner portals, Finance or external sales systems.
Webhook receivers should process events idempotently, log errors and, if needed, check the current state via the API.
Integrate identity, login and SSO
Besides API and Webhooks, login and identity processes can also be part of a tebio integration. Companies can integrate tebio into existing authentication and SSO landscapes so that internal teams, customers or partners can work with suitable access and roles.
tebio uses Keycloak-based identity and access mechanisms. Depending on the setup, this can support single sign-on, external identity providers and customer-specific login processes. This lets you integrate the Business Portal, Hosted Pages, customer portal, sales partner portal and external systems consistently into existing access processes.
Subscription Management / Billing / Payments / API
Portal, Hosted Pages, API and identity work together
Business Portal
Internal teams manage customers, subscriptions, orders, products, invoices, payments, helpdesk and settings in the tebio Business Portal.
Hosted Pages
Customers, sales partners or affiliate partners use Hosted Pages for order flows, checkout, Self-Care, registration or partner-side processes.
API & Webhooks
External systems access tebio technically or are notified about relevant events so that processes can be synchronized automatically.
Identity & SSO
Depending on the setup, login, role and access concepts can be connected with existing identity providers and SSO landscapes.
Integrate with your existing system landscape
API, Webhooks and identity features help connect tebio with systems already in use at your company. This keeps customer, subscription, billing, payment and access data available in the relevant processes.
Custom frontends and portals
Your own websites, customer portals or Self-Care interfaces can use tebio as their subscription and billing backend.
CRM
Customer data, sales processes and support information can be connected with subscription and billing context.
ERP and Finance
Invoices, payment status, reports, journal and DATEV-ready processes can be included in downstream finance processes.
Product backends
Digital products, content access, licenses or service entitlements can react to subscription status.
Provisioning systems
Activation, modification or deactivation of services can be triggered by subscription or payment events.
Data warehouse and BI
Customer, subscription, billing and payment data can be processed further for reporting, analysis and management.
Helpdesk and support
Support systems can use customer, contract, invoice and payment information to handle requests faster.
Identity providers and SSO
Depending on the setup, existing login and identity landscapes can be connected with tebio so that internal teams, customers or partners can work with suitable access and roles.
Industry platforms
Publishing systems, telco systems, healthcare platforms, IoT platforms or fitness systems can be connected with tebio.
Documented and testable for developers
tebio provides technical features so that developers can plan, test and operate integrations. API reference, API keys, Webhooks, events, playground and identity concepts support the implementation of your own integrations.
API reference
The API reference describes resources, parameters, requests, responses and technical details for the integration.
API keys
API keys can be used to connect external systems with tebio in a controlled way.
Webhooks
Webhook endpoints can be configured so that external systems receive relevant events.
Events
Events help transfer business changes from tebio to external processes.
Playground
The playground helps you test and understand technical flows before integrations go into production.
Identity and login
Depending on the setup, Keycloak-based login and access processes can be used for SSO, external identity providers and role-based access.
Documentation
The tebio documentation explains integration concepts, typical workflows and practical setup steps.
Operate interfaces and access in a controlled way
Integrations for subscription management and billing are business-critical. That's why API access, webhook receivers, error handling, monitoring, login processes and role models should be planned deliberately. tebio supports a structured technical connection via documented interfaces, configurable integration features and identity-related access mechanisms.
API and webhook management
Manage API keys in a controlled way
Configure webhook endpoints specifically
Process events traceably
Log errors
Handle repeated events idempotently
Check the current state via API if needed
Identity and access management
Align SSO and identity processes depending on the setup
Configure roles and access deliberately
Technical preparation and collaboration
Use a test environment or playground for technical preparation
Clarify responsibilities between tebio and external systems
Integrate billing, payment and finance processes
API and Webhooks are especially relevant when billing, invoice, payment or financial data needs to flow into external systems. This lets Finance, support, reporting and product processes react to current billing and payment events.
Receipt was createdPayment status was updatedPayment failedOpen item was detectedRefund was recordedDocument was createdExternal systems check current data via APIDATEV-ready processes are preparedReport data is processed further
Subscription
Billrun
Invoice / payment
Billing or payment event
Webhook
External system
API check / downstream process
Integrations for different business models
API, Webhooks and identity features help companies integrate tebio into industry-specific processes — from digital products and customer and partner portals to complex subscription and billing system landscapes.
The tebio documentation shows how API, Webhooks, events, playground, Hosted Pages and platform processes can be used to integrate tebio with external systems.
Identity, login and SSOUnderstand how login, role and identity processes can be connected with tebio depending on the setup.
Frequently asked questions
What does tebio offer with API and Webhooks?
tebio provides API and Webhooks so that external systems can work with customers, subscriptions, orders, invoices, payments, documents and events from tebio. The API is used for active technical integration, while Webhooks notify external systems about relevant events.
What is the difference between API and Webhooks?
The API is used when an external system actively communicates with tebio. Webhooks are used when tebio notifies external systems about events, for example changes to customers, subscriptions, invoices or payments.
Does tebio support single sign-on?
Depending on the setup, tebio can be integrated into SSO and identity provider landscapes. This lets internal teams, customers or partners work with suitable login and access processes.
Does tebio use Keycloak?
tebio uses Keycloak-based identity and access mechanisms. Depending on the setup, this allows login processes, roles and external identity providers to be included in tebio-related processes.
Can customers or partners access tebio via their own login processes?
Depending on the configuration, customer or partner access can be connected with Hosted Pages, Self-Care, the sales partner portal and identity provider processes. The exact scope depends on the setup and the access requirements.
Is SSO part of the API?
SSO is not an API endpoint but part of the identity and access integration. API, Webhooks, Hosted Pages and SSO serve different purposes, but can be combined in one platform architecture.
Can I connect my own frontend with tebio?
Yes. Your own websites, portals or product frontends can integrate tebio via API and Webhooks. Alternatively or additionally, Hosted Pages can be used for standardized ordering and Self-Care processes.
Which systems can be connected?
Typical integration targets are CRM, ERP, finance systems, product backends, provisioning systems, customer portals, support systems, data warehouses, BI systems, identity providers and industry-specific platforms.
Can external systems react to subscription changes?
Yes. Webhooks can notify external systems about relevant subscription events. This can trigger downstream processes such as activation, deactivation, reporting or customer communication.
Can billing and payment events be integrated?
Yes. API and Webhooks can be used to connect invoice, payment, document or status events with external systems.
Is there an API reference?
Yes. The tebio API reference describes technical resources, parameters, requests, responses and integration details.
Is there a playground?
Yes. The playground helps developers test technical flows and better understand the API before using it in production.
Do API and Webhooks replace the Business Portal?
No. API, Webhooks and the Business Portal serve different purposes. The Business Portal is the interface for internal teams. API and Webhooks are intended for technical integration and automation. Many setups use both together.
How should webhook events be processed?
Webhook receivers should process events idempotently, log errors and, if needed, check the current state via the API. This keeps external processes more robust, even if events are processed repeatedly or with a delay.
Is tebio a pure developer platform?
No. tebio combines the Business Portal, Hosted Pages, API, Webhooks, identity features, billing, payments and finance-related processes. Developers can integrate tebio while business teams handle day-to-day processes in the portal.
Ready to integrate tebio into your system landscape?
Start with tebio for free or talk to us about how you can connect customers, subscriptions, billing, payments, Hosted Pages, API, Webhooks and identity processes with your existing systems.