Alunta for developers

Build what your customers love. Let Alunta handle subscriptions.

Build your product. Let Alunta handle subscriptions. Connect customer data and recurring agreements through the API.

REST API · JSON · OpenAPI

Your product and Alunta. One workflow.
Your productCRM · app · your checkout
REST APIRead data and perform actions
AluntaCustomers · subscriptions · invoices
WebhooksGet notified when something changes

Less duplicate entry. More time for your product.

Create customer records once and connect them to your recurring billing. Use Alunta’s API to bring subscriptions into your existing product, CRM or support workflow.

  1. Know the customer where you work

    Show customer subscriptions in your own system, keeping agreements close at hand for sales and support. The API gives you customer data and the references to connect it with the rest of your business.

    GET /customers
  2. From your product to a new subscription

    Let customers choose in your app and buy through Alunta’s checkout. A checkout session and the event after purchase connect the experience with your product.

    POST /checkout-sessions
  3. Connect usage to billing

    Selling on usage? Send measurements from your app to Alunta and include them in subscription usage billing. You build the product; Alunta connects the measurements with the agreement.

    POST /subscriptions/{uuid}/usage

From idea to connection

Your first connection is closer than you think.

You do not need to build the whole integration at once. Fetch your customers, inspect the response and take it from there. We have the documentation and a first example ready for you.

  1. Prepare access

    Enable API access in Alunta and use an access token for the account your integration will work with. Access follows the token’s permissions and its associated account.

  2. Fetch your customers

    Store the token securely on your server as ALUNTA_TOKEN and run the example. The request reads customer information without changing data.

  3. Build on the response

    Use customer UUIDs to connect the rest of the workflow. The reference helps you find the fields and requests your integration needs.

Your first API request

This example uses the documented v1 URL and bearer authentication. It requires a valid token with customer access on your Alunta account.

Read the getting started guide
GET /api/v1/customers
curl --request GET \
  'https://app.alunta.com/api/v1/customers' \
  --header "Authorization: Bearer $ALUNTA_TOKEN" \
  --header 'Accept: application/json'

ALUNTA_TOKEN is an environment variable in your own environment. Keep the token on the server and out of source code, browser code and logs.

When your data changes

Let your systems keep each other updated.

A subscription changes. A payment is recorded. Your product can hear about it and carry on while the team spends its time on customers. That is what webhooks are for.

Choose the relevant events and receive them at your HTTPS endpoint. Technical details on signatures, delivery and retries are ready in the documentation.

  1. Verify the sender

    Follow the documented signature verification against the raw request body before processing the event.

  2. Respond quickly, continue afterwards

    Accept the delivery and queue the follow-up work on your side. The documentation gives the current response-time limit.

  3. Handle retries

    An event can arrive more than once. Make sure repeated delivery does not trigger the same action repeatedly.

Give your coding assistant something useful to work with.

Building with a coding assistant? Give it Alunta’s OpenAPI file and documentation so it works with the right endpoints and responses. You get a concrete starting point for the integration and more time for your own code.

Understand the response. Find the next step.

An API response helps you find the next step. Here are three common messages and what you can do about them.

401 / 403Check access
Check the token, permissions and whether the API module is available on the account.
422Check the content
Read the validation error and the endpoint’s requirements for fields and actions.
429Give the request time
Respect Retry-After and limit concurrent requests. Reads and writes have separate quotas.

Stuck? Send us the X-Request-Id so we can help trace the request. Write requests and failed requests appear under Settings → API → Log. Keep your token private.

There is more than one way to do less work.

API

When your own code needs to read data or perform a documented action in Alunta.

Find your endpoint

MCP

When a compatible AI assistant should work with selected information and tools from your account.

Explore AI access

Integrations and Zapier

When an existing connection or workflow can do the work for you.

Find an integration

Good questions. Let’s get you moving.

Can the API work with all my Alunta accounts?

A token grants access to its associated account and the actions its permissions allow. Plan the account connection in your integration. Use /me to see the authenticated account’s context.

Can I use the API from a browser?

Keep the token on the server. Have your server call Alunta and pass your interface only the information it needs. Do not put your API token in public browser code.

What if I need another endpoint?

Tell us about the workflow and the information or action you need. We are happy to explore it with you. The public reference shows what you can build with today.

Can you help with my integration?

Yes. Send a description of what you want to connect, the endpoint and any HTTP status or X-Request-Id to support@alunta.com. Leave tokens and sensitive customer data out of the message.

What will you connect to Alunta?

Have an idea, a frustrating manual task or an integration you want to build? Talk to us. We are happy to help find a good connection between your product and Alunta.

Let’s build the connection together

Start with the API

Use the documented API for supported customer and subscription operations. Keep credentials private.

Stay updated with webhooks

Let webhooks notify your software about supported events. Plan for retries and check incoming requests.

Test the complete workflow

Test the complete workflow before launch. Use the documentation to check available operations and limits.