Skip to main content
Every key belongs to one organization and carries one access level. What a key can do is fixed when it is created; create a new key to change it.

​
Create a key

Workspace owners and admins on the Pro or Enterprise plan create keys in LocalAds under Settings > API keys. Each key has:
  • a name
  • an access level (see below)
  • an optional expiry: 30, 90, or 365 days
  • an optional monthly credit budget (see below)
The workspace owner is emailed whenever a key is created or revoked. Give every integration or agent its own key so you can revoke it on its own. An expired key receives 401 Unauthorized, the same as a missing or revoked one. Keys without an expiry do not expire.

​
Access levels

Each key is created with one access level:

​
Permissions

Endpoints check these permissions: Every generate permission includes the matching read permission, so a key that starts work can always check on it.
Keys created before September 25, 2026 do not include the videos, chatgpt_ads or amazon_listings permissions, and Settings shows them as custom access. Create a new key to use those endpoints.
A valid key without the required permission receives 403 Forbidden. A missing, disabled, expired, or invalid key receives 401 Unauthorized.

​
Monthly credit budgets

A key can carry an optional monthly credit budget. Once the credits spent by jobs the key started this calendar month (UTC) reach the budget, requests that start new generation return 422 with the code key_budget_exceeded. Reads keep working. The check runs before a job starts, so a single job can finish slightly over the budget. See Credits and spending for the rest of the spending model.
Last modified on September 30, 2026