Business and plugins

    Disable or Delete a UPCS API Key

    Learn how to disable or delete a UPCS API key in the partner panel, what stops working straight away, and how to replace a key safely.

    Updated 14 October 2026 · 2 min read

    You can switch off a UPCS API key at any time from the partner panel. Do this when a site is retired, when a key may have been exposed, or when you are replacing it with a new one.

    Disable or delete

    • Disable when you may want the key back, or while you investigate. The key stays in the panel but no longer works.
    • Delete when you are sure the key is no longer needed. Create a new key if you need access again.

    Steps

    1. Sign in to the partner panel.
    2. On the API keys card, find the key by its name. Clear names make this easy; see naming and separating keys.
    3. To disable it, switch off the Enabled toggle on that key. Switch it on again to restore it.
    4. To delete it, choose the bin icon and confirm with Delete key. Deleting cannot be undone.

    What happens afterwards

    Anything using that key is cut off at once:

    • Plugin checkout maps stop working until you enter a different key in the plugin settings.
    • Embedded maps that depend on the key lose their sessions immediately.
    • Server requests and new session requests return a 401 with the message "Invalid or inactive API key" (no code). Maps already running report key_inactive. See error codes explained.

    Replace a key without downtime

    1. Generate a new key.
    2. Update your plugin settings or server configuration with the new key.
    3. Confirm the integration works, for example with the plugin's connection test.
    4. Disable or delete the old key.

    If one key is shared by several integrations, disabling it affects all of them. That is a good reason to keep separate keys per site when the sites have different owners or risk levels.

    Frequently asked questions

    What error appears after a key is disabled?

    Server requests and new session requests made with a disabled key are rejected with a 401 and the message Invalid or inactive API key. A map that is already running reports the code key_inactive through onError.

    Do embedded maps stop immediately?

    Yes. Disabling a key immediately stops sessions that depend on it.