Overview
Job Listing Webhooks let your system receive a real-time HTTPS POST from Double Nickel whenever a job listing is created, edited, or closed — so your careers site, internal recruiting tool, or TMS stays in sync with Double Nickel without anyone copying pay, requirements, or benefits changes by hand.
Each delivery includes a full snapshot of the listing before and after the change, plus a list of exactly which fields changed. You do not need to call back into Double Nickel to see what's new.
Event types
There is currently exactly one job listing webhook event type:
Event type |
| Fires when |
Job Listing Updated |
| A new job listing is created |
| Any customer-facing field on an existing listing changes (including its status) |
There is no separate "closed" event. To act only on closures (or any other change), subscribe to this event and filter on the payload — see "Filtering for the changes you care about" below.
When deliveries fire
Listing creation (
eventTypeisjob_listing.createdandpreviousisnull).Any change to a customer-facing field — for example pay moving from $1,300/week to $1,400/week, a new endorsement requirement, an updated description, or added benefits.
Status changes, including deactivating a listing (
INACTIVE) and deleting it (ARCHIVED).
Three things to keep in mind:
Every active Job Listing Updated webhook configured for your company receives every listing change — there is no per-field or per-listing filtering on the Double Nickel side. Filter in your endpoint.
Internal-only updates (such as recruiter round-robin assignment) do not trigger a delivery.
Changes to a listing's address only do not trigger a delivery today. The current address is always included in the payload whenever another change fires.
Configuring webhooks
Log in to your Double Nickel dashboard.
Navigate to Settings → Integrations → Webhooks.
Click Add Webhook, select Job Listing Updated as the event type, and provide your endpoint URL (must be HTTPS), an authentication type, and any optional custom headers.
Click Activate.
Each webhook subscribes to a single event type. To receive both applicant status changes and job listing changes, create two webhooks — ideally pointing at separate endpoints.
There is no built-in test-send option today — to verify connectivity, edit a job listing (for example, update its description) and confirm your endpoint receives the live notification. Partner sandboxes can do this safely in the Test environment (dashboard-test.getdoublenickel.com).
Delivery authentication
Job Listing Webhooks use the same authentication options as Applicant Status Webhooks — no authentication (with optional static custom headers) or OAuth 2.0 client credentials. See Applicant Status Webhooks → Delivery authentication for the full OAuth 2.0 flow details.
All webhook destinations must use HTTPS (TLS 1.2+). Stored tokens and secrets are encrypted at rest and masked in logs.
Example notification payload
{
"eventId": "9f2c7a41d0b84e6fa3c15e82b7d04a19",
"eventType": "job_listing.updated",
"timestamp": "2026-09-26T15:12:22.145Z",
"companyId": "3f9a1c2e-7b4d-4e8a-9c1f-2d6b8e0a4c73",
"jobListing": {
"jobListingId": "5b8e2d14-6c3a-4f97-8e21-7d0c9a4b3f62"
},
"data": {
"jobListing": {
"jobListingId": "5b8e2d14-6c3a-4f97-8e21-7d0c9a4b3f62",
"address": {
"street": null,
"city": "Dallas",
"state": "TX",
"zipCode": "75201",
"country": "USA"
}
},
"change": {
"previous": {
"jobListingId": "5b8e2d14-6c3a-4f97-8e21-7d0c9a4b3f62",
"status": "ACTIVE",
"title": "OTR Class A Driver",
"subtitle": "Home weekly",
"type": "DRIVER",
"description": "Long-haul routes across the Southeast...",
"benefits": ["Health", "401k"],
"payMin": 1300,
"payMax": 1300,
"payUnit": "WEEKLY",
"payCurrency": "USD",
"employmentType": "FULL_TIME",
"licenseClass": ["A"],
"endorsements": ["N"],
"minMonthsExperience": 12,
"minEmploymentHistoryYears": 3,
"numberOfHires": 5,
"hiringTimeline": "IMMEDIATE",
"jobPostingDate": "2026-09-01T00:00:00.000Z",
"createdAt": "2026-09-01T14:03:10.221Z",
"updatedAt": "2026-09-10T09:41:55.012Z"
},
"current": {
"...": "same fields as previous, with the new values",
"payMin": 1400,
"payMax": 1400,
"updatedAt": "2026-09-26T15:12:18.431Z"
},
"changedFields": ["payMin", "payMax"],
"changedAt": "2026-09-26T15:12:22.145Z"
}
},
"metadata": {
"environment": "production",
"version": "1.0.0"
}
}What the payload contains — and what it doesn't. The payload includes every customer-facing field on the listing, before and after the change. It does not include internal assignment details (recruiters, round-robin tracking), applicants, or tracking links.
Field reference
Field | Type | Values |
| String |
|
| String | Free text ( |
| String |
|
| Array of strings | Free text |
| Number | Pay amount in |
| String |
|
| String | ISO currency code (defaults to |
| String |
|
| Array of strings |
|
| Array of strings |
|
| Number | Or |
| Number | Or |
| String |
|
| String | ISO 8601 timestamp in UTC |
Treat any field as optional rather than assuming a fixed schema — new fields may be added over time, and previous is null for newly created listings.
Filtering for the changes you care about
Pay changes:
data.change.changedFieldsincludes"payMin","payMax", or"payUnit"Listing closed:
changedFieldsincludes"status"anddata.change.current.statusis"INACTIVE"or"ARCHIVED"Listing reopened:
changedFieldsincludes"status"andcurrent.status === "ACTIVE"New listings only:
eventType === "job_listing.created"
Deduplication and ordering
eventIduniquely identifies a single change to a listing and is identical across retries of that change. Store processedeventIdvalues and skip any you have already seen — this protects you from duplicate processing if a delivery is retried after a timeout.Deliveries are sent independently and can arrive out of order (for example, when a retry lands after a newer change). Compare
data.change.current.updatedAtagainst the last value you stored for thatjobListingIdand ignore anything older.
Responding, timeouts & retries
Your endpoint should return an HTTP 2xx status code as quickly as possible — acknowledge first, then do heavy processing asynchronously.
Condition | System action |
2xx response within the timeout | Event marked Delivered |
Non-2xx response | Event retried |
No response within the timeout (5 seconds per attempt by default) | Event retried |
All retries failed | Event marked Failed and logged |
Failed deliveries are retried up to 3 times with exponential backoff (4 total attempts). Every attempt is logged internally with the response status, body, and timing — if a delivery does not arrive, contact support and we can pull the delivery log for your endpoint.
Using no-code tools (Zapier, Make, etc.)
Job Listing Webhooks work with catch-hook triggers such as Webhooks by Zapier → Catch Hook: paste the hook URL as your endpoint, choose None for authentication, then edit a job listing once so the tool can capture a sample. Nested fields are available for mapping (for example data__change__current__payMin), and you can add a filter step on changedFields to act only on the changes you care about.
Questions or need help?
For authentication and the REST endpoints, see Getting Started and the API & Webhooks FAQ.
Contact the Double Nickel support team at [email protected].
