Enlivy is an API-first business management platform designed to streamline financial operations, invoicing, and back-office workflows.
Built with scalability and global compliance in mind, Enlivy gives businesses full control over their data and processes, whether through a modern user interface or direct API integrations.
Enlivy was built from the ground up with an API-first architecture, meaning that every feature available in the UI is also fully accessible via its REST API. This approach enables:
Whether you’re a startup automating your billing stack or an enterprise orchestrating financial operations at scale, the Enlivy API is built to give you full extensibility and control.
This is the link to the Swagger interface containing all available endpoints:
https://api.enlivy.com/swagger
This guide will help you get started by walking through the essentials.
To interact with protected endpoints in the Enlivy API, you must first authenticate using your credentials.
After a successful login, you will receive a JWT token that you can use for subsequent API requests.
To log in and obtain your token, use the following endpoint:
https://api.enlivy.com/authentication/login
Payload for the login authentication call:
{
"email": "example@gmail.com",
"password": "123456",
"remember": true
}string | The email address associated with your account string | password for your accountboolean | true or false. The response if the API call is successful:
{
"token": "pat_xxxxxx|xxxxxxxxxx"
}Once you have the accessToken, you will need to include it in the Authorization header for all future API requests to protected endpoints.
For example, to access an organization’s data:
GET /organizations/12345
Authorization: Bearer <your_token_here>When making an API call to a protected endpoint, include the
Authorization header with the value Bearer :
Authorization: Bearer <your_token_here>Ensure the Bearer prefix is followed by a space and the token itself.
This token will allow you to access various protected endpoints in the API, such as retrieving user details, creating invoices, and more.
Enlivy’s API uses JWT (JSON Web Token) for secure authentication. Understanding the difference between public and protected endpoints is crucial for working with the API.
Some API endpoints are public and can be accessed without authentication. These typically include actions that occur before a user is authenticated, such as:
/authentication/login)For these endpoints, no token is required.
Once you are authenticated and have obtained a token, most API requests to access or modify data are protected and require the Bearer token. These include actions like:
These endpoints require the token to be included in the Authorization header to validate the request.
Once you’re authenticated and have your token, you’re ready to make your first real request to the Enlivy API.
In this example, we’ll fetch details of an existing organization. To do this, you must already have an organization created in your account.
This call retrieves data for a specific organization by its ID.
GET /organizations/{organizationId}Authorization: Bearer
Content Type: application/json{
"data": {
"id": "org_id",
"user_id": "user_id",
"organization_id": null,
"name": "Dummy Name",
"slug": "dummy_name",
"type": "srl",
"country_code": "RO",
"timezone": "Europe\/Athens",
"address_line_1": "Dummy Address",
"address_line_2": null,
"address_city": "Dummy City",
"address_county": "Dummy County",
"address_state": "Dummy State",
"address_iso_3166": "RO",
"address_zip_code": "123456",
"feature_list": ["stripe"],
"membership_plan": "elite",
"user_abilities": [],
"membership_features": []
}
}