# Be able to specify a key prefix when downloading secrets

**URL:** <https://community.doppler.com/t/be-able-to-specify-a-key-prefix-when-downloading-secrets/525>\
**Category:** Feature Requests\
**Created:** [February 20, 2022, 3:14pm UTC](https://community.doppler.com/t/be-able-to-specify-a-key-prefix-when-downloading-secrets/525 "2022-02-20T15:14:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon88019548](https://avatars.discourse-cdn.com/v4/letter/a/b19c9b/32.png) [@anon88019548](https://community.doppler.com/u/anon88019548)\
**Post date:** [February 20, 2022, 3:14pm UTC](https://community.doppler.com/t/be-able-to-specify-a-key-prefix-when-downloading-secrets/525/1 "2022-02-20T15:14:28Z")

</div>

Would be great to be able to inject a key-prefix when downloading secrets, e.g.

```auto
doppler secrets download
  .doppler/doppler.dev.json
  -p example-project
  -c dev
  --key-prefix MYSAMPLE_

```

Why? To be able to separate secrets being provided by Doppler CLI (via `doppler run --fallback`), without having to store a specific key-prefix in the Doppler backend.

In my case, used to provide specific secrets via a custom configuration provider in .NET, which then can work both against offical API but also against Doppler CLI provided values, from fallback file.

---

<div class="post-metadata">

**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\
**Post date:** [February 22, 2022, 8:49pm UTC](https://community.doppler.com/t/be-able-to-specify-a-key-prefix-when-downloading-secrets/525/2 "2022-02-22T20:49:24Z")

</div>

Hi @anon88019548!

Thanks for submitting this suggestion! I can definitely see how this could be useful in a variety of situations. I’ve passed this along to our Product team!

Regards,  
-Joel