A requirement in rinkats is private until you say otherwise. Three flags on the requirement page decide what the outside world sees, and the same three flags drive the jobs API, so your own website can list roles without anyone copying text between systems.
The three flags
Public. When it is on, the requirement is returned by GET /api/v1/recruiter/jobs. When it is off, the role exists only for your team and any agent working inside your workspace.
Show company. When it is on, the client's name travels with the posting. When it is off, the client's industry stands in for the name everywhere the role is shown, including the API. Use this for confidential searches.
Featured. Featured roles sort first and can be filtered with featured=true. It is a hint for your homepage, nothing more.
Reading roles from your site
Create an API key under Account → API keys and call the jobs endpoint from your server (never from the browser, where the key would be visible):
GET https://www.rinkats.com/api/v1/recruiter/jobs?featured=true
Authorization: Bearer rk_p_…
The response is a page of roles with title, company (or null when the company is hidden), industry, location, workMode and skills. Salary is returned only to callers whose role may see it. Page through with nextCursor.
Taking applications
Post the candidate's name and email with the job id to POST /api/v1/recruiter/applications. The application appears at the first stage of that requirement's pipeline, in the same board your recruiters already use. A resume upload for this endpoint is on the roadmap; until then, candidates can attach their resume on the hosted application page, or your team can attach it from the candidate's profile.
Where to look next
The full request and response shapes are in the API reference, and the same capability is available to agents through the MCP server.