> ## Documentation Index
> Fetch the complete documentation index at: https://www.courier.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# List steps for a Journey run

> List the per-node state of one Journey run, in full — this endpoint is not paginated. Each step's `node_id` is the id of the node in the published Journey, so a step maps directly onto the Journey graph. `message_id` is present on send steps that produced a message; follow it to `GET /messages/{message_id}` for delivery status.



## OpenAPI

````yaml /openapi-specs/openapi.documented.yml get /journeys/runs/{run_id}/steps
openapi: 3.0.1
info:
  title: Courier
  description: The Courier REST API for sending and managing notifications across channels.
  version: 0.0.1
servers:
  - url: https://api.courier.com
    description: Production
security: []
tags:
  - name: Send
    description: >-
      Send a message to one or more recipients — users, lists, audiences, or
      tenants — across every channel you have configured.
  - name: Templates
    description: >-
      Create, update, version, publish, and localize notification templates and
      their content.
  - name: Brands
    description: >-
      Manage the logos, colors, and layout that give the templates you send a
      consistent look.
  - name: Routing Strategies
    description: >-
      Define reusable channel routing and failover strategies, and see which
      templates use them.
  - name: Journeys
    description: >-
      Build, version, publish, invoke, and cancel multi-step notification
      workflows, along with the templates scoped to them.
  - name: Broadcasts
    description: >-
      Create a one-off send to a list or audience, author its content, then send
      it immediately or schedule it for later.
  - name: User Profiles
    description: >-
      Store the contact information Courier delivers to for each user — email,
      phone number, push tokens, and any custom data you send to.
  - name: Tenants
    description: >-
      Manage tenants — the organizations, teams, or accounts your users belong
      to — along with their users and default preferences.
  - name: Audiences
    description: >-
      Define filter-based groups whose membership Courier recalculates as user
      profiles change.
  - name: Lists
    description: >-
      Manage static groups of users that you subscribe explicitly, and send to
      them by list id or list pattern.
  - name: Providers
    description: >-
      Configure the channel providers Courier delivers through, and browse the
      provider types it supports.
  - name: Preference Topics
    description: >-
      Manage the workspace catalog of subscription topics, the sections that
      group them, and publishing the preference page.
  - name: User Preferences
    description: >-
      Read and write a single user's notification preferences, per topic and per
      channel.
  - name: Messages
    description: >-
      Look up the messages Courier has accepted, inspect their delivery history
      and rendered output, and cancel, resend, or archive them.
  - name: Device Tokens
    description: >-
      Register and manage the APNS and FCM device tokens Courier delivers push
      notifications to.
  - name: Tenant Memberships
    description: >-
      Associate a user with one or more tenants, and read or remove those
      associations.
  - name: Tenant Templates
    description: >-
      Manage the templates and template versions scoped to a single tenant,
      including the ones authored in the embedded designer.
  - name: Automations
    description: >-
      Invoke a stored automation template or an ad hoc automation defined in the
      request.
  - name: Digests
    description: >-
      Inspect what has accumulated in a digest schedule and release a digest
      ahead of its next scheduled delivery.
  - name: Translations
    description: >-
      Store and retrieve the translation strings Courier uses to render
      localized template content.
  - name: Track Events
    description: >-
      Record an inbound event that triggers the journeys and automations mapped
      to it.
  - name: Audit Events
    description: >-
      Read the audit trail of configuration and access changes in your
      workspace.
  - name: Authentication
    description: >-
      Issue scoped, short-lived JWTs so client-side SDKs — Inbox, Preferences,
      and the embedded designer — can call Courier as a single user. Server-side
      requests authenticate with your workspace API key instead.
