# Generating a Vendor API Token

**URL:** <https://community.replicated.com/t/generating-a-vendor-api-token/29>\
**Category:** Packaging an application\
**Created:** [March 6, 2018, 7:24pm UTC](https://community.replicated.com/t/generating-a-vendor-api-token/29 "2018-03-06T19:24:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![marc](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/marc/32/7_2.png) [@marc](https://community.replicated.com/u/marc)\
**Post date:** [March 6, 2018, 7:24pm UTC](https://community.replicated.com/t/generating-a-vendor-api-token/29/1 "2018-03-06T19:24:18Z")

</div>

To interact with the [vendor API](https://replicated-vendor-api.readme.io/v1.0/reference)  
(anything that is available in the vendor web portal is available in the API) you’ll need to create API tokens. API tokens identify your team and depending on your needs the API token can be read or read/write. Using the API you can automate most of your development and license issuing workflows.

After you have created your API token use it in the `Authorization` header for vendor API calls.

```auto
curl --header "Authorization: API-TOKEN" https://api.replicated.com/vendor/v2/licenses

```

To create an API token you use your [Replicated - Vendor](https://vendor.replicated.com/team) page.

![Generate API Token](https://yyz2.discourse-cdn.com/flex030/images/post-screens/generate-token.png)