Developer platform

Interact with your product data

The same live records behind your portal and your PDFs, two ways: a REST API for your code, and an MCP server for AI assistants such as Claude, Cursor or Copilot. Both are read-only and versioned, and a key sees no further than its tier.

v1OpenAPI 3.1 specManage API keys →

For your code

REST API

Your website, your ERP or your quoting tool reads the catalog as JSON: filtered, sorted and paged, with a unit on every number.

GETa request your code sends
curl "https://app.speclatch.com/api/v1/records?tableId=tbl_hc&min.bep_flow=250&sort=-bep_flow&specs=bep_flow,bep_head" \ -H "Authorization: Bearer $SPECLATCH_API_KEY"

2002 records, largest flow first

{ "records": [
  { "modelNumber": "HC-4X3-10-17-CI", "status": "PUBLISHED",
    "specs": [
      { "field": "bep_flow", "value": 330, "unit": "GPM", … },
      { "field": "bep_head", "value": 84.8, "unit": "ft", … }
    ] },  { "modelNumber": "HC-4X3-8-17-CI", "status": "PUBLISHED",
    "specs": [
      { "field": "bep_flow", "value": 260, "unit": "GPM", … },
      { "field": "bep_head", "value": 57.7, "unit": "ft", … }
    ] }  ],
  "page": { "total": 2, "next": null } }
  • Filter and sort by any field key
  • Look a record up by model number or SKU
  • Fetch only what changed since a date
  • An ETag on every response: 304 when nothing changed

Start with the overview ↓This endpoint ↓OpenAPI 3.1 spec

For your assistant

AI assistants MCP

Claude, Cursor or Copilot answers from the same records, with the same key. One address, one step, and nothing to export first.

in a terminal

claude mcp add --transport http speclatch https://app.speclatch.com/api/mcp \
  --header "Authorization: Bearer $SPECLATCH_API_KEY"

Claude, Cursor and Visual Studio Code are trademarks of their respective owners. SpecLatch is not affiliated with them.

Then ask. Connected with a public key:

Which close-coupled pumps deliver at least 250 GPM, and at what head?

search_recordsmin.bep_flow = 2502 records

Two published pumps deliver 250 GPM or more, both at 1,750 RPM:

  • HC 4x3-10: 330 GPM at 84.8 ft
  • HC 4x3-8: 260 GPM at 57.7 ft

How assistants connect ↓A whole session, replayed →

Overview

The SpecLatch Read API is a read-only, versioned HTTP API over your organization's tables and records. It serves the same live data that powers your public portal and generated PDFs. Point your website, dealer portal, or quoting tool at it and retire the exported copy.

Every path lives under https://app.speclatch.com/api/v1 and returns JSON (downloads return the file itself). Breaking changes only ever arrive in a new version prefix, so integrations against /api/v1 keep working.

The API sends CORS headers, so browser-side calls work. A key embedded in client code, though, is visible to anyone who opens the page. For public websites, call the API from your server or edge layer and keep the key a secret.

Overview
curl "https://app.speclatch.com/api/v1/tables" \
  -H "Authorization: Bearer $SPECLATCH_API_KEY"

A first call: list the tables your key can see.

Authentication

Every request carries an organization-scoped API key as a bearer token. Keys start with slk_ and are shown once, at creation. Store them like any other secret. The Read API comes with the Growth plan and up (pricing); how many keys a workspace can mint follows its plan.

Each key has a visibility scope (public, internal or confidential), and that scope is the most the key can ever see. A PUBLIC-scoped key receives only published records and public fields and documents: issue one of those for anything customer-facing, and keep fuller-scoped keys for internal tooling.

Workspace admins create and revoke keys under Settings → API keys. Revocation is immediate.

Authentication
curl "https://app.speclatch.com/api/v1/records" \
  -H "Authorization: Bearer slk_your_key_here"

AI assistants (MCP)

SpecLatch is also a Model Context Protocol server at https://app.speclatch.com/api/mcp, so Claude, Copilot, Cursor or any MCP client can answer questions from your own catalog without you exporting anything: "which models deliver at least 5 HP in a TEFC enclosure?", or "draft a description for EXM20 from its specs". It is read-only, and it sees exactly what the API key you give it sees: a PUBLIC-scoped key, published records and public fields only.

The tools map one-to-one onto this API: list_tables, describe_table, search_records, get_record and list_tags. An assistant discovers your fields, units and choices through describe_table, then filters with the same operators documented above. Every tool call is one API request and draws on the same rate limit.

