Express an obligation.
Submit the business context, parties, amount, and due date through a versioned interface.
AEGVEN for developers
Connect finance to the way you build.
An integration experience designed to bring business financial obligations into your software, without making your customers change how they work.
Developer preview
AEGVEN is in development. This is an introduction to the integration experience. SDK downloads, installation guides, and the public API reference are available at sdk.aegven.com. Organization access, environment details, and supported scope are agreed during onboarding. Your administrator or developer creates server credentials through individual console access.
A familiar starting point
Your workflow stays at the center.
Connect from your application’s backend, preserve your own source references, and bring updates back into the systems your business relies on.
Connect the interaction.
Include the returned hosted link in your existing customer communication. The recipient can engage without creating an AEGVEN account.
Keep records informed.
Use resource queries and signed event updates to reflect progress in your application.
API & SDK
Less integration guesswork.
Our TypeScript/JavaScript, Python, C#/.NET, and Go SDKs follow the same API contract. The developer experience centers on explicit credentials, exact monetary values, safe retries, and clear errors.
Choose your languageVersioned REST interfaces
A clear boundary between your application and AEGVEN.
Typed resources
Request and response shapes aligned with the API.
Signed event updates
Progress you can authenticate and process in your own workflow.
Setup and recovery tools
Test event delivery, inspect readiness, and investigate uncertain requests.
Build with context
Start with the obligation.
Understand the outcome.
An obligation represents what a business owes or is owed, and the context behind it. The initial developer workflow uses invoices as a source. This first integration does not define the limits of our broader vision.
Financial progress needs to be interpreted carefully. A report that someone has paid is different from a confirmed, reconciled outcome. The integration guide explains how to keep that distinction clear in your own software.
Understand status and outcomesDeveloper resources
The next steps, in one place.
Understand the API.
Source references, exact amounts, hosted links, accepted outcomes, and recovery after uncertain requests.
Integration guideChoose an SDK.
Installation and registration examples for TypeScript/JavaScript, Python, C#/.NET, and Go.
Language SDKsPrepare your workflow.
Organization access, credentials, webhook testing, customer communication, and CSV onboarding.
Setup & onboardingLet’s build the connection