Use One UPCS API Key Across Plugins and Code

You do not need a different key for each product. A UPCS key created in the partner panel works in the WordPress / WooCommerce plugin, the PrestaShop module, the OpenCart extension and in code that calls the embed or REST endpoints.

What sharing means in practice

When several integrations use one key:

• They all count toward the same hourly request limit, 1,000 per hour by default. See the hourly limit explained.
• Disabling or deleting the key switches all of them off together.
• A leak from one integration exposes the others.

When one key is fine

A single key is reasonable if:

• All sites are owned and managed by the same team.
• Traffic is low and well below the hourly limit.
• You are testing or building a first integration.

When to use separate keys

Prefer separate keys when:

• Sites belong to different clients or business units.
• One site has much heavier traffic than the others.
• You want to retire or rotate access for one site without a risk to the rest.
• A development or staging site should not share production access.

How to split keys

1. Generate a new key for each site or environment, naming it clearly.
2. Replace the key in each plugin or server configuration.
3. Register each site's address under allowed origins if it uses the embeddable map.

More on naming is in name and separate API keys for each site.

A simple rule of thumb

Start with one key while you are learning how UPCS behaves. As soon as a second team, client or high-traffic site arrives, split the keys. Doing it early is easy; doing it after an incident means finding every place the old key was pasted.