Two ways to take applications

1. Claim your addressSettings, under Pipeline: type the name you want, such as acme, and save. The page is live at https://app.interviewwatch.com/careers/acme immediately. Addresses are lowercase letters, numbers and hyphens, three to forty characters, and a handful of words are reserved so a page can never collide with a product route. If the name you want is taken you are told to pick another, and you are never told who holds it.
2. Choose what the form asksName, email and a resume are always collected, so a page can never be configured into collecting nobody. Everything else is yours: in the same settings screen, tick Ask on careers page against any application field, tick Required if an answer is compulsory, and move questions up or down into the order you want them asked. See form fields below.
3. Share the linkPut it in your job posts, your email signature and your LinkedIn page. Every submission creates a pipeline card in Applied with the resume attached and indexed for search, marked as having arrived from your careers page.

1. Mint an apply keyOn the Pipeline screen, issue a company apply key. It looks like iwk_1a2b3c4d… and is shown once, because only its hash is stored. Put it in your server environment as INTERVIEWWATCH_APPLY_KEY.
2. Read your job idsCall GET /api/careers/jobs and build your listings from the result, so a closed role never leaves a dead form behind.
3. Post each applicant from your backendOne request per submission carrying jobId, name and email, plus whatever else your form asks. Send it as multipart and the resume comes along in the same call.

The request

curl -X POST https://app.interviewwatch.com/api/careers/applications \
  -H "Authorization: Bearer $INTERVIEWWATCH_APPLY_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jobId":"3f1c…","name":"Ada Lovelace","email":"[email protected]"}'

The response

// 201 Created on a new application, 200 OK if they already had a card for this job
{
  "applicationId": "a41d…",
  "candidateId":   "9b02…",
  "jobId":         "3f1c…",
  "stage":         "Applied",
  "source":        "CareersApi",
  "created":       true,
  "active":        true
}

Repeat submissions are safe: the same person and job returns 200 with created: false rather than a second card. Treat both as success in your UI.

The full integration guide has working examples for Next.js, PHP and WordPress, every endpoint and status code, resume upload as multipart, custom fields, and how to rotate a key.

The hosted page is capped harder on purpose. Its address is public and cannot be rotated the way a leaked key can, so the per-page and per-visitor ceilings are what stand between a public apply form and somebody filling your board. The address authorizes creating an application and attaching its resume, and nothing else: it cannot read your pipeline, list your candidates or run a bulk import.