API Finance.HDdev
Integrate Finance.HDdev into your tools. Access your accounts, transactions, budgets and categories via a simple and secure REST API.
Authentication
Bearer token (JWT). Obtain your token from your personal dashboard in the account settings.
Base URL
All requests use the following base URL:
https://finance.hddev.eu/api/v1Format
All requests and responses use JSON format. Required header: Content-Type: application/json
Authentication example
curl -X GET https://finance.hddev.eu/api/v1/accounts \ -H "Authorization: Bearer VOTRE_TOKEN_JWT" \ -H "Content-Type: application/json"
Available endpoints
Overview of the main Finance.HDdev API endpoints.
/api/v1/accountsList of connected bank accounts with balances and metadata.
/api/v1/transactionsList of transactions with filters (date, category, amount, account).
/api/v1/budgetsBudgets and goals with current progress.
/api/v1/transactionsCreate a manual transaction (expense, income or transfer).
/api/v1/categoriesAvailable categories (system and custom).
Rate limits
API requests are rate-limited to ensure service stability.
Full documentation
The full interactive documentation (OpenAPI / Swagger) will be available soon. It will include request and response schemas, error codes and detailed examples.
Security
All communications are encrypted via HTTPS/TLS. JWT tokens expire after 30 minutes (automatic renewal via refresh token). The API is GDPR compliant and never returns banking credentials.
Need help with the API?
Our technical team is available to assist you with integrating the Finance.HDdev API into your tools and workflows.
Contact the API teamapi@hddev.eu
Architecture Principles and Usage
The Finance.HDdev API is based on a RESTful architecture, making it predictable and easy to use. All requests are made via HTTPS to ensure the confidentiality of exchanged data. Responses, as well as POST and PUT request bodies, are systematically formatted in JSON. The URL structure is resource-oriented, allowing you to intuitively interact with the different objects in our system, such as accounts, transactions or budgets. We apply a rate limiting system to ensure platform stability for all our users. Details of these limits are specified in each response header.
Key Endpoints and Use Cases
Our API exposes several endpoints to cover all financial management features. The `/transactions` endpoint allows you to list, filter and retrieve the details of each transaction, ideal for in-depth spending analyses. With `/accounts`, you can get the list of your connected accounts and their real-time balances. For budget tracking, the `/budgets` and `/categories` endpoints give you full control over creating and monitoring your spending envelopes. Finally, the `/goals` endpoint lets you manage your savings goals. These combined tools open the door to many applications, from a simple data export script to a complete mobile financial coaching app.
API Authentication and Security
Security is our absolute priority. API access is protected by personal authentication keys that you can generate, manage and revoke from your user dashboard. Each API request must include your API key in the `Authorization` header as a Bearer Token. It is imperative to keep these keys secret and never expose them on the client side (in browser JavaScript code, for example). All API connections are encrypted with TLS (SSL). We also encourage you to use webhooks to receive real-time notifications on important events, such as a new transaction, rather than continuously polling the API, thereby reducing request volume and optimising performance.