# Build Config Validation: Using \`api\_key\` breaks npm deployments

**URL:** <https://travis-ci.community/t/build-config-validation-using-api-key-breaks-npm-deployments/6696>\
**Category:** Build Config Validation\
**Tags:** config-validation\
**Created:** [January 2, 2020, 12:38pm UTC](https://travis-ci.community/t/build-config-validation-using-api-key-breaks-npm-deployments/6696 "2020-01-02T12:38:21Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [January 2, 2020, 2:16pm UTC](https://travis-ci.community/t/build-config-validation-using-api-key-breaks-npm-deployments/6696/2 "2020-01-02T14:16:41Z")

</div>

Duplicate of

> [@Npm deploy failed && missing api\_key, but I have set it](https://travis-ci.community/t/npm-deploy-failed-missing-api-key-but-i-have-set-it/6624):
>
> this is my build history and .travis.yml config: [https://travis-ci.org/DWmister/build-pack/jobs/629531172/config](https://travis-ci.org/DWmister/build-pack/jobs/629531172/config) Also, I don’t know why this happens?, use v1 ‘api\_key’ ----- ‘api\_token’ In addition, I also used the v2. In v2, I know ‘api\_token’ alias: ‘api\_key’,but,Same problem as above [https://travis-ci.org/DWmister/build-pack/jobs/629535399/config](https://travis-ci.org/DWmister/build-pack/jobs/629535399/config) finally,I have set Environment Variables.

---

_[View the full topic](https://travis-ci.community/t/build-config-validation-using-api-key-breaks-npm-deployments/6696)._