GET /api/v1/x/jobs/{id}

Jobs

Changed on Oct 20, 2026

Returns a public job listing with its description as text & Markdown, work type, seniority, salary, company & apply link. A job that closed returns job_not_found & is free.

get/api/v1/x/jobs/{id}

Request

Base URL: https://xquik.com
URL: https://xquik.com/api/v1/x/jobs/{id}
Auth: one of:
- API key in header x-api-key
- HTTP bearer
- none

Path parameters

idstring required

Job ID or URL-encoded job URL, such as x.com/i/jobs/123. Anything else gets 400 invalid_job_id.

Query parameters

fieldsstring

Example:id,text,author.username

Fields to keep in each row, comma-separated. Use dots for nested fields, such as author.username. A list keeps the field in each item. Case & underscores do not matter. A row that lacks a field leaves it out. Cursors, counts & diagnostics always stay. An unknown name answers 400 unknown_field with the valid names, before any read. The price stays the same. SDK row types then hold only the named fields. A longer URL fails at the edge before Xquik reads it.

omitstring

Example:entities,media

Fields to drop from each row, comma-separated. It takes the same names as fields. With fields, it drops from the kept fields. A longer URL fails at the edge before Xquik reads it.

Response

Job listing

Example response

{
  "job": {
    "id": "1899202395210649861",
    "title": "Engineer",
    "url": "https://x.com/i/jobs/1899202395210649861",
    "applyUrl": "https://commonware.xyz/hiring.html?utm_source=la37oZNq55&ashby_jid=d34716f5-0515-42f8-849a-c8fbac36c488",
    "location": "United States",
    "locationType": "remote",
    "employmentType": "full_time",
    "seniorityLevel": "lead",
    "jobFunction": "software_engineering",
    "formattedSalary": "Starting at $225K",
    "salaryMin": 225000,
    "salaryCurrencyCode": "USD",
    "salaryInterval": "annually",
    "featured": true,
    "shortDescription": "Commonware is hiring for founding engineers that can help us expand the Commonware Library to a broader set of applications and deploy cloud-based components to augment it.",
    "description": "What is Commonware?\n\nToday's blockchain stack is designed to be a jack of all trades, but master of none. Modeled after virtual machines (VM) and kernels, it exposes a monolithic interface through a one-size-fits-all framework instead of molding to the needs of any specific application.\nAt Commonware, we believe that the most popular onchain experiences of the next decade will develop a sustained edge through vertical integration. To accelerate developers that share this perspective, we are building a library of open (MIT/Apache-2) primitives meant to be remixed and modded.\nStreaming unstructured data over globally distributed infrastructure",
    "descriptionMarkdown": "# What is Commonware?\n\nToday’s blockchain stack is designed to be a jack of all trades, but master of none. Modeled after virtual machines (VM) and kernels, it exposes a monolithic interface through a one-size-fits-all framework instead of molding to the needs of any specific application.\n\nAt Commonware, we believe that the most popular onchain experiences of the next decade will develop a sustained edge through vertical integration. To accelerate developers that share this perspective, we are building a [library of open (MIT/Apache-2) primitives](https://github.com/commonwarexyz/monorepo) meant to be remixed and modded.\n\n- Streaming unstructured data over globally distributed infrastructure",
    "account": {
      "id": "1812126202804711425",
      "username": "commonwarexyz",
      "name": "commonware",
      "verified": true,
      "verifiedType": "Business",
      "profilePicture": "https://pbs.twimg.com/profile_images/1812494863784378368/1Iqip1ir_normal.jpg",
      "profileImageShape": "Square"
    }
  }
}

Changes

Oct 20, 202645942c75fdc2 Revision changes
- warning
  added the new topup_in_progress enum value to the ///// response property for the response status
- warning
  added the new topup_in_progress enum value to the ////// response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the / response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the // response property for the response status
- warning
  added the new topup_in_progress enum value to the ////// response property for the response status
- warning
  added the new topup_in_progress enum value to the /////// response property for the response status
- warning
  added the new topup_in_progress enum value to the ////// response property for the response status
- warning
  added the new topup_in_progress enum value to the /////// response property for the response status

Operation history