GitHub Actions API Update Streamlines Workflow Tracking for Developers

Peter Zhang Feb 19, 2026 23:29

GitHub's workflow dispatch API now returns run IDs, eliminating the need for custom polling solutions when triggering automated workflows programmatically.

GitHub Actions API Update Streamlines Workflow Tracking for Developers

GitHub has quietly solved one of the more annoying pain points for developers automating their CI/CD pipelines. The workflow dispatch API endpoint now returns run IDs directly in its response—a small change that eliminates hours of workaround code.

Previously, triggering a workflow via API gave you nothing but a 204 No Content status. You knew the workflow started, but good luck figuring out which run was yours without polling the API repeatedly or building custom tracking systems. That's now fixed.

The update, announced February 19, 2026, introduces a new optional parameter called return_run_details. Set it to true, and you'll get a 200 OK response containing the workflow ID, API URL, and workflow URL. Skip the parameter, and the old 204 behavior continues—backward compatibility preserved.

GitHub CLI users running version 2.87.0 or later get this automatically. Fire off gh workflow run and you'll see the created run's URL plus the gh run view command to check on it. The CLI now defaults return_run_details to true.

This matters for anyone building automation on top of GitHub Actions. Think deployment orchestration systems, batch processing pipelines, or any tooling that needs to track what it spawned. The previous approach—polling the runs endpoint and trying to match timestamps or commit SHAs—was fragile and rate-limit hungry.

The timing is notable. GitHub previewed its Agentic Workflows concept just two days earlier on February 17, signaling deeper investment in programmatic workflow control. And the platform is still recovering reputationally from a major outage affecting hosted runners on February 2 that disrupted CI/CD pipelines across the ecosystem.

For context, GitHub bumped the maximum workflow_dispatch inputs from 10 to 25 back in December 2025, another quality-of-life improvement for complex automation scenarios.

The feature is live now in the REST API. Documentation is available in GitHub's Actions workflow events guide for anyone ready to ditch their custom tracking hacks.

Image source: Shutterstock