Contract management

In this section, we will address several requests to control pre-existing contracts, a.k.a. business requests.

Webhook Notifications

Webhook notifications enable external systems to receive real-time updates whenever specific events occur within the Digital Certification (E-Contracting) platform.

Once a webhook subscription is configured, the platform automatically sends an HTTP POST request to the subscribed endpoint whenever the selected event is triggered (for example, when a contract or business request changes status).

This mechanism allows seamless integration with third-party systems for automation, monitoring, and downstream processing.

Supported Use Cases

Webhooks can be used to :

• Track contract lifecycle changes (creation, approval, signing, or counter signing).

• Synchronize contract status with external systems.

• Trigger automated workflows based on contract events.

• Maintain real-time audit and monitoring dashboards.

Webhook Subscriptions

A webhook subscription defines:

1. Event to listen to – e.g., App.BusinessRequestStatusChange

2. Endpoint for notification delivery – the URL where POST requests will be sent

Key Points:

• Subscriptions are event-specific and endpoint-specific.

• Multiple subscriptions can be created for the same event, each targeting a different endpoint.

How to Create a Webhook Subscription

1. Navigate to Webhook Subscriptions in the portal.

2. Click “Add New Webhook Subscription”.

3. Fill in the required fields:

   • Webhook Endpoint* — The URL that will receive the POST notifications.

   • Webhook Events* — Select the event(s) to subscribe to (e.g., App.BusinessRequestStatusChange).

4. Click Save.

Webhook Payload Example

Whenever an event occurs, the webhook sends a payload like the following:

{
  "Id": "2b020a26-ec12-4f59-8e6a-7d4bf941372b",
  "WebhookEvent": "App.BusinessRequestStatusChange",
  "Attempt": 1,
  "Data": {
    "Id": "c2f27bd2-bb49-4dde-bb5f-22a6b8e0d20d",
    "NewStatus": "PendingApproval"
  },
  "CreationTimeUtc": "2025-12-11T11:27:18.6197007Z"
}

Payload details:

• WebhookEvent: Name of the triggered event

• Attempt: Delivery attempt number

• Data: Event-specific information (e.g., contract ID, new status)

• CreationTimeUtc: Time the event occurred (UTC)

Webhook Logs

Each webhook call is logged and includes:

• HTTP Method (POST)

• Source IP Address

• Timestamp of the request

• Request Headers

• Request Body

Screenshots for the “Add New Webhook Subscription” flow.