# Sending parameters to an API triggered workflow

**URL:** <https://discuss.circleci.com/t/sending-parameters-to-an-api-triggered-workflow/28882>\
**Category:** Build Environment\
**Created:** [March 9, 2019, 11:17pm UTC](https://discuss.circleci.com/t/sending-parameters-to-an-api-triggered-workflow/28882 "2019-03-09T23:17:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidbai87](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/davidbai87/32/21622_2.png) [@davidbai87](https://discuss.circleci.com/u/davidbai87)\
**Post date:** [March 9, 2019, 11:17pm UTC](https://discuss.circleci.com/t/sending-parameters-to-an-api-triggered-workflow/28882/1 "2019-03-09T23:17:50Z")

</div>

I’m trying to get CircleCI 2.1 integrated with Phabricator. I’ve got it working where the build on phabricator properly triggers the right workflow via the instructions here: [https://circleci.com/docs/api/v1-reference/#new-project-build](https://circleci.com/docs/api/v1-reference/#new-project-build).

The problem is that Phabricator needs us to send them a message telling them the build has either passed or failed, and in order to do that, we need to pass in the ID of the phabricator build. I was hoping to be able to just pass that in the initial API call, but the Trigger a new build by project API doesn’t allow build\_parameters. Is there another way to do this? Either through circleci or bypassing circleci in some way.

---

<div class="post-metadata">

**Author:** ![ndintenfass](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ndintenfass/32/156_2.png) [@ndintenfass](https://discuss.circleci.com/u/ndintenfass)\
**Post date:** [March 10, 2019, 2:01am UTC](https://discuss.circleci.com/t/sending-parameters-to-an-api-triggered-workflow/28882/2 "2019-03-10T02:01:04Z")

</div>

Not yet, but we are working on adding parameters to api triggered runs.

---

<div class="post-metadata">

**Author:** ![cpanato](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/cpanato/32/22019_2.png) [@cpanato](https://discuss.circleci.com/u/cpanato)\
**Post date:** [July 6, 2019, 4:27pm UTC](https://discuss.circleci.com/t/sending-parameters-to-an-api-triggered-workflow/28882/3 "2019-07-06T16:27:00Z")

</div>

hello, any update when we can trigger a job using the api and passing some custom parameters?

thanks!

---

<div class="post-metadata">

**Author:** ![simesy](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/simesy/32/23500_2.png) [@simesy](https://discuss.circleci.com/u/simesy)\
**Post date:** [October 25, 2019, 1:40am UTC](https://discuss.circleci.com/t/sending-parameters-to-an-api-triggered-workflow/28882/4 "2019-10-25T01:40:48Z")

</div>

I was able to pass FOO with:

```auto
curl -u ${MY_TOKEN}: -d build_parameters[CIRCLE_JOB]=ETC -d build_parameters[FOO]=bar https://circleci.com/api/v1.1/project/github/ETC/ETC/tree/ETC

```

Edit - oh you’re talking about a workflow, not a job