Developer documentation

Webhooks

Meridian webhooks are a quick and simple way to get information about changes to your projects. Instead of pulling updates using the Meridian API, the webhook is triggered by specific events, instantly pushing a safe, one-way data share to your application.

For example, when your project budget is approved, the Budget_Approved webhook can send you the updated project data.

Event types

Webhooks are available for the following event types:

• Budget Status: BUDGET_APPROVED, BUDGET_REJECTED

• Project Status: PROJECT_APPROVED, PROJECT_REJECTED, PROJECT_CANCELED

• Task Updates: TASK_CREATED

Requirements

To receive notifications, you will need a public, secure URL (https://) hosted on your application that is configured to listen for and accept these incoming data payloads.

Create a webhook

To create a webhook, complete the following:

1. Log in to Meridian.

2. Open the Webhooks screen.
   (Administration / Webhooks)

3. Select Add a Webhook. 

4. Enter the following information:

   • Name: Enter a name for the webhook.

   • URL: Enter the HTTP endpoint where your events will be sent.

   • Authorization token: Enter your authorization token. If you do not have an authorization token, contact Support. 

5. Click Save. 

Payload example

When the event triggers, Meridian’s webhook sends the event data as a standard JSON object via an HTTP POST request.

Example: BUDGET_APPROVED

{

  "event_id": "evt_987654321",

  "event_type": "BUDGET_APPROVED",

  "timestamp": "2026-06-23T21:58:53Z",

  "data": {

    "project_id": "ABS-1122426",

    "project_name": "Q3 Infrastructure Upgrade",

    "requested_by": "Annie wood",

    "currency": "USD",

    "total_budget": 125000.00,

    "approval_status": "APPROVED",

    "approver_comments": "Budget matches adjusted quarterly targets. Approved for phase one."

  }

}

Retry & timeout

To ensure reliable data delivery, your endpoint must respond with an HTTP 200 OK status code within 5 seconds of receiving the payload. 

If the connection times out or returns an error code, Meridian will automatically attempt to redeliver the payload up to three times before marking the delivery as failed.

• Enabled sales self-service: Provided a standalone asset for Sales to give prospects, letting client business users easily validate the tech with their own developers.

• Eliminated alignment meetings: Created a definitive source of truth that answered product questions instantly, reducing meetings.

• Prevented support tickets: Allowed external developers to self-serve, keeping internal support teams from tracking down engineering answers.