Overview

Developer and API updates may affect credentials, permissions, endpoints, or integration behavior and should be reviewed before deployment.

This article is written as a practical reference for developer and api updates. Follow the steps in order the first time, then use the headings and screenshots as landmarks when you return later. The screenshots reflect the current Open Accessible Cloud layout shown in September 2026, so labels may move slightly as the dashboard evolves.

Where to look in the dashboard

Use the interface landmarks below to get to the right place before making changes. The screenshots are included as guidance so you can match the documentation to what you see in the dashboard.

Organization API keys have their own management screen.
Organization API keys have their own management screen.Use the API Keys tab to review organization-scoped credentials and expiration information.
Personal tokens expose permission controls.
Personal tokens expose permission controls.Personal API Tokens let a user choose create, read, delete, and update permissions. Release notes that change permissions should be reviewed before rotating or recreating a token.

Before you begin

Confirm that you are signed in to the correct account and, when applicable, that the organization selector in the upper-right corner shows the organization you intend to manage. If you work with multiple websites, verify the domain before changing settings.

For changes that can affect a live site, take note of the current configuration first. A screenshot, copied setting value, or short change note makes rollback much easier. Avoid changing unrelated options at the same time; smaller changes are easier to verify and troubleshoot.

How to review an update safely

Read release notes with your own deployment in mind. Pay special attention to changes involving loading behavior, API authentication, saved preferences, widget appearance, or browser support because those areas can affect integrations even when the visible feature change seems small.

For production sites, test an update against a representative set of pages before considering the rollout complete. Keep a note of the version or date you tested so future troubleshooting starts from a known point.

Step-by-step workflow

  1. Find the release or date that applies to your deployment.
  2. Scan for areas you use. Pay attention to widget UI, browser behavior, authentication, API permissions, and saved preferences.
  3. Test impacted workflows in staging or a controlled page.
  4. Check the browser console and network requests if behavior changes unexpectedly.
  5. Document the tested version. This makes later troubleshooting much faster.

How to verify the result

Do not stop at the saved confirmation. Reload the relevant page and confirm the visible state matches what you intended. If the change affects authentication, open a fresh browser session. If it affects a website, test the public page as a visitor rather than only the dashboard.

For user-facing changes, check with keyboard input, browser zoom, and a narrow mobile viewport. Watch for overlapping fixed controls, clipped dialogs, focus that disappears off-screen, or settings that reset unexpectedly after navigation.

Troubleshooting

If the dashboard does not match these screenshots, first confirm you are in the correct organization and account. UI labels can also change over time, so look for the same concepts—Websites, API Keys, Secrets, organization settings, or Profile & 2FA—even if the exact placement has moved.

For website problems, check the browser developer console and network panel. Look for blocked scripts, 404 responses, Content Security Policy errors, or requests being stopped by a consent manager or extension. For account problems, try a private window and verify that the email address and organization membership are correct before resetting credentials.

Use descriptive names for websites, keys, tokens, secrets, and team roles. Clear names reduce the chance of editing the wrong resource and make audits easier months later. Avoid putting sensitive values into screenshots, tickets, documentation, or public source repositories.

Review access periodically. Remove old sessions, unused credentials, and team members who no longer need access. For production integrations, document where each credential is used and who is responsible for rotating it.

Next steps

After completing developer and api updates, return to the documentation home page and use search to find the next related workflow. Search accepts normal phrases, so queries such as “website branding,” “2FA,” “API token,” or “installation” will surface related guides.

If you are troubleshooting, keep the page URL, browser name, approximate time, and a concise set of reproduction steps. Those details make it much easier to distinguish an account configuration issue from a website integration issue.