> ## 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.

# Adobe PDF Services Webhook Setup Guide

> Configure Adobe PDF Services to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](/connectors/adobepdfservices#getting-started) on the Adobe PDF Services connector page.

<section data-guide-section data-guide-scopes="">
  <h2>Webhook setup</h2>

  <p>This connector uses <strong>Manual Webhooks</strong>. Adobe PDF Services has no webhook subscription API or portal setting. Instead, each PDF Services job carries its own callback URL in the `notifiers` field of the job request, and Adobe calls that URL once when the job finishes or fails.</p>

  <Steps>
    <Step title="Copy the Native Webhook URL">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>In StackOne, open the <strong>Linked account</strong> for your Adobe PDF Services connection and copy the <strong>Native Webhook URL</strong>.</p>
      </div>
    </Step>

    <Step title="Add a CALLBACK notifier to each job">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>When submitting a job with any PDF Services action (for example Combine PDF, Create PDF, Export PDF, OCR, Compress, Protect, Split or Extract), pass a `notifiers` entry of type `CALLBACK` whose `data.url` is the Native Webhook URL. Only jobs submitted with this notifier are delivered to StackOne.</p>

        <ul>
          <li>Example notifier: `[{"type": "CALLBACK", "data": {"url": "<Native Webhook URL>"}}]`</li>
          <li>Adobe accepts HTTPS callback URLs only.</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Available webhook events</h2>

  <p>The following Adobe PDF Services events can be enabled. Only events selected in StackOne are delivered, and only for jobs submitted with the CALLBACK notifier described above.</p>

  <Steps>
    <Step title="Job events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events related to the lifecycle of PDF Services jobs.</p>

        <ul>
          <li><strong>Job Completed</strong> (`done`) — Fired when a PDF Services job finishes successfully. The payload includes the job ID and the output asset with its download URI.</li>
          <li><strong>Job Failed</strong> (`failed`) — Fired when a PDF Services job fails. The payload includes the job ID and the Adobe error code, message and status.</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Delivery format</h2>

  <p>Details of how Adobe PDF Services delivers events to StackOne.</p>

  <Steps>
    <Step title="One notification per job">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Adobe sends a single POST per job when it reaches a terminal state. The payload has no event timestamp, so the event date is the time StackOne received it. If 50 deliveries fail within 10 minutes, Adobe blocks webhook delivery for 20 minutes.</p>
      </div>
    </Step>
  </Steps>
</section>

## 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.