This page answers common questions about the Uber Ads API. If your question isn’t covered here, please reach out to our developer team.

¶ Is the client credentials grant supported?

No. We do not currently plan to support the client credentials authorization flow. If this is a requirement for your integration, please reach out to our developer team.

¶ Does the authentication method differ from the Promo API?

The two are largely the same. The key difference is that the Promo API requires an additional step to request access at the store level, on top of requesting access to the user. The Ads API does not require store-level authentication.

¶ What is the data freshness for the reporting APIs?

For most reports, data is refreshed approximately every 10 minutes.

¶ How are ad accounts set up, and how are stores linked to an account?

It depends on the type of ad account:

• Traditional ad account (common for enterprise merchants): The stores linked to the account are selected during account setup. Merchants request these changes through their Account Manager.
• Store group ad account (common for SMB merchants who have not set up a traditional ad account): This account type is created automatically and links to every store the merchant can access in Uber Eats Manager. To gain access to additional stores, merchants contact Uber support or their Account Representative.

¶ Can a single store be linked to more than one ad account?

Yes. While one ad account can be linked to many stores, a single store can also be linked to multiple ad accounts, including multiple traditional ad accounts and multiple store group ad accounts.

¶ Will the API support creating and pushing creatives to ad campaigns?

Custom creatives will not be available at the initial launch (February 2026). We plan to add this capability in a later release.