Qualcomm® Device Cloud

Authentication Management

QDC supports two authentication methods: ClientId/ClientSecret or API Key.

ClientId / ClientSecret

Used for service account users, contact qdc.support@qti.qualcomm.com to obtain credentials.

API Key

Used for individual users, API keys can be generated by users themselves. The following steps explain how to create one.

If you cannot access the page, contact qdc.support@qti.qualcomm.com to obtain credentials.

Log in to your existing Qualcomm Device Cloud account. If you don't have an account yet, you can create a new one.

Step 2: Navigate to API Key Settings

Locate and select the User Settings section within your account. From there, navigate to the API Keys tab.

QDC Home

Step 3: Generate API key

Once in the API Keys section, click on the "Generate" button to initiate the creation of a new API token.

Newly generated API keys expires in 6 months.
A newly generated API key overwrites existing API key.

QDC Home

Step 4: Use the API key with QDC Public API lib

For detailed instructions on using the API Key, please refer to Sample - Monkey Job.

Terms of Use Privacy Policy Cookie Policy Contact Us

2025 ©Qualcomm Technologies, Inc. and/or its affiliated companies. All rights reserved. References to "Qualcomm" may mean Qualcomm Incorporated, or subsidiaries or business units within the Qualcomm corporate structure, as applicable. Qualcomm Incorporated includes Qualcomm's licensing business, QTL, and the vast majority of its patent portfolio. Qualcomm Technologies, Inc., a wholly-owned subsidiary of Qualcomm Incorporated, operates, along with its subsidiaries, substantially all of Qualcomm's engineering, research and development functions, and substantially all of its products and services businesses. Qualcomm products referenced on this page are products of Qualcomm Technologies, Inc. and/or its subsidiaries. Materials that are as of a specific date, including but not limited to press releases, presentations, blog posts and webcasts, may have been superseded by subsequent events or disclosures. Nothing in these materials is an offer to sell any of the components or devices referenced herein.