generated: '2026-07-21'
method: searched
source: https://developer.zenput.com
docs: https://developer.zenput.com/docs/introduction
authentication:
  style: api-token-header
  header: X-API-TOKEN
  ref: authentication/zenput-authentication.yml
versioning:
  scheme: uri-path
  versions:
  - v1
  - v3
  detail: >-
    API version is carried in the URL path. Core resources live under
    /api/v1/ (e.g. /api/v1/forms/list_templates/); newer submission and
    location endpoints are exposed under /api/v3/ (e.g. /api/v3/submissions/batch,
    the v3 locations listing).
  ref: lifecycle/zenput-lifecycle.yml
pagination:
  style: token-batch
  detail: >-
    Standard list endpoints return up to a 10,000 record limit. For larger
    result sets the Large Batch submissions flow returns 2,500 records at a
    time: POST to /api/v3/submissions/batch, and if a token is returned in the
    response, send that token via GET to /api/v3/submissions/batch to fetch the
    next page. Paging is therefore continuation-token based rather than
    offset/limit.
  next_token: true
base_urls:
  production: https://www.zenput.com/api/v1/
  staging: https://staging.zenput.com/api/v1/
  ref: sandbox/zenput-sandbox.yml
idempotency:
  supported: unknown
  detail: >-
    No idempotency-key header or retry-safety contract is documented in the
    public developer portal. Not asserted (no Idempotency pointer emitted).
error_envelope:
  detail: >-
    Error response envelope shape is not documented verbatim in the public
    portal excerpt; standard REST HTTP status codes apply. Not asserted.
notes: >-
  Cross-cutting semantics derived from the ReadMe-hosted developer portal
  (developer.zenput.com) and the published llms.txt endpoint index. Only
  conventions with documented evidence are asserted; idempotency and the exact
  error envelope are left unknown rather than fabricated.