Build it yourself or use Boxflow?

eBox Enterprise offers a REST API for DocConsumers. With your own development team, you can integrate it yourself. But what does that involve?

Boxflow

eBox Enterprise and MyMinfin out of the box, with API and webhooks to build on.

Boxflow interface

Build your own

Full control, but you build, host and maintain everything yourself.

Short answer

Building your own gives you full control and no vendor dependency, but requires development and ongoing maintenance. Moreover, according to the FPS Finance, the MyMinfin API is available through registered software companies, which makes it hard to access for a regular company. Boxflow provides both integrations out of the box, with an API and webhooks to build on.

Comparison at a glance

Build your own eBox DocConsumer and MyMinfin integration?
Boxflow Build your own
Costs Subscription with public pricing; free plan for 1 company. No licence, but development, hosting, security and maintenance.
eBox Enterprise Ready to use, including onboarding wizard. Possible through the DocConsumer REST API; requires certificates, OAuth onboarding and support for multiple document providers.
MyMinfin Ready to use. According to the FPS Finance, available through registered software companies.
Documentation and testing Already tested and in production; public documentation for our own API. Documentation of the government APIs is limited here and there, so budget plenty of time for testing and trial and error.
Distribution and follow-up Automations, assignment, statuses, comments, audit trail, SSO. To be built yourself.
Integration with your software REST API, webhooks, official Make app. Completely free.
Maintenance We keep up with changes to the government APIs. Your team follows API changes, certificate renewals and outages itself.

What you need to build and maintain

  1. 1 DocConsumer onboarding and management of certificates and OAuth tokens per company.
  2. 2 Retrieving messages from every document provider in the provider registry.
  3. 3 Secure, encrypted storage of messages and attachments.
  4. 4 Duplicate detection (eBox and MyMinfin).
  5. 5 Rules to route messages to the right person or software.
  6. 6 User and access management, logging and monitoring.
  7. 7 Keeping up with changes to the government APIs.
  8. 8 Testing against the government APIs: their documentation is limited here and there, so budget plenty of time for trial and error.

Where building your own shines

  • Full control over data, logic and hosting.
  • No dependency on an external supplier.
  • Can match very specific internal processes perfectly.

Where Boxflow shines

  • Live within minutes instead of after a development project.
  • eBox Enterprise and MyMinfin, without having to be a registered software company.
  • Maintenance, security and penetration testing included.
  • REST API and webhooks to still add your own logic.

Our verdict

Building your own mainly pays off if you have a large development team and very specific needs. For most organisations, it is faster and cheaper to use Boxflow and add your own logic through our API or webhooks where needed.

Frequently asked questions

Can I build my own integration with eBox Enterprise?

Yes. eBox Enterprise offers a REST API for DocConsumers, documented on the eBox Enterprise website and on GitHub. You will need to handle onboarding, authentication, synchronisation, storage and maintenance yourself.

Can a company use the MyMinfin API itself?

According to the FPS Finance (via the ITAA), the MyMinfin API is available through registered software companies. Boxflow offers that integration out of the box.

Can I use Boxflow as the basis for my own integration?

Yes. Our webhooks notify you of every new message, and the REST API lets you retrieve its details and attachments.

Sources

Last verified on October 10, 2026.

Spotted an error or outdated information in this comparison? Let us know at hi@boxflow.be and we will correct it.