Authentication is the API key as a bearer token (Streamable HTTP transport, stateless). Clients that let you set a header connect in one line; a sign-in flow for assistants that cannot (claude.ai and ChatGPT connectors) is planned.

AI assistants (MCP)
# Claude Code (in a terminal)
claude mcp add --transport http speclatch https://app.speclatch.com/api/mcp \
  --header "Authorization: Bearer $SPECLATCH_API_KEY"

# Cursor (.cursor/mcp.json)
{
  "mcpServers": {
    "speclatch": {
      "url": "https://app.speclatch.com/api/mcp",
      "headers": { "Authorization": "Bearer slk_your_key_here" }
    }
  }
}

# VS Code (.vscode/mcp.json)
{
  "servers": {
    "speclatch": {
      "type": "http",
      "url": "https://app.speclatch.com/api/mcp",
      "headers": { "Authorization": "Bearer slk_your_key_here" }
    }
  }
}

# Claude Desktop (claude_desktop_config.json, through mcp-remote)
{
  "mcpServers": {
    "speclatch": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.speclatch.com/api/mcp",
        "--header", "Authorization: Bearer slk_your_key_here"]
    }
  }
}

Four clients, one URL. Use a PUBLIC-scoped key for anything that leaves your team.

List tables

GET/api/v1/tables

Every table visible to the key, with its published-record count. The natural first call for discovering an organization's catalog structure.

Request

curl "https://app.speclatch.com/api/v1/tables" \
  -H "Authorization: Bearer $SPECLATCH_API_KEY"

Response · 200

GET/api/v1/tables
{
  "tables": [
    {
      "id": "tbl_ac1m0t",
      "name": "AC Induction Motors",
      "description": "NEMA frame motors, 1-20 HP.",
      "publishedRecordCount": 4
    },
    {
      "id": "tbl_gearbx",
      "name": "Inline Gear Reducers",
      "description": null,
      "publishedRecordCount": 9
    }
  ]
}
  • Tables are ordered by their configured sort order, then by name.
  • description is null when the table has none.

Describe a table

GET/api/v1/tables/{id}

The table's schema as the key may see it: every field with its type, unit, choices, link target and the /records operators that accept it, plus the table's performance-curve definitions. Call it once, then query records with confidence.

ParameterInTypeDescription
idrequiredpathstringThe table id (from /tables).
langquerystring (en | fr | es)Display language for field names, descriptions and choices.

Request

curl "https://app.speclatch.com/api/v1/tables/tbl_ac1m0t" \
  -H "Authorization: Bearer $SPECLATCH_API_KEY"

Response · 200

GET/api/v1/tables/{id}
{
  "table": {
    "id": "tbl_ac1m0t",
    "name": "AC Induction Motors",
    "description": "NEMA frame motors, 1-20 HP.",
    "publishedRecordCount": 4,
    "fields": [
      {
        "key": "rated_power",
        "name": "Rated Power",
        "type": "UNIT_NUMBER",
        "description": "Nameplate output",
        "required": true,
        "visibility": "PUBLIC",
        "unit": "HP",
        "dimension": "POWER",
        "units": { "imperial": "HP", "metric": "W" },
        "filters": ["min", "max", "eq"],
        "sortable": true
      },
      {
        "key": "enclosure",
        "name": "Enclosure",
        "type": "SELECT",
        "description": null,
        "required": false,
        "visibility": "PUBLIC",
        "options": ["ODP", "TEFC", "TENV"],
        "filters": ["eq"],
        "sortable": true
      },
      {
        "key": "compatible_accessories",
        "name": "Compatible Accessories",
        "type": "LINK",
        "description": null,
        "required": false,
        "visibility": "PUBLIC",
        "linkTable": { "id": "tbl_acc001", "name": "Accessories" },
        "filters": [],
        "sortable": false
      },
      {
        "key": "installation_notes",
        "name": "Installation Notes",
        "type": "LONG_TEXT",
        "description": null,
        "required": false,
        "visibility": "PUBLIC",
        "formatted": true,
        "filters": [],
        "sortable": false
      }
    ],
    "curves": [
      {
        "key": "torque_speed",
        "name": "Torque vs speed",
        "x": { "label": "Speed", "unit": "RPM" },
        "y": { "label": "Torque", "unit": "N·m" }
      }
    ]
  }
}