paths:
  /journeys/runs/{run_id}/steps:
    get:
      tags:
        - Journeys
      summary: List steps for a Journey run
      description: >-
        List the per-node state of one Journey run, in full — this endpoint is
        not paginated. Each step's `node_id` is the id of the node in the
        published Journey, so a step maps directly onto the Journey graph.
        `message_id` is present on send steps that produced a message; follow it
        to `GET /messages/{message_id}` for delivery status.
      operationId: journeys_list_run_steps
      parameters:
        - name: run_id
          in: path
          description: A unique identifier representing the Journey run.
          required: true
          schema:
            type: string
            minLength: 1
      responses:
        '200':
          description: Every step of the Journey run.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/JourneyRunStepsResponse'
              examples:
                Example1:
                  value:
                    steps:
                      - node_id: node_1786394360065_4z4dv0oxk
                        action: send
                        status: PROCESSED
                        created_at: '2026-08-10T23:40:17.015Z'
                        updated_at: '2026-08-10T23:40:48.879Z'
                        message_id: 0nbHxOAZ701QO2wFU9z81
                      - node_id: node_1770752689239_ek6riz4xv
                        action: exit
                        status: PROCESSED
                        created_at: '2026-08-10T23:40:17.015Z'
                        updated_at: '2026-08-10T23:41:09.702Z'
        '400':
          description: Malformed run id.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BadRequest'
              examples:
                Example:
                  value:
                    message: invalid run id
                    type: invalid_request_error
        '404':
          description: >-
            No such run in this workspace, or the run has passed its retention
            window.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotFound'
              examples:
                Example:
                  value:
                    message: run not found
                    type: invalid_request_error
      security:
        - BearerAuth: []
      x-codeSamples:
        - lang: JavaScript
          source: >-
            import Courier from '@trycourier/courier';


            const client = new Courier({
              apiKey: process.env['COURIER_API_KEY'], // This is the default and can be omitted
            });


            const journeyRunStepsResponse = await
            client.journeys.runs.listSteps('x');


            console.log(journeyRunStepsResponse.steps);
        - lang: Python
          source: |-
            import os
            from courier import Courier

            client = Courier(
                api_key=os.environ.get("COURIER_API_KEY"),  # This is the default and can be omitted
            )
            journey_run_steps_response = client.journeys.runs.list_steps(
                "x",
            )
            print(journey_run_steps_response.steps)
        - lang: Go
          source: "package main\n\nimport (\n\t\"context\"\n\t\"fmt\"\n\n\t\"github.com/trycourier/courier-go/v4\"\n\t\"github.com/trycourier/courier-go/v4/option\"\n)\n\nfunc main() {\n\tclient := courier.NewClient(\n\t\toption.WithAPIKey(\"My API Key\"),\n\t)\n\tjourneyRunStepsResponse, err := client.Journeys.Runs.ListSteps(context.TODO(), \"x\")\n\tif err != nil {\n\t\tpanic(err.Error())\n\t}\n\tfmt.Printf(\"%+v\\n\", journeyRunStepsResponse.Steps)\n}\n"
        - lang: Java
          source: |-
            package com.courier.example;

            import com.courier.client.CourierClient;
            import com.courier.client.okhttp.CourierOkHttpClient;
            import com.courier.models.journeys.JourneyRunStepsResponse;
            import com.courier.models.journeys.runs.RunListStepsParams;

            public final class Main {
                private Main() {}

                public static void main(String[] args) {
                    CourierClient client = CourierOkHttpClient.fromEnv();

                    JourneyRunStepsResponse journeyRunStepsResponse = client.journeys().runs().listSteps("x");
                }
            }
        - lang: Ruby
          source: |-
            require "courier"

            courier = Courier::Client.new(api_key: "My API Key")

            journey_run_steps_response = courier.journeys.runs.list_steps("x")

            puts(journey_run_steps_response)
        - lang: PHP
          source: >-
            <?php


            require_once dirname(__DIR__) . '/vendor/autoload.php';


            use Courier\Client;

            use Courier\Core\Exceptions\APIException;


            $client = new Client(apiKey: getenv('COURIER_API_KEY') ?: 'My API
            Key');


            try {
              $journeyRunStepsResponse = $client->journeys->runs->listSteps('x');

              var_dump($journeyRunStepsResponse);
            } catch (APIException $e) {
              echo $e->getMessage();
            }
        - lang: C#
          source: >-
            using System;

            using TryCourier;

            using TryCourier.Models.Journeys.Runs;


            CourierClient client = new();


            RunListStepsParams parameters = new() { RunID = "x" };


            var journeyRunStepsResponse = await
            client.Journeys.Runs.ListSteps(parameters);


            Console.WriteLine(journeyRunStepsResponse);
        - lang: CLI
          source: |-
            courier journeys:runs list-steps \
              --api-key 'My API Key' \
              --run-id x
components:
  schemas:
    JourneyRunStepsResponse:
      title: JourneyRunStepsResponse
      description: Every step of a Journey run. Not paginated.
      type: object
      properties:
        steps:
          type: array
          items:
            $ref: '#/components/schemas/JourneyRunStep'
      required:
        - steps
      additionalProperties: false
    BadRequest:
      title: BadRequest
      type: object
      properties:
        type:
          type: string
          enum:
            - invalid_request_error
      required:
        - type
      allOf:
        - $ref: '#/components/schemas/BaseError'
    NotFound:
      title: NotFound
      type: object
      properties:
        type:
          type: string
          enum:
            - invalid_request_error
      required:
        - type
      allOf:
        - $ref: '#/components/schemas/BaseError'
    JourneyRunStep:
      title: JourneyRunStep
      description: >-
        One executed node of a Journey run. `node_id` is the id of the node in
        the published Journey, so a step maps directly onto the Journey graph.
      type: object
      properties:
        node_id:
          type: string
          description: The id of the node in the published Journey that this step executed.
        action:
          type: string
          description: The kind of node that ran, e.g. `send`, `delay`, or `exit`.
        status:
          type: string
          description: >-
            The state of the step: the seven run statuses, plus `SKIPPED` and
            `COMPUTING`. Not an enum — new values have been added before.
        created_at:
          type: string
          description: When the step started, as an ISO 8601 timestamp.
        updated_at:
          type: string
          description: When the step last changed state, as an ISO 8601 timestamp.
        message_id:
          type: string
          description: >-
            The message this step produced, present on send steps. Pass it to
            `GET /messages/{message_id}` for delivery status. A send to a List
            or an Audience yields one id for the request, not one per recipient.
      required:
        - action
        - status
      additionalProperties: false
    BaseError:
      title: BaseError
      type: object
      properties:
        message:
          type: string
          description: A message describing the error that occurred.
      required:
        - message
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer

````