> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lara Translate Webhook Setup Guide

> Configure Lara Translate to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](https://docs.stackone.com/connectors/laratranslate.md#getting-started) on the Lara Translate connector page.

## Webhook setup

This connector uses **Manual Webhooks**. Lara Translate has no webhook subscription API or portal setting. Instead, each async job carries its own `callback_url`, and Lara Translate calls that URL once the job finishes.

**1. Copy the Native Webhook URL**

In StackOne, open the **Linked account** for your Lara Translate connection and copy the **Native Webhook URL**. Keep it private, as the URL includes a delivery token.

**2. Add the callback URL to each job**

When starting a job with one of the actions below, set `callback_url` to the Native Webhook URL. Only jobs started with this callback URL are delivered to StackOne.

<ul>
  <li>Import TMX into Translation Memory — delivered as Memory Import Completed</li>
  <li>Export Translation Memory (Async) — delivered as Memory Export Ready</li>
  <li>Export Glossary (Async) — delivered as Glossary Export Ready</li>
  <li>Do not set the callback URL on Import CSV into Glossary. Its callback has the same body as a memory import callback and would be delivered as Memory Import Completed.</li>
</ul>

## Available webhook events

The following Lara Translate events can be enabled. Only events selected in StackOne are delivered, and only for jobs started with the callback URL described above.

**1. Translation memory events**

Events related to translation memory import and export jobs.

<ul>
  <li>**Memory Import Completed** (`memory.import_completed`) — Fired when a TMX import finishes. The payload includes the import job ID and its progress.</li>
  <li>**Memory Export Ready** (`memory.export_ready`) — Fired when an async memory export is ready to download. The payload includes the export job ID and the download URL.</li>
</ul>

**2. Glossary events**

Events related to glossary export jobs. Glossaries require a Lara Translate plan with glossary access.

<ul>
  <li>**Glossary Export Ready** (`glossary.export_ready`) — Fired when an async glossary export is ready to download. The payload includes the export job ID and the download URL.</li>
</ul>

## Delivery format

Details of how Lara Translate delivers events to StackOne.

**1. One callback per job**

Lara Translate sends a POST when a job finishes and may retry it. Repeated deliveries of the same job carry the same event ID, the job ID. The payload has no event timestamp, so the event date is the time StackOne received it.

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.