API reference

Pagination and cursors

Feeds (partner_jobs, partner_companies) page by change time with a cursor of since + after_id. Each page returns next; send it back unchanged to read the following page.

• Pages are ordered by (change time, id) and hold 1 to 1,000 records.
• A page only contains changes older than complete_until, so no write still in progress can land behind your cursor: replaying from a stored cursor after any failure never skips a record.
• has_more: false with an empty page means you are caught up. Cursors never expire; an old cursor returns the current state of everything changed since then.
• since: null replays everything (a full snapshot).
• company_search pages with page and page_size (up to 100 a page, 10,000 results). partner_job_ids pages by id with after_id (up to 20,000 a page).

cursor = load_cursor()                  # {"since": null, "after_id": 0} the first time
while True:
    page = post("partner_jobs", {**cursor, "page_size": 1000})
    for job in page["jobs"]:
        upsert(job) if job["active"] else hide(job["id"])
    commit()
    cursor = page["next"]; save_cursor(cursor)   # only after the page is committed
    if not page["has_more"]:
        break

Closures and tombstones

• Jobs are never hard-deleted. A job that closes, expires, is merged into a duplicate, is unpublished, or whose company is hidden is sent again with active: false and the reason (status, closed_at, expires_at, duplicate_of).
• Remove inactive jobs from search; do not delete jobs because a run timed out or returned few rows. A job can become active again.
• Companies carry hidden and merged_into. Jobs of a merged company move to the company it was merged into.

Reconciliation

Run a reconciliation now and then (for example daily) in addition to the change feed.

• Page through partner_job_ids until has_more is false.
• Anything you show that is not listed is no longer active: hide it.
• Anything listed that you lack, or hold with an older changed_at, should be read with partner_job.

Logo versions and caching

• Every logo address carries a version (v=). It changes whenever the logo people see changes: a new or replaced image, or a logo hidden or shown again.
• A logo change also counts as a change to the company and to its open jobs, so the feeds send them again with the new address, usually within seconds, and logo.changed webhooks fire.
• Replace the stored logo address every time a job or company arrives. A versioned address can be cached for a year (immutable).
• Without v= (or with an old one) the Logo API is cached for 5 minutes; ETag and X-Logo-Version carry the version and If-None-Match answers 304 while it is unchanged.

Webhooks: delivery, signing and retries

Add up to 5 webhooks per key under Account → API keys → Webhooks. Addresses must be https:// on a public network; redirects are not followed. About every 20 seconds (within seconds for logo changes) the worker posts what changed since the last delivery.

POST <your address>
X-Jobiwork-Event: companies.changed
X-Jobiwork-Delivery: whd_123
X-Jobiwork-Signature: t=1792570000,v1=<hex HMAC-SHA256 of "<t>.<raw body>" with your signing secret>

{"id": "whd_123", "event": "companies.changed", "created_at": "2026-10-14T12:40:05Z", "webhook_id": 7,
 "data": {"count": 2, "ids": ["JW-000123", "JW-000456"], "changed_from": "…", "changed_to": "…", "more": false}}

• ids are job ids for jobs.changed and company JW ids otherwise (at most 500; more: true means another delivery follows). Read the records with your key.
• logo.changed also lists each company's new address: "logos": [{"id": "JW-000123", "logo_url": "…&v=1792737567", "version_at": "…"}] (logo_url is null when the logo was hidden).
• Answer with any 2xx within 15 seconds. Anything else is retried after 1 min, 5 min, 30 min, 2 h, 6 h and 12 h. After 50 failures in a row the webhook is switched off.
• The signing secret (whsec_…) is shown once; make a new one from the same page. Check the timestamp to refuse replays.
• Deliveries are kept for 30 days and can be sent again from your account.

Alert events (listing.changed, company.activity) come from your watchlists and carry the events themselves: "data": {"count": 1, "events": [{"id": 90211, "type": "listing.suspended", "company": {...}, "security": {...}, "before": {...}, "after": {...}, "watchlists": [12]}]}, at most 100 events per delivery. A test alert has "test": true.

