In Self host method webhook and API token

[Nishal07]

Hi OpenSign Team,

I am currently evaluating OpenSign for integration into our CRM platform and plan to self-host OpenSign as a completely separate service.

Our planned architecture is:

CRM (proprietary application)
→ REST API
→ Self-hosted OpenSign
→ MongoDB

While testing the self-hosted version locally, I noticed that the OpenSign Cloud UI shows API Token and Webhook settings, but I could not find these options in the self-hosted/open-source version.

I have a few questions:

Are API Tokens and Webhooks available in the self-hosted open-source version?
If not, is it expected that developers implement these features themselves by extending the OpenSign source code?
Is there any recommended approach for machine-to-machine authentication when integrating a self-hosted OpenSign instance with another application?
For production use, do we need to provide our own signing certificate (PFX/P12) in order to generate legally valid signed PDFs?

If we add custom functionality such as:

API Token support
Webhook events (document completed, signed, declined, etc.)
Additional integration endpoints

would this create any AGPL-3.0 licensing concerns for a deployment where OpenSign is hosted as a separate service and consumed via REST APIs from our CRM?

We are trying to understand the recommended way to build a production-grade integration while remaining compliant with the AGPL license.

Thank you for your help.