Chain API requests and check a captured token

← All templates

Requirements: Internet access; no model or account.

Download this workflow ZIP

Complete project · 1.6 KB · No signup

The steps

1. Echo login payload
2. Capture and check token
3. Send authenticated-style request
4. Verify echoed header

Run it in Bandura

1. Install Bandura. Read the platform’s installation notes.
2. Extract the ZIP into a new folder. Keep the included files together.
3. Choose File → Open Folder and select that folder. Open workflow.aether.
4. Press Run. The requests go to the public httpbingo.org echo service; use synthetic data only.
5. Select a step to inspect results and variables. For CSV evaluation, review the row results in History.

Expected result

Two successful HTTP requests and passing assertions. The echo service does not authenticate users: this example demonstrates capture and reuse with a synthetic token.

Try a failure

Change the final expected token from tok-example-123 to another value and run again. The echoed-header assertion should fail. Restore the example after inspecting the failed step.

Workflow source

version: "1.0"
name: Capture and reuse a demo token
description: Demonstrate request chaining with an echo API, not real authentication.
start: login
variables:
  baseUrl: https://httpbingo.org
nodes:
  - id: login
    label: Echo a demo login payload
    type: request
    config:
      method: POST
      url: ${{ variables.baseUrl }}/anything/login
      headers:
        Content-Type: application/json
      body: '{"username":"demo","token":"tok-example-123"}'
      capture:
        accessToken: response.body.json.token
    next: token_check
    ui:
      position: { x: 80, y: 80 }
  - id: token_check
    label: Check captured token
    type: assertion
    config:
      check: "response.status === 200 && variables.accessToken === 'tok-example-123'"
    next: profile
    ui:
      position: { x: 340, y: 80 }
  - id: profile
    label: Send token in next request
    type: request
    config:
      method: GET
      url: ${{ variables.baseUrl }}/anything/profile
      headers:
        Authorization: Bearer ${{ variables.accessToken }}
    next: verify
    ui:
      position: { x: 600, y: 80 }
  - id: verify
    label: Check echoed header
    type: assertion
    config:
      check: "response.status === 200 && String(response.body.headers.Authorization) === 'Bearer tok-example-123'"
    next: null
    ui:
      position: { x: 860, y: 80 }

Validation and limits

Prepared October 1, 2026. Format and execution checks target source version 1.0.0 using deterministic model responses and a local HTTP echo fixture. Real Ollama/LM Studio model output and the public echo service are not guaranteed by those tests. Setup and troubleshooting.

Use synthetic data while learning. Prompts request a format; assertions verify it. They cannot guarantee model correctness. Review outputs before connecting the workflow to real actions. Bandura has no built-in scheduling or hosted execution.

1df0284408abbf29aa7ffac12882302bc96d9dd0cdea6fd829767a6609baa960