REST API / Jobs

Get a job

The status of an async job. Coming soon: async jobs aren't available yet, so this route answers 404 for every id.

GET/v1/jobs/{id}MCP: none yet

Status

Not available yet

Costs

Nothing

Today

404 not_found

Path parameters

idstring

The job id. No job ids exist yet.

Response

Every call answers 404 with the error shape from Errors and retries. Nothing is counted.

Until async jobs ship run calls directly and split large runs across windows: page through searches with a cursor, verify up to 100 emails per call, and pace with GET /v1/usage. Async jobs and webhooks will be announced in the changelog.

Errors

Status	type	Meaning
`404`	`not_found`	Async jobs are not available yet.

Previous
← scrape_jobsNext
get_usage →

Was this page useful? Tell us

cURLTypeScriptPython

curl https://api.leadsets.ai/v1/jobs/job_7Qd2 \
  -H "Authorization: Bearer $LEADSETS_KEY"

import { Leadsets } from "@leadsetsai/sdk";

const ls = new Leadsets(process.env.LEADSETS_KEY);
// Throws NotFoundError (404) until async jobs ship.
const job = await ls.jobs.get("job_7Qd2");

import os
from leadsets import Leadsets

ls = Leadsets(os.environ["LEADSETS_KEY"])
# Raises NotFoundError (404) until async jobs ship.
job = ls.jobs.get("job_7Qd2")

Response404 Not Found

{
  "error": {
    "type": "not_found",
    "message": "Async jobs are not available yet. Split large runs across windows instead.",
    "charged": 0
  },
  "request_id": null
}