API
When your own code needs to read data or perform a documented action in Alunta.
Find your endpointAlunta for developers
Build your product. Let Alunta handle subscriptions. Connect customer data and recurring agreements through the API.
REST API · JSON · OpenAPI
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.
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 /customersLet 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-sessionsSelling 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}/usageFrom idea to connection
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.
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.
Store the token securely on your server as ALUNTA_TOKEN and run the example. The request reads customer information without changing data.
Use customer UUIDs to connect the rest of the workflow. The reference helps you find the fields and requests your integration needs.
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 guidecurl --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
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.
Follow the documented signature verification against the raw request body before processing the event.
Accept the delivery and queue the follow-up work on your side. The documentation gives the current response-time limit.
An event can arrive more than once. Make sure repeated delivery does not trigger the same action repeatedly.
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.
An API response helps you find the next step. Here are three common messages and what you can do about them.
401 / 403Check access422Check the content429Give the request timeStuck? 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.
When your own code needs to read data or perform a documented action in Alunta.
Find your endpointWhen a compatible AI assistant should work with selected information and tools from your account.
Explore AI accessWhen an existing connection or workflow can do the work for you.
Find an integrationA 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.
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.
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.
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.
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 togetherUse the documented API for supported customer and subscription operations. Keep credentials private.
Let webhooks notify your software about supported events. Plan for retries and check incoming requests.
Test the complete workflow before launch. Use the documentation to check available operations and limits.