Skip to content
JobreachGet started

Send posts from your own agent

If you run your own AI agent that finds hiring posts, it can hand them straight to Jobreach instead of you pasting them. Each post becomes your lead, like one you paste: Jobreach reads it, checks the company, scores it against your own work, and for a strong or good match drafts the email and a one-page resume in your Gmail. You read them and press Send.

Updated

Make a key

  1. Open Profile, Your agent

    Sign in to Jobreach and press Make a key.

  2. Keep it secret

    The key starts with jri_ and is shown once. Give it to your agent as a secret.

  3. Turn it off if it leaks

    From the same place. Anything still using it is refused.

An agent can’t sign up or sign in for you, and the key can only send you posts and read its own status: it can’t read your resume, your emails or your Gmail, and it can’t send anything.

What to send

POST https://jobreach.app/api/intake/leads
Authorization: Bearer jri_...
Content-Type: application/json

{
  "leads": [
    {
      "text": "The whole post, to the end, including the poster's line and its age (\"3h\")",
      "url": "https://www.linkedin.com/posts/...",
      "age_label": "3h",
      "found_by": "posts: backend intern pune, past 24 hours",
      "found_at": "2026-10-24T09:15:00+05:30"
    }
  ]
}
  • text (required): the post exactly as shown, to the very end; pay terms are often in the last line. 40 to 40,000 characters.
  • url: the post’s link. The same link sent twice is one lead.
  • age_label: the age as shown on the post, like “45m”, “3h” or “2d”.
  • found_at: when the agent saw the post, in ISO 8601.
  • found_by: the search that found it, so you can see later which searches lead to replies.

Send only what the agent saw. Don’t extract email addresses, verify the company, write emails or create Gmail drafts: Jobreach does all of that, and writes only to an address the post or the company published.

The answer and the limits

{"received": 2, "queued": 1,
 "results": [{"job_id": "…", "status": "queued"}, {"job_id": "…", "status": "duplicate"}]}
  • duplicate: the same text or link is already one of your leads.
  • 401: the key is wrong or turned off. 422: a post is missing its text or is too short. 429: today’s limit is reached.
  • Up to 25 posts per call, 100 a day.
  • Queued posts appear on Add a post within a couple of minutes, marked Found by your agent; the good matches appear on Today with their emails.

A brief you can give your agent

For each hiring post you find, send it to Jobreach and do nothing else with it.
POST it to https://jobreach.app/api/intake/leads with the header Authorization: Bearer <key> and a JSON body
{"leads": [...]}, up to 25 posts per call. For each post send text (the whole post exactly as shown, to the end,
including the poster's line and the age line), url, age_label (the age as shown, like "3h"), found_at (when you saw
it, ISO 8601) and found_by (the search you ran). Do not extract emails, verify companies, write letters or create
Gmail drafts: Jobreach does that. A duplicate status means it already has the post. Keep the key secret.

For agents and their builders