Fields come in display order. filters and sortable tell you exactly which /records parameters accept each key.

  • Fields above the key's tier are absent, not marked. A PUBLIC-scoped key cannot learn that a confidential field exists.
  • unit is the storage unit the API returns value in; units are the two display units a dual value is rendered in.
  • formatted: true marks a several-lines text field whose values carry formatting. Its spec value is a Markdown subset (**bold**, *italic*, - and 1. lists, text links) and each spec also carries html, a sanitized rendering of the same.
  • curves lists the table's data-series definitions; the series themselves come with each record (see Get a record).

List records

GET/api/v1/records

One page of records visible to the key's tier, with every visible spec value. Narrow by table, full-text search, model number or SKU, change date, tag, or any field's value; sort; page with a cursor.

ParameterInTypeDescription
tableIdquerystringLimit results to one table (an id from /tables). Required to filter on a key whose type differs between tables.
qquerystringFull-text search over names, model numbers and spec values. Results come in relevance order unless sort is given.
limitqueryintegerPage size, 1 to 200. Default 50.
cursorquerystringThe page.next value from the previous response. Opaque, and bound to the exact query it was issued for. Reusing it with different parameters is a 400.
sortquerystringname, modelNumber, updatedAt, or a sortable field key (see Describe a table). Prefix - for descending. Records missing the value sort last.
min.{key}querynumber | dateLower bound on a numeric or date field, e.g. min.rated_power=5. Compared against the stored value in the field's unit; dates as YYYY-MM-DD. Records with no value are excluded.
max.{key}querynumber | dateUpper bound, same rules as min.
eq.{key}querystringCase-insensitive equality on a text, select, boolean, number or date field, e.g. eq.enclosure=TEFC. On a multi-select, "contains".
modelNumberquerystringExact model number, case-insensitive. The lookup an ERP or website keys on.
skuquerystringExact SKU, case-insensitive.
updatedSincequeryISO 8601 date-timeOnly records changed at or after this moment. Spec edits, built-in edits, tag changes and workflow transitions all count. The basis of an incremental sync.
statusqueryDRAFT | IN_REVIEW | PUBLISHEDKeys above PUBLIC only; a PUBLIC key sees PUBLISHED records and nothing else, so the parameter is refused.
tagquerystringRecords carrying this tag (by name, case-insensitive). INTERNAL-scoped keys and above.
specsquerystringComma-separated field keys to keep in each record's specs, e.g. specs=rated_power,enclosure. Smaller payloads when you only need a few values.
langquerystring (en | fr | es)Display language for labels, choice values and prose, where the organization has translated them. Stable field keys, ids and units are unaffected.

Request

curl "https://app.speclatch.com/api/v1/records?tableId=tbl_ac1m0t&min.rated_power=5&sort=-rated_power&limit=50" \
  -H "Authorization: Bearer $SPECLATCH_API_KEY"

Response · 200

GET/api/v1/records
{
  "records": [
    {
      "id": "rec_8f2k31",
      "tableId": "tbl_ac1m0t",
      "name": "Example Motor 20",
      "modelNumber": "EXM20",
      "sku": "EXM20-230-4P",
      "description": "Foot-mounted AC induction motor, 20 HP, 230/460 V.",
      "status": "PUBLISHED",
      "updatedAt": "2026-08-14T18:22:09.000Z",
      "specs": [
        {
          "field": "rated_power",
          "name": "Rated Power",
          "type": "UNIT_NUMBER",
          "value": 20,
          "unit": "HP",
          "dual": {
            "imperial": { "value": 20, "unit": "HP" },
            "metric": { "value": 14914, "unit": "W" }
          }
        },
        {
          "field": "compatible_accessories",
          "name": "Compatible Accessories",
          "type": "LINK",
          "value": [
            { "id": "rec_9b7q44", "name": "Mounting Base", "modelNumber": "ACC-BASE" }
          ]
        },
        {
          "field": "speed_range",
          "name": "Speed Range",
          "type": "ROLLUP",
          "value": [850, 1725],
          "unit": "RPM"
        },
        {
          "field": "installation_notes",
          "name": "Installation Notes",
          "type": "LONG_TEXT",
          "value": "Mount on a **level** base.\n\n- Torque bolts to spec\n- Check alignment before first run",
          "formatted": true,
          "html": "<p>Mount on a <strong>level</strong> base.</p><ul><li>Torque bolts to spec</li><li>Check alignment before first run</li></ul>"
        }
      ],
      "images": [
        {
          "id": "att_1",
          "filename": "front.png",
          "mimeType": "image/png",
          "sizeBytes": 20481,
          "isPrimary": true,
          "downloadUrl": "/api/v1/attachments/att_1"
        }
      ],
      "files": [
        {
          "id": "att_2",
          "filename": "outline-drawing.pdf",
          "mimeType": "application/pdf",
          "sizeBytes": 88213,
          "downloadUrl": "/api/v1/attachments/att_2"
        }
      ]
    }
  ],
  "page": {
    "limit": 50,
    "total": 1,
    "next": null
  }
}
  • Responses are paginated: page.total counts the whole filtered set, page.next is the cursor for the next page and null on the last. The default order is by name, or by relevance when q is given.
  • Nothing is silently ignored: an unknown parameter, an unknown field key, an operator the field's type does not support, or a cursor from a different query is a 400 BAD_REQUEST with the reason.
  • tags appears on each record for INTERNAL-scoped keys and above; PUBLIC-scoped responses never carry it.
  • Responses served in French or Spanish include a top-level lang key echoing the language.

