Seek
Connect Seek to post and manage job ads, review candidate applications and resumes, and write screening questions for your hirer.
You enter two values into PopMCP: a Client ID and Client secret from Client credentials in SEEK's Developer Dashboard. SEEK has to approve your business first. You then pick the hirer the connection acts for.
Partner application before this connector works
SEEK has no self-service API key. A business asks through SEEK's integration request form, which lists SEEK Customer as a platform type as well as recruitment software, and SEEK assesses each request individually before opening the Developer Dashboard and approving live credentials.
- Typical wait
- SEEK says it will try to confirm the outcome of a request within 10 business days. Approval for live credentials comes later, once SEEK sees progress through its integration process.
- Cost
- The form and API terms state no fee for API access. Job ads posted through the API are real SEEK ads, charged under the hirer's own SEEK arrangement.
- Blocked until approved
- Connecting at all. Without SEEK's approval there is no client ID and secret. SEEK's support team also sets up each hirer relationship, which decides which features work.
- Works meanwhile
- Nothing on the live API. Once you have Dashboard access, Playground credentials give read-only mock data for trying the tools.
Where to apply: Send the form at https://au.employer.seek.com/partners/integration-request/ with your business details and the SEEK solutions you need, or ask your SEEK Partner Manager. You must accept the SEEK API Terms of Use.
- To post job ads you must also adopt an apply solution: SEEK requires one alongside job posting.
- SEEK may ask to review your integration against a test plan before you release it.
- SEEK's terms limit what you may do with candidate data and forbid sub-licensing the API. Read them before connecting.
- Setup time
- 5 min, after SEEK approves your business
- Auth
- API credentials
- API base URL
- https://graphql.seek.com/graphql
- Rate limits
- SEEK limits each query and mutation separately. Most limits are unpublished. It also rejects any request over a query complexity limit, which depends on the size of the expected answer.
Before you begin
- SEEK's approval for API access. Send the integration request form at au.employer.seek.com/partners/integration-request, or ask your SEEK Partner Manager
- An admin login to SEEK's Developer Dashboard, which SEEK sets up for a contact you nominate
- At least one hirer relationship, which SEEK's support team sets up. It decides which features work, such as job posting and application export
Get your credentials
Ask SEEK for API access
If you do not have a Developer Dashboard login yet, send SEEK's integration request form. Choose the Platform type that fits, such as SEEK Customer or ATS, and say which SEEK solutions you need. To post job ads you must also adopt an apply solution. SEEK assesses each request individually and says it will try to reply within 10 business days. If you already have a Partner Manager, ask them instead.
Integration Request for Partners
- Platform type
- SEEK Customer
- SEEK solutions
- SEEK Job Posting & SEEK Optimised Apply
Open Client credentials
When SEEK has set up your access, you get a welcome email for the Developer Dashboard. Sign in and open Client credentials under Auth in the left sidebar. If SEEK has not approved live credentials yet, you may only be able to make Playground ones, which work with mock data.
Client credentials
No credentials found.
No credentials found.
Create a set of live credentials
Click New under Live credentials, enter a name such as PopMCP, and click Create. You can have two live sets at a time, so if you already have two, delete one that nothing uses first.
Client credentials
Copy the Client ID and Client secret
Copy both values now. SEEK will not show the secret again after you close this dialog. If you lose it, make a new set.
Client credentials
Connect in PopMCP and pick your hirer
In PopMCP, open Seek, paste the Client ID and Client secret, and continue. PopMCP lists the hirers linked to these credentials. Pick the one this connection should act for. To see what each hirer has switched on, open Hirer relationships in the dashboard.
Hirer relationships
| Name | API Relationships | Application Methods |
|---|---|---|
| Acme Pty Ltd | Application Export, Job Posting | SEEK's Apply Form |
Connect in PopMCP
Open your workspace, choose Seek in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Client IDtext | SEEK Developer Dashboard, Credentials page. |
| Client secretsecret | Shown with the client ID. Stored encrypted and used only on PopMCP's server.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Seek immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP marks the Seek connection Verified with your hirer's name, records your partner name and which SEEK features the hirer has, and says so if the credentials are Playground ones. Asking the AI which job ads are open returns your position openings.
Troubleshooting
SEEK did not accept this client ID and secret
Why:
Fix: Check both values under Client credentials. The secret shows only once, so if it is lost, make a new set and use that.
SEEK has not linked any hirer to these credentials yet
Why:
Fix: A hirer relationship is set up by SEEK's support team. Ask them, or your Partner Manager, to add it, then connect again.
A tool answers that SEEK refused it (FORBIDDEN)
Why:
Fix: The hirer does not have the relationship for that feature, or it has been disabled. Check Hirer relationships in the dashboard and ask SEEK to add what is missing.
Writes are refused even though write actions are on
Why:
Fix: These are probably Playground credentials. SEEK checks a write's input in the Playground and then refuses it. Make live credentials and connect again.
A job ad I posted does not appear yet
Why:
Fix: Posting runs in the background and usually takes under a minute. A failed post shows up as a PositionNotPosted event.