Attlaz API

openapi: 3.1.0
info:
  title: Attlaz API
  version: '2026-10-19'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-19: 6 operation(s) read from 7 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; Attlaz has published no machine-readable contract that the pipeline
    could find. Engine: anthropic.'
  x-evidence-tiers:
    code-example: 6
    documentation: 0
    pages-with-code: 5
    pages-read: 7
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-19'
  x-generator: generate-contract-from-docs.py
  x-engine: anthropic
  x-sources:
  - https://docs.attlaz.com/reference/api/auth
  - https://docs.attlaz.com/reference/mcp-tools
  - https://docs.attlaz.com/reference/api/overview
  - https://docs.attlaz.com/reference/api/filtering
  - https://docs.attlaz.com/reference/api/pagination
  - https://docs.attlaz.com/reference/api/identifiers
  - https://docs.attlaz.com/integrations/catalog
servers:
- url: https://api.attlaz.com
paths:
  /1.13:
    get:
      operationId: get_1_13
      tags:
      - '1'
      summary: GET /1.13
      x-source: https://docs.attlaz.com/reference/api/auth
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl https://api.attlaz.com/1.13/ .. . \\ -H \"Authorization: Bearer <personal_access_token>\" \n See Permissions & scopes for\
          \ how a token's scopes and your project access determine what it can do. \n Connecting connectors ​ \n Connecting a third-party connector\
          \ (Magento 2, Google, and so on) uses a dedicated, browser-based OAuth flow rather than a token you pass yourself. Your integration\
          \ first calls P"
  /1.13/configurations/prj_0iFyTMyAouzgjpuF6aqRxiLWbPs:
    get:
      operationId: get_1_13_configurations_prj_0iFyTMyAouzgjpuF6aqRxiLWbPs
      tags:
      - '1'
      summary: GET /1.13/configurations/prj_0iFyTMyAouzgjpuF6aqRxiLWbPs
      x-source: https://docs.attlaz.com/reference/api/identifiers
      parameters:
      - name: path
        in: query
        required: false
        schema:
          type: string
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl \"https://api.attlaz.com/1.13/configurations/prj_0iFyTMyAouzgjpuF6aqRxiLWbPs?path=database.host\" \\ -H \"Authorization:\
          \ Bearer <access_token>\" \n Two rules cover everything else: \n In responses, ids are never prefixed. An id field is always the bare\
          \ 27 characters. \n In requests, either form is accepted. Where an endpoint takes an id, passing the prefixed\nform works too — the\
          \ prefix is ignored. It"
  /1.13/environments:
    get:
      operationId: get_1_13_environments
      tags:
      - '1'
      summary: GET /1.13/environments
      x-source: https://docs.attlaz.com/reference/api/overview
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl https://api.attlaz.com/1.13/environments \\ -H \"Authorization: Bearer <access_token>\" \n For server-to-server integrations,\
          \ use an OAuth client instead. \n Read next ​ \n Authentication — obtain and use access tokens. \n Permissions & scopes — what a token\
          \ is allowed to do. \n Requests — base URL, versioning, response envelope, and errors. \n Identifiers — the shape of an id , and when\
          \ it carries a "
  /1.13/pulse/catalogs/abc123/products:
    get:
      operationId: get_1_13_pulse_catalogs_abc123_products
      tags:
      - '1'
      summary: GET /1.13/pulse/catalogs/abc123/products
      x-source: https://docs.attlaz.com/reference/api/filtering
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl https://api.attlaz.com/1.13/pulse/catalogs/abc123/products?brand = Nike \\ -H 'Authorization: Bearer {TOKEN}' \n Multiple\
          \ string filters can be combined. Only records matching all filters are returned: "
  /1.13/resources:
    get:
      operationId: get_1_13_resources
      tags:
      - '1'
      summary: GET /1.13/resources
      x-source: https://docs.attlaz.com/reference/api/filtering
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl https://api.attlaz.com/1.13/resources?status = active \\ -H 'Authorization: Bearer {TOKEN}' \n Passing an invalid enum\
          \ value returns a 400 Bad Request error with the allowed options. \n Combining Filters with Pagination ​ \n Filters work together with\
          \ cursor pagination . Apply filters as query parameters alongside limit , starting_after , and ending_before : "
  /oauth/token:
    post:
      operationId: post_oauth_token
      tags:
      - Oauth
      summary: POST /oauth/token
      x-source: https://docs.attlaz.com/reference/api/auth
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl -X POST https://api.attlaz.com/oauth/token \\ -H \"Content-Type: application/x-www-form-urlencoded\" \\ -d \"grant_type=client_credentials\"\
          \ \\ -d \"client_id=<client_id>\" \\ -d \"client_secret=<client_secret>\" \n The response contains an access_token you send as the Authorization:\
          \ Bearer header. Tokens expire; when a token expires, request a new one (or use a refresh_token grant if you were issued a re"
components:
  securitySchemes:
    bearer:
      type: http
      scheme: bearer
security:
- bearer: []
tags:
- name: '1'
- name: Oauth