Read ZalesMachine like a machine.

Quickstart

Three requests and you know what ZalesMachine is, what it costs and what it has delivered.

curl -sS https://www.zalesmachine.com/api/v1/company
curl -sS "https://www.zalesmachine.com/api/v1/case-studies?service=outbound&lang=es"
curl -sS -H "Accept: text/markdown" https://www.zalesmachine.com/

Endpoints

Base URL: https://www.zalesmachine.com

Every endpoint accepts ?lang=en|es. Default is English.

OpenAPI 3.1: https://www.zalesmachine.com/openapi.json

Errors

Every error under /api is JSON with the same shape, including unknown paths (404) and unsupported methods (405). No HTML is ever returned under /api.

{
  "error": {
    "code": "not_found",
    "message": "Case study \"acme\" was not found.",
    "hint": "Valid slugs: aon, visma, thomson-reuters, ... List them at /api/v1/case-studies.",
    "status": 404,
    "docs": "https://www.zalesmachine.com/developers"
  }
}

Pages as Markdown

Send Accept: text/markdown to any page of the site and you get the same content as Markdown, with Content-Type: text/markdown and Vary: Accept. Unknown paths return a 404 with a Markdown body that points to the sitemap and llms.txt.

curl -sS -i -H "Accept: text/markdown" https://www.zalesmachine.com/es/casos/mendel

Machine-readable files

• openapi.json

  OpenAPI 3.1 spec of the public API. Also at /api/openapi.json.

• .well-known/api-catalog

  API catalog (RFC 9727): where the spec, the docs and the policy live, as a Linkset.

• llms.txt

  Company summary for LLMs: when to use ZalesMachine, pricing, modules, case studies, articles.

• sitemap.xml

  Every indexable page in both languages.

• brand-system.html

  Design tokens as JSON, voice rules and claims with validity dates.

Rate limits

60 requests per minute per client IP. Every response carries the IETF RateLimit headers, in the current structured form (RateLimit-Policy, RateLimit) and in the earlier integer form (RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset). Over the limit you get a 429 with a JSON error and Retry-After in seconds: wait that long and retry. Successful responses are cacheable for 5 minutes.

HTTP/2 200
RateLimit-Policy: "default";q=60;w=60
RateLimit: "default";r=59;t=60
RateLimit-Limit: 60
RateLimit-Remaining: 59
RateLimit-Reset: 60
API-Version: 1
Link: <https://www.zalesmachine.com/developers#versioning>; rel="deprecation"; type="text/html"

HTTP/2 429
Retry-After: 42
{ "error": { "code": "rate_limited", "message": "Too many requests.", ... } }

Terms

Prices and figures carry an as-of date and are updated with the site. There are no write endpoints: hiring, booking a call or sending data goes through a person.

Need something the API does not expose (a webhook, an MCP server, write access for a client integration)? Write to nfrancese@zalesmachine.com.