import crypto from "node:crypto";

// raw: the request body exactly as received (a string or Buffer), header: X-Jobiwork-Signature
export function verify(raw, header, secret, toleranceSeconds = 300) {
  const parts = Object.fromEntries(header.split(",").map((p) => p.split("=")));
  const t = Number(parts.t);
  if (!t || Math.abs(Date.now() / 1000 - t) > toleranceSeconds) return false;
  const expected = crypto.createHmac("sha256", secret).update(`${t}.${raw}`).digest("hex");
  return crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(parts.v1 ?? ""));
}

import hashlib, hmac, time

def verify(raw: bytes, header: str, secret: str, tolerance: int = 300) -> bool:
    parts = dict(p.split("=", 1) for p in header.split(","))
    t = int(parts.get("t", "0"))
    if abs(time.time() - t) > tolerance:
        return False
    expected = hmac.new(secret.encode(), f"{t}.".encode() + raw, hashlib.sha256).hexdigest()
    return hmac.compare_digest(expected, parts.get("v1", ""))

Where the data comes from

• Company records start in official company registers (India MCA, Australia ASIC, US SEC and state registers) and are refreshed weekly or monthly.
• Websites count as confirmed only after they are checked on the company's own site. Group structure comes from GLEIF (Legal Entity Identifiers) and Wikidata.
• Jobs come only from employers' own careers sites and the job systems they use; never from job aggregators. Show “via Jobiwork” and link apply_url.
• Company facts only: no directors, personal emails or phone numbers. contact.email is a company's role mailbox (info@, careers@ …) from its register filing, given only when its website is confirmed and the mailbox is on that domain. A register match is not a verified employer; employer_verified means the company confirmed its page with us.
• capital ranks compare paid-up capital among active Indian companies on the MCA register (1 = largest); paid-up capital is not revenue or headcount.

Changelog

Schema version 2. Fields are only added within a version; a breaking change gets a new version and advance notice.

1. 27 Oct 2026

   New company registrations (India)

   • new_companies: every company and LLP registered with MCA, in registration order with a no-skip cursor, filters for state, industry, class, paid-up capital and research status, and the research of each company.
   • Watchlists take the event type registration with a filter (states, industries, classes, capital_bands, min_capital); webhook event company.registered.
   • Plans carry a monthly allowance of new-company records.
2. 25 Oct 2026

   Listed-company alerts

   • Watchlists (alert_watchlists, alert_watchlist_create, alert_watchlist_update, alert_watchlist_delete) by company, ISIN / symbol or filter.
   • Events feed alert_events with the no-skip cursor; webhook events listing.changed and company.activity; alert_test.
   • Every NSE and BSE equity listing is now a company record (company.cin is empty until the MCA record is matched).
3. 24 Oct 2026

   Paid-up capital bands and ranks

   • Company records carry capital: band, rank in India, in the state and in the industry, and a percentile (Indian companies).
   • company_search takes capital_band, min_paidup_capital and sort=capital.
   • contact.email: a company's role mailbox, only when its website is confirmed and the mailbox is on it.
4. 23 Oct 2026

   Instant logo versions

   • Every logo address carries a version (v=); versioned addresses are cacheable for a year.
   • logo.changed webhooks list each company's new logo_url; ETag, X-Logo-Version and 304 on the Logo API.
5. 22 Oct 2026

   Feed contract, schema version 2

   • schema_version and complete_until in every feed page; replaying a stored cursor never skips a record.
   • New partner_job_ids for reconciliation.
6. 21 Oct 2026

   Webhooks and per-key datasets

   • Signed webhooks for jobs.changed, companies.changed and logo.changed, with retries.
   • Datasets can be set per key; key rotation.
7. 17 Oct 2026

   Company Data API and Logo API

   • company_lookup, company_enrich, company_search, company_group and api_account; publishable keys and the Logo API; plans.
8. 14 Oct 2026

   Jobs and companies feeds

   • partner_jobs, partner_job, partner_companies and partner_status.