Connect your own software through API and webhooks
Want to process eBox and MyMinfin messages automatically in your ERP, DMS or your own application? Here is how the integration with Boxflow works.
What you need
- A Boxflow account with at least one connected company.
- An HTTPS endpoint in your own software that can receive requests.
- An API token, created in your Boxflow profile.
How the integration works
-
1
New message
Boxflow retrieves a new message from eBox Enterprise or MyMinfin.
-
2
Automation
An automation with your conditions sends a webhook to your endpoint.
-
3
Your software
Your endpoint receives the data and, if needed, retrieves details and attachments through the REST API.
Step by step
-
1
Create an API token
Create an API token in your Boxflow profile. Store it securely: you will use it as a Bearer token for the REST API.
-
2
Provide an endpoint
Provide an HTTPS endpoint in your software that receives webhooks and quickly returns a 2xx response. Ideally, process the message asynchronously.
-
3
Add a webhook action
In Boxflow, create an automation with the desired conditions and add a webhook action. Choose the HTTP method (e.g. POST), the format (JSON or XML) and the authentication.
-
4
Compose the payload
Define the webhook payload yourself using placeholders such as {{ message.uuid }}, {{ message.subject }}, {{ sender.name }} and {{ company.name }}. That way your software receives exactly the fields it needs.
-
5
Retrieve details and attachments
Use the message ID from the webhook to retrieve the message details and attachments through the REST API.
Webhook authentication
- No authentication (only recommended for testing).
- Basic authentication with username and password.
- Bearer token in the Authorization header.
- API key in a header of your choice.
- You can also add your own custom headers.
Retries
- On a temporary error (timeout, 408, 429 or 5xx), Boxflow retries automatically.
- Up to 10 attempts, with increasing intervals spread over about 3 days.
- Every attempt is logged in the message's audit trail.
- Tip: make your endpoint idempotent based on the message ID, so a repeated delivery does not create duplicates.
REST API
- List workspaces and users.
- List the messages of a workspace and retrieve message details.
- List and download the attachments of a message.
- Bearer token authentication; the full documentation is available at /apidocs.
Frequently asked questions
What data does a Boxflow webhook contain?
You decide. You compose the payload with placeholders for the message, sender, company, status and workspace.
What if my server is temporarily unavailable?
Boxflow retries automatically, up to 10 times over about 3 days.
How do I download attachments through the API?
With the message ID from the webhook, you list the message's attachments and download each one through the REST API, using your API token as a Bearer token.
Read next
Billit
Government letters straight into Billit, via email
Read moreExact Online
Government letters straight into Exact Online, via email
Read moreMake.com
eBox messages in SharePoint automatically
Read moreOdoo
Government letters straight into Odoo, via email
Read morePower Automate
eBox messages in SharePoint or Teams with Power Automate
Read moreSingle sign-on
Log in with Microsoft Entra ID or Google Workspace
Read moreZapier
Coming soon: connect Boxflow to thousands of apps
Read moreReady to put your eBox on autopilot?
Connect your first company for free and receive your government messages wherever you need them.