Skip to main content

Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Smartling connector page.

Smartling webhooks are configured automatically

StackOne provisions the Smartling webhook subscription for you when you connect your account. There is nothing to configure in Smartling — no URL to paste and no events to select manually.

  • On connect, StackOne creates a subscription named StackOne against your account and removes it when you disconnect.
  • Only the events you enable in StackOne are delivered.

Verify the subscription in Smartling

You can confirm the subscription was created from your Smartling dashboard, though no action is required.

  • Open the Account Settings menu in the top-right corner, then under Integrations click Webhooks.
  • You should see a subscription named StackOne, labeled Added by Stackone API, with status Enabled, subscribed to all supported events.

Available webhook events - Files

File lifecycle events for source and translated content.

  • File Uploaded (file.uploaded) — Fired when a source file is uploaded to a project.
  • File Published (file.published) — Fired when a file’s translations are published.
  • File Prepublished (file.prepublished) — Fired when a file’s translations are pre-published.
  • File Renamed (file.renamed) — Fired when a source file is renamed.
  • File Deleted (file.deleted) — Fired when a source file is deleted.

Available webhook events - Translation Jobs

Translation job lifecycle events.

  • Job Created (translationJob.created) — Fired when a translation job is created.
  • Job Updated (translationJob.updated) — Fired when a translation job is updated.
  • Job Completed (translationJob.completed) — Fired when a translation job is completed.
  • Job Canceled (translationJob.canceled) — Fired when a translation job is canceled.
  • Job Locale Workflow Step Reached (translationJob.localeWorkflowStep.reached) — Fired when the content for a job, locale, and workflow-step slice reaches a workflow step.

Available webhook events - Source Issues

Issues and comments raised against source strings.

  • Source Issue Created (sourceIssue.created) — Fired when a source issue is created.
  • Source Issue Updated (sourceIssue.updated) — Fired when a source issue is updated.
  • Source Issue Deleted (sourceIssue.deleted) — Fired when a source issue is deleted.
  • Source Issue Comment Created (sourceIssue.comment.created) — Fired when a comment is added to a source issue.
  • Source Issue Comment Updated (sourceIssue.comment.updated) — Fired when a source issue comment is updated.
  • Source Issue Comment Deleted (sourceIssue.comment.deleted) — Fired when a source issue comment is deleted.

Available webhook events - Translation Issues

Issues and comments raised against translations.

  • Translation Issue Created (translationIssue.created) — Fired when a translation issue is created.
  • Translation Issue Updated (translationIssue.updated) — Fired when a translation issue is updated.
  • Translation Issue Deleted (translationIssue.deleted) — Fired when a translation issue is deleted.
  • Translation Issue Comment Created (translationIssue.comment.created) — Fired when a comment is added to a translation issue.
  • Translation Issue Comment Updated (translationIssue.comment.updated) — Fired when a translation issue comment is updated.
  • Translation Issue Comment Deleted (translationIssue.comment.deleted) — Fired when a translation issue comment is deleted.

Available webhook events - Integrations

Integration platform events.

  • Integration Asset Exported (integrations.platform.asset.exported) — Fired when an integration asset is exported.

Delivery format

StackOne receives each Smartling event, normalizes it, and delivers it to your configured StackOne webhook endpoint.

  • Each event is delivered individually (Smartling does not batch multiple events into one request).
  • The normalized payload carries the event type, the affected record’s id, and the full original Smartling payload under the event data.
  • StackOne signs every delivery to your endpoint with an x-stackone-signature header.

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.