Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Adobe PDF Services connector page.Webhook setup
This connector uses Manual Webhooks. 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.
Copy the Native Webhook URL
In StackOne, open the Linked account for your Adobe PDF Services connection and copy the Native Webhook URL.
Add a CALLBACK notifier to each job
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.
- Example notifier:
[{"type": "CALLBACK", "data": {"url": "<Native Webhook URL>"}}] - Adobe accepts HTTPS callback URLs only.
Available webhook events
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.
Job events
Events related to the lifecycle of PDF Services jobs.
- Job Completed (
done) — Fired when a PDF Services job finishes successfully. The payload includes the job ID and the output asset with its download URI. - Job Failed (
failed) — Fired when a PDF Services job fails. The payload includes the job ID and the Adobe error code, message and status.
Delivery format
Details of how Adobe PDF Services delivers events to StackOne.
One notification per job
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.