For you who build software

Your product can do more when everything works together.

Are you building analytics tools, automation or other products for subscription businesses? As an integration partner, you can connect your product to Alunta and make the connection available where customers already work.

Create account and applySee the partner process

Do you have an Alunta account? Apply for partner access under Extensions.

From connection to common valueAn integration. Two products that help each other.
  1. AluntaCustomers, subscriptions and billing
  2. Your integrationThe data and events your product needs
  3. Your productInsights and workflows for your joint customers

The customer chooses to activate the connection. You build the experience together.

Build something the customer enjoys every day.

A good integration solves a specific task between two products. Start with the workflow your mutual customer spends time on today.

From subscription data to insight

Let your analysis product work with the customer's subscription data. Give the figures a context so that the customer can follow his business without moving data manually.

From event to action

Use relevant webhooks as a starting point for automation in your product. A subscription that starts or ends can be the start of a task in the customer's other workflow.

From single project to product

Build a connection that multiple customers can use. After review and approval, the integration can be published in Alunta's overview of extensions.

The partner process

From idea to a connection the customer can activate.

A good idea must go to the customers. We have compiled the path from application to activation in the partner portal, so you can use your efforts to build a connection that makes a difference.

  1. Apply for partner access

    Create an Alunta account and apply under Extensions. Describe your product and the task the integration must solve, so that we have a common starting point.

    Start with the customer's needs

  2. Present your integration

    When you have access to the partner portal, you fill in your company profile and the description of the integration. Make it clear who it is for and what the customer needs in place.

    Make expectations clear

  3. Build and test the connection

    Use the API documentation and portal test webhooks to develop the integration. Test both the normal process and the handling of errors, repeated incidents and separate customer accounts.

    Test more than the first success

  4. Send for review

    Submit the integration when it is ready. Alunta reviews it before approval and release. Clarify any questions and corrections as part of the process.

    Approval before publication

  5. Allow customer to activate

    The approved integration will be available in Alunta's extensions overview. The customer activates the connection and follows the steps your product requires to get started.

    A clear way into your product

An example from the partner program

GrowPanel makes subscription data an overview.

GrowPanel is an analytics product for subscription businesses. The integration connects data from Alunta with dashboards for, among other things, MRR, churn, customer lifetime and cohorts.

For the customer, the value is concrete: subscription data can be included in the analysis without an ongoing manual export. For GrowPanel, Alunta is a connection to the data base from which the product creates insights.

See GrowPanel integration
  1. Subscription data in Alunta
  2. GrowPanel integration
  3. MRR · churn · cohorts
The workflow in the example. The illustration does not show actual customer figures.

The connection must last in everyday life

Consider the customer's access and operations from the start.

A partner integration must work for several companies, each with their own data. The technical choices are also part of the customer experience.

OAuth and the right team

API access is tied to the team and the rights the token gives access to. The public reference describes OAuth and recommends prompt=consent for partner integrations so that the customer selects team and confirms access on connection.

Webhooks with space for repetitions

Check the signature of the original request body, respond quickly, and handle the event afterwards. Deliveries can be repeated, so the same event cannot create the same action twice.

Test, debug and maintain

Use test webhooks to check your receiver and test in an Alunta account without production data before deployment. Follow the API contract, handle interrupted access, and give the customer an understandable path forward when something goes wrong.

Go from overview to implementation.

Start in the public documentation. Use the partner portal for the parts of the setup that belong to your integration.

01 / Get started

Access, first calls and webhooks

Get an overview of tokens, team access, errors, retries and the first API calls.

Read Getting Started

02 / API reference

The current contract

Find endpoints, fields, events and OAuth notes. Use the reference to check your concrete implementation.

Open the API reference

03 / Development tools

Documentation in your own flow

Use the OpenAPI file for clients and contract testing. In the partner portal, you can also download the documentation as markdown for your code assistant. Always review and test the code you build with it.

Get the OpenAPI file

A partnership has two sides.

You know your product

You develop and maintain your integration, describe the setup and help the customer with the use of your product. Make any account, subscription and data access requirements clear before activation.

We know Alunta

Alunta provides the API, documentation and partner process and reviews the integration before release. If you have questions about Alunta's side of the connection, take them with us along the way.

Want to talk through an integration idea before you build it?Write to us about your product

Questions before you start.

What is the difference between using the API and being an integration partner?

You can use the API for a connection in your own business. The partner program is for you if you are building an integration for your software product and want to make it available to more Alunta customers through the extensions overview.

How do I access the partner portal?

Create an Alunta account or log in to the one you already have. Apply for partner access under Extensions. Once you have access, you can work with profile, integration setup and testing in the partner portal.

Will the integration become public immediately?

No. You build and test first and then submit the integration for review. It must be approved before publication. The time course depends on the integration and the questions or corrections that need to be clarified.

Does the customer also have an account in my product?

It depends on your integration. Clearly describe whether the customer must create an account, choose a subscription or carry out further setup with you. Activation in Alunta must be related to the experience your product offers.

Can I use a code assistant for development?

Yes. You can use documentation such as markdown from the partner portal and the public OpenAPI file as a basis. You are still responsible for checking the code, protecting tokens and testing access, webhooks and error handling, among other things.