Get a record

GET/api/v1/records/{id}

One record in full: tier-projected specs, images, files, its table, its performance curves, and documents: the record's documents and its table's, visible at the key's tier.

ParameterInTypeDescription
idrequiredpathstringThe record id (from /records).
langquerystring (en | fr | es)Display language for labels, choice values and prose.

Request

curl "https://app.speclatch.com/api/v1/records/rec_8f2k31" \
  -H "Authorization: Bearer $SPECLATCH_API_KEY"

Response · 200

GET/api/v1/records/{id}
{
  "record": {
      "id": "rec_8f2k31",
      "tableId": "tbl_ac1m0t",
      "name": "Example Motor 20",
      "modelNumber": "EXM20",
      "sku": "EXM20-230-4P",
      "description": "Foot-mounted AC induction motor, 20 HP, 230/460 V.",
      "status": "PUBLISHED",
      "updatedAt": "2026-08-14T18:22:09.000Z",
      "specs": [
        {
          "field": "rated_power",
          "name": "Rated Power",
          "type": "UNIT_NUMBER",
          "value": 20,
          "unit": "HP",
          "dual": {
            "imperial": { "value": 20, "unit": "HP" },
            "metric": { "value": 14914, "unit": "W" }
          }
        },
        {
          "field": "compatible_accessories",
          "name": "Compatible Accessories",
          "type": "LINK",
          "value": [
            { "id": "rec_9b7q44", "name": "Mounting Base", "modelNumber": "ACC-BASE" }
          ]
        },
        {
          "field": "speed_range",
          "name": "Speed Range",
          "type": "ROLLUP",
          "value": [850, 1725],
          "unit": "RPM"
        },
        {
          "field": "installation_notes",
          "name": "Installation Notes",
          "type": "LONG_TEXT",
          "value": "Mount on a **level** base.\n\n- Torque bolts to spec\n- Check alignment before first run",
          "formatted": true,
          "html": "<p>Mount on a <strong>level</strong> base.</p><ul><li>Torque bolts to spec</li><li>Check alignment before first run</li></ul>"
        }
      ],
      "images": [
        {
          "id": "att_1",
          "filename": "front.png",
          "mimeType": "image/png",
          "sizeBytes": 20481,
          "isPrimary": true,
          "downloadUrl": "/api/v1/attachments/att_1"
        }
      ],
      "files": [
        {
          "id": "att_2",
          "filename": "outline-drawing.pdf",
          "mimeType": "application/pdf",
          "sizeBytes": 88213,
          "downloadUrl": "/api/v1/attachments/att_2"
        }
      ]
    
,
      "table": { "id": "tbl_ac1m0t", "name": "AC Induction Motors" },
      "curves": [
        {
          "key": "torque_speed",
          "name": "Torque vs speed",
          "x": { "label": "Speed", "unit": "RPM" },
          "y": { "label": "Torque", "unit": "N·m" },
          "series": [
            { "label": "60 Hz", "points": [{ "x": 0, "y": 240 }, { "x": 1725, "y": 81 }] }
          ]
        }
      ],
      "documents": [
        {
          "id": "doc_5t1m20",
          "title": "EXM20 Spec Sheet",
          "filename": "exm20-spec-sheet.pdf",
          "docType": "SPEC_SHEET",
          "mimeType": "application/pdf",
          "sizeBytes": 182340,
          "validUntil": null,
          "downloadUrl": "/api/v1/documents/doc_5t1m20/download",
          "source": "record"
        }
      ]
    }
}

