# Argument order causes issues when fetching artifacts **URL:** \ **Category:** Bug Reports\ **Tags:** api, artifacts\ **Created:** [May 18, 2016, 10:24am UTC](https://discuss.circleci.com/t/argument-order-causes-issues-when-fetching-artifacts/4063 "2016-05-18T10:24:20Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![gfarrell](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/gfarrell/32/2283_2.png) [@gfarrell](https://discuss.circleci.com/u/gfarrell)\ **Post date:** [May 18, 2016, 10:24am UTC](https://discuss.circleci.com/t/argument-order-causes-issues-when-fetching-artifacts/4063/1 "2016-05-18T10:24:20Z")
Part of our deployment process involves fetching a binary from the CircleCI server. This has been working reasonably well (we get random failures which work after several retries but that’s not the issue at hand). Since yesterday, I am now getting the error message “Project not found” for _one_ of the binaries, but not the other (they are different projects) when I try to get a list of artefacts. I am testing this with ```auto curl https://circleci.com/api/v1/project/ORG/PROJECT/latest/artifacts?branch=master&filter=successful&circle-token=TOKEN ``` UPDATE: the project which works is open source, so works without a `circle-token`, whereas the other does not (which makes sense). I have discovered that the `circle-token` is not actually working as `curl` warns me that `circle-token: command not found`. If I change the parameter order, putting `circle-token` **before** `filter` and `branch`, then it works. This bug appeared some time before yesterday (we hadn’t deployed for about a week before that). ---
**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\ **Post date:** [June 18, 2018, 11:34am UTC](https://discuss.circleci.com/t/argument-order-causes-issues-when-fetching-artifacts/4063/2 "2018-06-18T11:34:10Z")