This content provides an early look at an upcoming extension to the SEEK API. You may use it to scope integration effort, but the features described are not fully implemented and may be adjusted ahead of a production release.Check with your SEEK contact before starting any build work described here.
- Candidate or applicant list: in this context, the panel can be displayed in a drawer.
- Candidate details: in this context, the panel can be displayed in a tab, drawer or its own page.
HTML
Copy
<script
type="text/javascript"
src="https://integration.seek.com/panels/SeekApi.js"
></script>
SeekApi.render function renders an instance of the panel in the specified DOM element.JavaScript
Copy
SeekApi.render(containerNode, 'candidateProfile', props);
containerNode: The DOM element to render the panel into.'candidateProfile': The name of the panel to render.props: Props for rendering the panel.
Prop | Type | Description |
|---|---|---|
getAuthToken | () => Promise<string> | Function to call to retrieve the browser token to use when calling the SEEK API. |
candidate | object | The details of the candidate to view the profile of. This includes: email (string). |
hirerId | string | The SEEK hirer ID viewing the candidate profile. |
context | stringoptional | The context in which the candidate profile is being viewed. Supported values are APPLICANT_LIST and CANDIDATE_DATABASE. |
position | objectoptional | In the APPLICANT_LIST context, provide the details of the job the candidate is applying for. |
applicationStatus | objectoptional | In the APPLICANT_LIST context, provide the status of the candidate’s application. |
locale | stringoptional | Specifies the locale to display content in, e.g. en-AU. Supported locales are outlined in the content localisation documentation. |
- The panel loads and invokes the
getAuthTokenfunction passed to it. - Your frontend requests a browser token from your backend.The
getAuthTokenfunction should request a new token for the hirer ID inpositionProfile.positionOrganizations. If a user switches to a different SEEK hirer account, your software should re-render the panel with the new hirer ID inpositionProfile.positionOrganizations, and ensure that subsequent invocations ofgetAuthTokenwill request a token for the new hirer ID. - Your backend authenticates and authorizes the user.Your software is responsible for verifying that the user is authorized to access a given hirer ID. A user must not be able to request a browser token for an arbitrary organization that they do not belong to.
- Your backend requests a browser token from the SEEK API for the appropriate hirer ID and
query:seek-candidate-profilesscope. - Your backend responds with the browser token.
- Your frontend returns the browser token from the
getAuthTokenfunction. - The panel can now make requests to the GraphQL endpoint.
HTTP
Copy
POST https://graphql.seek.com/auth/token HTTP/2
Authorization: Bearer PARTNER_TOKEN_HERE
Content-Type: application/json
User-Agent: YourPartnerService/1.2.3
{"hirerId": "seekAnzPublicTest:organization:seek:93WyyF1h",
"scope": "query:seek-candidate-profiles",
"userId": "317665"
}