The detail payload wraps the record in a record key and adds table, curves and documents.

  • A 404 covers both records that don't exist and records the key's tier may not see. The API never confirms the existence of hidden data.
  • curves groups the record's data series by definition: each group carries its axes (label + unit) and one series entry per sibling curve, points in the axis units. Only definitions at or below the key's tier appear.
  • A spec from a formatted text field carries html beside its value: value is the Markdown subset the organization stores, html is sanitized (only p, br, strong, em, a, ul, ol, li; links are http(s) or mailto only). Render either; never treat value as HTML.
  • documents[].validUntil is the expiry date a document carries (YYYY-MM-DD), or null.
  • documents lists the record's own documents first, then the ones linked to its table, such as a product line's catalog or manual. source is record or table.
  • Responses served in French or Spanish include a top-level lang key.

List tags

GET/api/v1/tags

The organization's tags with record counts: the vocabulary behind ?tag= on /records. INTERNAL-scoped keys and above.

Request

curl "https://app.speclatch.com/api/v1/tags" \
  -H "Authorization: Bearer $SPECLATCH_API_KEY"

Response · 200

GET/api/v1/tags
{
  "tags": [
    { "id": "tag_3k9f", "name": "2026 catalog", "color": "#2f9e44", "recordCount": 42 },
    { "id": "tag_7a2c", "name": "Discontinued", "color": null, "recordCount": 6 }
  ]
}
  • Tags are internal information and never appear on the public portal, so a PUBLIC-scoped key receives 403 TIER_SCOPE here rather than an empty list.
  • recordCount counts records in the organization carrying the tag, at every status.

Download an attachment

GET/api/v1/attachments/{id}

The raw bytes of an image or file from a record's images / files lists, exactly what each entry's downloadUrl points at.

ParameterInTypeDescription
idrequiredpathstringThe attachment id (from an images or files entry).

Request

curl "https://app.speclatch.com/api/v1/attachments/att_2" \
  -H "Authorization: Bearer $SPECLATCH_API_KEY" \
  -o outline-drawing.pdf

Response · 200

GET/api/v1/attachments/{id}
{
  "_comment": "Binary response - the file bytes, not JSON.",
  "Content-Type": "application/pdf",
  "Content-Length": "88213",
  "Content-Disposition": "attachment; filename=\"outline-drawing.pdf\""
}

The response is the file itself; headers shown for orientation. Images are served inline, other types as downloads.

  • 404s unless the attachment's field is at or below the key's tier AND the record itself is visible.

Download a document

GET/api/v1/documents/{id}/download

The raw bytes of a generated document (spec sheet, catalog) from a record's documents list.

