# How to inject new Env Vars into a CircleCI Rerun (API Workaround)

**URL:** <https://discuss.circleci.com/t/how-to-inject-new-env-vars-into-a-circleci-rerun-api-workaround/54252>\
**Category:** API\
**Created:** [November 27, 2025, 6:09pm UTC](https://discuss.circleci.com/t/how-to-inject-new-env-vars-into-a-circleci-rerun-api-workaround/54252 "2025-11-27T18:09:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rudratrivedi-bs](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/rudratrivedi-bs/32/36821_2.png) [@rudratrivedi-bs](https://discuss.circleci.com/u/rudratrivedi-bs)\
**Post date:** [November 27, 2025, 6:09pm UTC](https://discuss.circleci.com/t/how-to-inject-new-env-vars-into-a-circleci-rerun-api-workaround/54252/1 "2025-11-27T18:09:54Z")

</div>

### 

The `POST /workflow/{id}/rerun` endpoint doesn’t accept new parameters or variables. If you need to pass a one-off variable (like `rerun=true`) to an **existing** workflow ID without triggering a brand new pipeline, you have to hack it via Project Settings.