Webhooks let BeLazy notify another system when something happens to your opportunities, projects or quotes. Instead of asking the BeLazy API again and again whether there is anything new, your system, script or iPaaS scenario (Make.com, n8n, ActivePieces) receives a request the moment the event happens, and can react to it straight away. Think of webhooks like an email notification, but written for systems.
Typical uses are enriching a new opportunity with the Update Opportunity API, starting an AI step when a file is ready for processing, updating a JIRA ticket status when a project is created or closed, or informing a team channel when a vendor is assigned.
Setting up a webhook
Open Webhooks in the profile menu and create a new webhook subscription.
- Select connections. Optional. If you leave it empty, the webhook fires for events on all connections. Select one or more connections to limit it.
- Request settings. Give the webhook a name, choose the HTTP method (POST by default) and enter the URL that should receive the request.
- Request headers. Add any headers your endpoint needs, for example an authorization token, as key-value pairs. Click Add after each one.
- Select event types. Tick the events you want to be notified about. The icons next to each group select or clear all events in that group. The question mark next to an event explains when it fires, and the clipboard icon shows an example payload in the Preview panel.
- Click Confirm.
Tip: Use the Preview panel before you build anything on the receiving side. It shows exactly which fields you will get.
Event types
"Origin" always means the system the work came from in the Content and Project Hub: the vendor portal, the customer's TMS or the workspace. "TMS" in the opportunity and file events means your own TMS in the TMS Processing Hub, and "BMS" means your system in the Business Management Hub.
Opportunity events
- Ready opportunities: a new opportunity has arrived and is waiting for approval (it appeared under Approvals pending). This is the event to use for enriching opportunities with the Update Opportunity API.
- Opportunity dismissed: an opportunity was dismissed.
- Origin project details were transferred into TMS (preview): BeLazy created the project in your TMS.
Project events
- Pricing items delivered in Origin: part of a project, for example one language, was delivered back to the origin system.
- Project delivered in Origin: the whole project was delivered back to the origin system.
- Project dismissed: a project was dismissed.
- Project details transferred to BMS: BeLazy created or updated the project in your BMS.
- Linguist assigned in Origin: a linguist was assigned in the origin system.
- Vendors assigned in BMS: vendors were assigned to jobs in your BMS.
- Project closed in BMS: the project was closed in your BMS.
- Files from the origin system are ready for processing: the bilingual files of a project that arrived already prepared in the customer's TMS (From TMS) can be downloaded for an automated step.
- XLIFF exported from TMS: BeLazy exported the XLIFF files from your own TMS (Into TMS) at the start of a workflow step.
Quote events (preview)
- Quote dismissed: a quote request was dismissed.
- Quote details transferred to BMS: BeLazy created the quote in your BMS.
Events marked Preview are new. They work, but their payload may still change, so check the Preview panel again if you update your integration later.
The two file events are the starting points of the AI Hub workflows. See Extending TMS capabilities via the AI Hub APIs for the steps that follow them.
What the request contains
Each request contains the event type and the IDs your system needs to continue, such as the project ID, the BMS project ID and, for file events, the file IDs. The payload tells you what happened, not everything about the object. To get the full details, call the BeLazy API with the IDs from the payload, for example GET /opportunities/v1/{opportunityId} or the TMS file download endpoint. See BeLazy's API pages.