ParameterInTypeDescription
idrequiredpathstringThe document id (from a record's documents list).

Request

curl "https://app.speclatch.com/api/v1/documents/doc_5t1m20/download" \
  -H "Authorization: Bearer $SPECLATCH_API_KEY" \
  -o exm20-spec-sheet.pdf

Response · 200

GET/api/v1/documents/{id}/download
{
  "_comment": "Binary response - the document bytes, not JSON.",
  "Content-Type": "application/pdf",
  "Content-Length": "182340"
}

The response is the document itself; headers shown for orientation.

  • 404s unless the document is flagged visible at the key's tier and its record is visible.

Response shape

Spec values are unit-aware: numeric fields carry their unit and a dual imperial/metric rendering, keyed by stable machine-readable field keys. Records also carry tableId, sku, description, status and updatedAt. On the list, ?updatedSince= turns updatedAt into an incremental sync.

LINK specs list the records they point at; LOOKUP and ROLLUP specs carry values derived from those linked records. A range-style rollup returns value as a [min, max] pair with its unit (and no dual). A linked record is only ever named when your key may see that record too. A PUBLIC key never learns about an unpublished one.

A several-lines text field can carry formatting (bold, italic, lists, links). Its field descriptor says formatted: true, its spec value is a small Markdown subset, and a sanitized html rendering rides beside it, the way dual rides beside a number. The same subset is what a CSV import accepts for such a field; SpecLatch normalizes it on the way in.

Add ?lang=fr or ?lang=es to get display strings (name, choice values, descriptions) in that language where the organization has translated them; the response then carries a top-level lang key. Languages beyond the workspace's default follow its plan. The stable field keys, ids and units never change with the language, so your integration code doesn't either.

Response shape
{
  "field": "rated_torque",
  "name": "Rated Torque",
  "type": "UNIT_NUMBER",
  "value": 240,
  "unit": "N·m",
  "dual": {
    "imperial": { "value": 177.01, "unit": "lb·ft" },
    "metric": { "value": 240, "unit": "N·m" }
  }
}

The anatomy of one spec entry. (All sample data in this reference is fake.)

Querying and pagination

/records returns one page at a time: limit sets the page size (1 to 200, default 50) and the response's page object carries total, the size of the whole filtered set, and next, an opaque cursor for the following page (null on the last one). Pass it back as ?cursor= with the same parameters; a cursor is bound to the query that issued it and is refused with any other.

Filters address fields by their stable key with an operator prefix: min.rated_power=5, max.rated_power=20, eq.enclosure=TEFC. Ranges apply to numeric and date fields and compare the stored value in the field's unit; equality applies to text, select, boolean, number and date fields (case-insensitive, and "contains" on a multi-select). Describe a table tells you which operators each key accepts.

sort takes name, modelNumber, updatedAt or a sortable field key, with - for descending. modelNumber= and sku= look a record up by its natural key, updatedSince= returns what changed since your last run, tag= narrows to a tag (INTERNAL+ keys) and specs= trims each record to the fields you name.

Every JSON response carries a weak ETag. Send it back as If-None-Match and an unchanged result returns 304 with no body. Polling a catalog that changes a few times a day then costs almost nothing.

Querying and pagination
curl "https://app.speclatch.com/api/v1/records?tableId=tbl_ac1m0t&min.rated_power=5&max.rated_power=20&eq.enclosure=TEFC&sort=-rated_power&specs=rated_power,enclosure&limit=100" \
  -H "Authorization: Bearer $SPECLATCH_API_KEY" \
  -H 'If-None-Match: W/"3f2a9c…"'

Motors from 5 to 20 HP in a TEFC enclosure, largest first, two spec values each. Nothing at all if the catalog hasn't changed.

Errors

Every error is JSON with a machine-readable code and a human-readable message. The codes are BAD_REQUEST (400, a parameter the API cannot honour, with the reason), UNAUTHORIZED (401), PLAN_LIMIT, SUSPENDED and TIER_SCOPE (403, a valid key that may not do this), NOT_FOUND (404), RATE_LIMITED (429) and INTERNAL (500). An unexpected server error still returns the same envelope, with a requestId.

A 404 covers missing resources and resources your key's tier may not see. The API deliberately doesn't distinguish the two, so hidden data is never confirmed to exist.

Every response, success or error, carries an X-Request-Id header. Quote it when you write to support and we can find the exact request.

Errors
{
  "error": {
    "code": "NOT_FOUND",
    "message": "Record not found"
  }
}

Rate limits

Limits apply per key and follow the workspace's plan: 120 requests per minute on Growth, 600 on Professional and above. Every response, success or error, includes X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (a unix timestamp).

Exceeding the limit returns 429 with a Retry-After header. Back off until the window resets; a small response cache on your side goes a long way for catalog data that changes a few times a day.

Rate limits
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 119
X-RateLimit-Reset: 1767139200

Versioning

The version lives in the path: /api/v1. Additive changes (new fields, new endpoints, new query parameters) ship in place; anything that would break an existing integration arrives in a new version prefix instead.

Within v1 so far: linked-record, lookup and rollup specs plus images/files (1.1); ?lang= display languages (1.2); the tables/records vocabulary (1.3); full machine-readable schemas in the OpenAPI description (1.4); pagination, filters, sort, lookup by model number or SKU, updatedSince, schema discovery, tags, curves, ETag/304 and request ids (1.5); spec group and table documents on a record (1.6); units on lookups of numbers (1.7); Calculated fields that return a choice: the value is the label, options lists the labels, eq filters it (1.8); display.exact for numbers printed with their trailing zeros (1.9); calculated on curves the tenant computes from the record's values (1.10).

One exception on record: 1.5 made /records paginated, which changed what a bare call returns. It shipped on 2026-11-01, before any external integration existed, and is the only such change in v1's history.

OpenAPI spec

The machine-readable description of this API lives at https://www.speclatch.com/openapi.yaml. It is an OpenAPI 3.1 document with typed schemas for every payload, ready for client generation and request validation tooling.

The spec and this reference are kept in lockstep by automated checks: an endpoint can't ship, change shape, or gain a parameter without both being updated together.