exports.list_applications

Export a board as spreadsheet rows

Request

GET/api/v1/boards/{boardId}/export

Scope required

applications:read

Effect

Reads only. Safe to retry and safe for an agent to call unprompted.

Acts on

Serves an account’s own data and, where shared, an organization’s.

MCP tool

exports_list_applications

Environment

Live and sandbox alike.

Request body

JSON.

Downloads

Also answers text/csv as a file. Ask for one or the other with the format parameter, or with an Accept header. An MCP tool call always receives the JSON shape.

What it does

Returns every application on a board flattened into the same columns the web app's CSV export writes, with every value already rendered as text. A column no application on the board has a value for is left out of every row, so read the keys from the rows rather than assuming a fixed set. Ask for `?format=csv`, or send `Accept: text/csv`, and the same rows come back as a downloadable CSV file instead of JSON. Use `table.list_rows` instead when you want typed values and public ids to write back with; this is for handing a board to something that eats spreadsheets. Staff of an organization the board is shared with may export it, and get exactly the columns the share exposes — the applicant’s résumé is never one of them. A board is exported whole rather than in pages — an export split across requests is not one file — so `hasMore` is always false and `nextCursor` always null.

Parameters

Response

data

array of object, required

hasMore

boolean, required

nextCursor

string or null, required

Examples

curl -s https://www.jobapplicationtracking.com/api/v1/boards/brd_7/export \
  -H "Authorization: Bearer $JAT_KEY"

{
  "data": [
    {
      "job_title": "Staff Engineer",
      "company_name": "Acme",
      "status": "Applied"
    }
  ],
  "hasMore": false,
  "nextCursor": null
}

Related operations