logo main
  • Language
    En
    English
    • Log in|Sign up
    Capterrarating stars4.8
    G2rating stars4.6

    11 API calls.
    Full control over your integration layer.

    User provisioning, billing, and connections — fully managed by you without dev work. Your customers see a native experience. Your devs ship integrations in days, not months.

    Read the docs

    11

    API methods is all you need

    30–45

    days on average to production

    0

    front-end frameworks to handle

    3 steps from signup to live integrations

    Your API talks to Albato's API. Your frontend shows the Albato iFrame. Your customers connect their apps in 3 clicks without ever leaving your product.

    • Step 1

      Create a user with one API call

      When a customer opens your integrations page, you call our API endpoint. Albato returns a session token — your customer's key to the integration builder.

      Create a user with one API call
    • Step 2

      Show the integration builder in your UI

      Plug an iFrame into your frontend. Pass the session token. Your customers see a fully branded automation builder inside your product. It auto-resizes and works across all devices.

      Albato integration builder inside your UI
    • Step 3

      Control billing and connections programmatically

      Assign user plans, add transaction caps, and manage available apps. You own the customer experience & monetization.

      Control billing and connections programmatically
    See the full implementation guide

    Everything you need to run integrations as your native feature

    11 API methods across four areas. Each one maps to a real product experience — not a technical exercise.

    Albato embedded integrations

    Create an Albato user when a new customer opens the integration page. Auto-refresh user tokens. Remove users when they churn. All done programmatically and under your control.

    • Auto-provision access to users with a single POST request
    • Enable SSO — no extra auth to your app needed
    • Block, unblock, or delete users programmatically
    Chatfuel manages 2,000+ integration users — zero support tickets for provisioning.

    Assign billing plans that match your pricing tiers. Top up transaction limits when customers need more. Turn Albato integrations into a revenue stream.

    • Map Albato plans to your pricing tiers
    • Top up user transactions on the fly
    • Check available plans and current usage
    RD Station turned integrations into a paid feature — 73% activated in month one.

    Manage all webhooks programmatically. Albato subscribes to your webhooks and automatically receives real-time payloads whenever an event happens on your end. Your users never touch webhook URLs — it's just a seamless plug-and-play experience.

    • Pre-configure webhooks as one-click toggles for your users
    • Auto-subscribe and unsubscribe users to webhooks when integrations are enabled or disabled
    • Fetch custom webhook fields dynamically via API
    1,000+ pre-built connectors. Instant access — no custom integrations needed.

    One permanent token for server-side calls. Auto-expiring session tokens for customer sessions. SOC 2 Type 2 infrastructure underneath.

    • API key for backend ops (permanent)
    • JWT session tokens for iFrame (auto-expire)
    • AES-256 encryption, GDPR, SOC 2 Type 2
    Explore all 11 methods

    What makes this different from building it yourself?

    Your engineering team has better things to do than maintain integration infrastructure.

    • Time to market

      Days, not months

      Average implementation takes 30–45 days — user provisioning, billing, white-labeling, and go-live included. Compare that to 4–7 months for in-house.

    • devices

      Your brand, everywhere

      White-label the entire experience — iFrame, OAuth pages, notification emails. Your customers never see 'Albato.' The Pro plan includes a custom domain and full brand control.

    • api

      1,000+ connectors on day one

      Your customers get access to every connector the moment you go live. No building, no maintaining, no keeping up with API changes.

      connectors

    • You own the billing logic

      Map Albato plans to your pricing tiers. Charge what you want for integrations, bundle them into your plans how you want. Integrations become a revenue stream, not a cost center.

    Teams shipping integrations with Albato's API

    • 250K+users across partner platforms
    • 300Kmonthly tasks
    • 1B+monthly API calls
    • 99.99%success rate
    Read the full API docs

    Common questions from engineering and product teams

    How long does a typical implementation take?

    collapsed

    Most teams go live in 30–45 days. That covers discovery, iFrame setup, user provisioning, billing integration, white-labeling, and QA. You get a dedicated PM, CSM, and API engineer from day one — not just on enterprise plans.

    What happens when a third-party API changes?

    collapsed

    Albato maintains all 1,000+ connectors. When an API updates, Albato's team handles the fix. Your engineering team doesn't monitor changelogs or patch integrations — that's included in every plan.

    What's a transaction, and how is it different from an API call?

    collapsed

    A transaction counts only when Albato successfully moves or modifies data. Polling and trigger checks are free. On average, 1 transaction replaces 4–5 API calls — so you're paying for results, not requests.

    What security certifications does Albato have?

    collapsed

    SOC 2 Type 2 (annual audits), GDPR compliant, pursuing ISO 27001. Infrastructure runs on AWS across 2 availability zones. Data encrypted with AES-256 at rest, TLS 1.2/1.3 in transit. Credentials stored on a separate key server. Regular third-party penetration testing.

    How does Albato compare to using Zapier for embedded integrations?

    collapsed

    With Zapier, your customers leave your platform, create a separate Zapier account, and pay Zapier directly. You lose revenue, brand control, and UX continuity. With Albato, everything stays inside your product — your brand, your billing, your customer relationship.

    Do our customers need to create an Albato account?

    collapsed

    No. Your backend creates users via API and passes a session token to the iFrame. Your customers never see a login screen, a redirect, or the Albato brand. It's SSO by design.

    How does billing work? Do our customers pay Albato?

    collapsed

    No. You control the billing relationship entirely. Map Albato plans to your own pricing tiers, top up transaction limits for power users, and bundle integrations however you want. Your customers only see your pricing. Albato charges you a platform fee — from $5,000/month on Pro.

    Can we white-label the entire experience?

    collapsed

    Yes. iFrame UI, OAuth screens, email notifications — all customizable. On the Pro plan ($3,000/month), you get custom domain support and full brand control. Your customers never see "Albato" anywhere.

    Can we build custom connectors for apps not in the catalog?

    collapsed

    Yes. On the Pro plan, Albato builds up to 2 custom connectors per month for you — no SDK work on your side. Starter plans can request custom builds as add-ons.