generated: '2026-08-13'
method: searched
source: https://app.choozle.com/apidoc/
also_probed:
  - https://status.choozle.com/
  - https://trust.choozle.com/
  - https://help.choozle.com/connecting-to-choozles-reporting-api
summary: >-
  Choozle publishes an API reference but no lifecycle commitments of any kind —
  no versioning scheme a caller can select, no deprecation policy, no dated
  changelog, no SLA and no status page. The reference itself carries a strong
  staleness signal: the apiDoc generator stamp reads 2015-06-04.
versioning:
  scheme: none-in-transport
  current: null
  selectable: false
  docs: https://app.choozle.com/apidoc/
  note: >-
    No path segment, header or query parameter selects a version. The base URL
    is https://app.choozle.com/api. Version strings exist only as metadata
    inside the published apiDoc dataset — each operation is tagged 1.0.0 and the
    project is 0.1.0 — and neither is addressable by a client.
  evidence:
    - source: https://app.choozle.com/apidoc/api_project.json
      field: version
      value: '0.1.0'
    - source: https://app.choozle.com/apidoc/api_data.json
      field: version (per operation)
      value: '1.0.0'
deprecation:
  policy_url: null
  policy_published: false
  sunset_header: false
  deprecation_header: false
  deprecated_operations: []
  note: >-
    No deprecation policy, no RFC 8594 Sunset or Deprecation header support, and
    no operation in the contract is marked deprecated. No Deprecation pointer is
    emitted.
changelog:
  url: null
  published: false
  note: >-
    No dated API changelog or release-notes page exists on choozle.com,
    help.choozle.com or app.choozle.com. The company blog at
    https://choozle.com/blog/ is marketing content, not release notes, and is
    already captured under blogs/.
status_page:
  url: null
  published: false
  note: >-
    No status page. https://status.choozle.com/ and https://trust.choozle.com/
    both resolve through a wildcard to the Choozle application and return the
    login page, not a status or trust surface — this is DNS catch-all behaviour,
    not a published page. No StatusPage pointer is emitted.
  evidence:
    - url: https://status.choozle.com/
      status: 200
      served: false
      reason: wildcard resolves to the app login page
    - url: https://trust.choozle.com/
      status: 200
      served: false
      reason: wildcard resolves to the app login page
sla:
  url: null
  uptime_target: null
  note: >-
    No uptime target or availability commitment is published for the API. The
    terms of service at https://choozle.com/terms-of-service/ govern the
    platform generally.
staleness:
  api_reference_generator_time: '2015-06-04T16:45:58.265Z'
  api_reference_generator: apidoc 0.13.1
  api_reference_last_modified: '2026-04-06'
  note: >-
    The reference at https://app.choozle.com/apidoc/ is still being redeployed —
    the JSON assets carry a 2026-04-06 Last-Modified — but its embedded
    generator timestamp shows the content was generated in June 2015 and has not
    been regenerated since. The examples in it are dated 2014 and 2015. Choozle
    has since added Amazon DSP, DOOH, Search and Social channels to the platform;
    none of that is reflected in the API surface, which remains the three
    original reporting operations.
  corroboration: >-
    The published apiDoc records the source file as
    ../../../app/Controller/ApiController.php, a single controller — consistent
    with a small reporting-only API rather than a platform API that grew with
    the product.
access_lifecycle:
  key_issuance: >-
    An ORG admin or advertiser admin creates an API profile/username in the
    application; the system generates the API secret key, which is released only
    on a Customer Portal ticket. There is no self-service key page and no
    programmatic key rotation.
  api_only_users: >-
    An API Only user has full access to account data through the API, including
    campaign and ad group reporting data, but cannot view, edit or otherwise
    access the account from the website.
  token_lifetime_seconds: 7200
  token_rotation: re-authenticate; no refresh token