Skip to main content
WISEPIM API access settings with a sample authenticated request for programmatic catalog access WISEPIM API access settings with a sample authenticated request for programmatic catalog access API Access is where you create the keys your own code uses to talk to WISEPIM. A key lets an ERP, a storefront or a sync script read and update one project’s catalog through the WISEPIM Public API, and it also works with the Category Finder API. Where to find it: Settings > API Access. The page header reads “Create API keys for the WISEPIM public API and the Category Finder API.” and the View API documentation button opens the developer docs.
API Access depends on your plan. If the page shows a locked preview instead of the key list, your plan does not include it yet; the note on the page points at the upgrade. Compare plans on the pricing page.

​
What a key can do

Every request to the Public API sends a key as a bearer token:
Three rules shape every key:
  • One project. A key belongs to the project you were in when you created it and can never reach another project.
  • Fixed permissions. You pick the permissions at creation and they cannot be widened later. Need more? Create a new key.
  • Acts on your behalf. The key carries the access of the person who created it. If that person loses access to the project, or is deactivated, the key stops working on the next request.

​
Create a key

Only project owners and admins can manage keys. Other members see the message “Only owners and admins can manage API keys” and have to ask an owner or admin to create one.
1

Pick the project

Keys belong to a project, so switch to the right one in the project switcher first.
2

Open API Access

Go to Settings > API Access and click Create API key in the API keys panel.
3

Name it and choose permissions

Use a name that says which system will hold the key, such as ERP price sync. Then tick the permissions it needs:Mutation permissions require your current edit access and the relevant role permissions. See the full scope catalog, entities and actions and jobs. Existing keys gain no new permissions automatically; create a replacement to expand access.
4

Copy the key

The full key is shown once, right after you create it. Copy it into your secrets manager before you close the dialog; afterwards the list shows only the key’s prefix.
5

Test it

Call GET /me with the new key. It returns the key’s name, permissions and rate limit, and the project it is bound to, so you know the integration is pointed at the right catalog.
Give each integration its own key. When one system is retired or a key leaks, you revoke that single key and nothing else breaks.

​
Limits

  • A project can hold 25 active keys, and one person can hold 10 active keys in a project. The panel shows both counts, for example “3 of 25 active keys in this project.” Revoked and expired keys do not count.
  • Each key may send 600 requests per minute by default. The response headers X-RateLimit-Remaining and X-RateLimit-Reset show where you stand; above the limit the API answers 429 with a Retry-After. Support can raise the limit for a key when a sync needs it.

​
Manage existing keys

Every row in the API keys panel shows the key’s prefix under Key, its Permissions, who created it and when, and Last used (or “Never used”). The state badge reads Active, Revoked or Expired.
  • Rename changes the label only. Nothing about the credential changes.
  • Revoke disables the key immediately. Revoked keys stay in the list so you can see who created what, and they free up a slot.
  • To rotate a key you suspect has leaked: create a new key with the same permissions, switch your integration to it, then revoke the old one.
Treat a key like a password. Send it from your server only, never from browser code or a public repository, and keep it out of source control. Check Last used now and then and revoke keys nobody uses anymore.

​
Developer docs

The Developer docs card on the page links to the Quickstart, Authentication and Category Finder API pages of the developer portal. The full endpoint reference, with request and response schemas and a playground, lives in the API reference of these docs, and the OpenAPI spec can be imported into Postman, Insomnia or a code generator. The Category Finder API returns the Google product category for product titles. Every live key works with it; a key allows up to 20 titles per request and 100 per day.

API reference

Base URL, paging, errors, rate limits and every endpoint with a playground.

Authentication and scopes

How keys are checked on every request and what each permission grants.

Connected Apps

Let an AI assistant reach your catalog through a scoped, revocable connection instead of a key.

Integration settings

Connect e-commerce platforms when you would rather not write code.

Security settings

Protect your account and review where it is signed in.

Settings overview

Find every settings page for your account and project.