Assertions let you validate HTTP responses — status codes, body content, and headers. They're the core of yapi's testing capability.

Status Expectations

expect:
  status: 200              # Exact match
  status: [200, 201, 204]  # Any of these

Body Assertions

Body assertions are JQ expressions that must evaluate to true:

expect:
  status: 200
  assert:
    - .id != null
    - .email != null
    - .active == true

Operators

All JQ comparison operators work: ==, !=, >, >=, <, <=

assert:
  - . | length > 0          # Array has items
  - .count >= 10             # Numeric comparison
  - .name != ""              # Not empty string

Array Operations

assert:
  - . | type == "array"
  - . | length > 0
  - .[0].name != null        # First element
  - .[] | .status == "active" # All items match

Type Checks

assert:
  - . | type == "array"
  - .data | type == "object"
  - .count | type == "number"

Environment Variable References

Compare response values against environment variables using env.VAR_NAME:

assert:
  - .owner.login == env.GITHUB_USER
  - .email == env.EXPECTED_EMAIL

Header Assertions

Use the grouped syntax to assert on response headers:

expect:
  status: 200
  assert:
    headers:
      - .["content-type"] | startswith("application/json")
      - .["x-request-id"] != null
    body:
      - .id != null

When using the grouped syntax, body assertions go under body:.

Flat vs Grouped Syntax

Flat (all assertions are body assertions):

assert:
  - .id != null

Grouped (separate body and header assertions):

assert:
  headers:
    - .["content-type"] | contains("json")
  body:
    - .id != null

Assertions in Chains

Each chain step can have its own expect block:

chain:
  - name: create
    url: /api/items
    method: POST
    body: { title: "test" }
    expect:
      status: 201
      assert:
        - .id != null

  - name: verify
    url: /api/items/${create.id}
    method: GET
    expect:
      status: 200
      assert:
        - .title == "test"