A signal that an action has been performed on the SEEK platform that may be of interest to an integration partner.Events can be delivered via:
- Webhook, using the
createWebhookSubscription
mutation - GraphQL polling, using the paginated
events
query
Fields
Name | Description |
---|---|
DateTime! | The date & time the event was created.This is commonly linked to the creation of an object that can be retrieved from the SEEK API.The data source for this field differs by event type and scheme.
This field has weak ordering guarantees, so it should not be used as a pagination argument. |
The identifier for the Event . | |
String! | The scheme ID of the event.Currently, only the seekAnz and seekAnzPublicTest schemes emit events. |
String! | The type of event.See Event implementations for a list of supported values. |
WebhookAttemptsConnection! | A page of webhook attempts for the current event matching the specified criteria.A maximum of 100 webhook attempts can be returned in a single page.
Additional webhook attempts can be queried using a pagination cursor.The result list is returned in ascending creation date & time order.
It starts from the earliest known attempt if no pagination arguments are provided. |
Implementations
Name | Description |
---|---|
The event signaling that a candidate has applied for a PositionOpening .A candidate may apply for the same position opening more than once.
Each application will trigger a new event with a distinct id . | |
The event signaling that a CandidateProfile has been purchased. | |
The event signaling that a hirer relationship has been added or removed. | |
The event signaling that a posted PositionProfile has been closed. | |
The event signaling that a PositionProfile has been posted. | |
The event signaling that a PositionProfile has been updated. |
Seen in
Parent name | Parent type | Description |
---|---|---|
Object | node field | |
Object | event field | |
Query | Result type |