Refresh API credentials

Replace the FullClarity API credentials on your NetSuite account with a fresh set — typically after a security rotation, a sandbox refresh, or when troubleshooting Portal-related errors.

When to use this

There are three common reasons to refresh API credentials:

  • Sandbox refresh. A NetSuite sandbox refresh deletes all access keys, so the previously-registered credentials no longer work. You need to re-register the sandbox.
  • Security rotation. If your security team rotates secrets on a schedule, you may want to refresh credentials to a fresh pair.
  • Troubleshooting. If Portal-backed features start failing with authentication errors, re-registering can resolve credential-corruption edge cases.

In all three cases, the steps are the same: re-run the registration flow.

Prerequisites

  • The Portal SuiteApp installed and previously registered
  • Either the Administrator role or the FC Portal Admin role
  • Your NetSuite Company ID

Walkthrough

Walkthrough coming

A step-by-step Scribe walkthrough for credential refresh is being recorded. Track its status in the Scribe register (internal).

API credentials are hidden from users in NetSuite — you can't edit them manually. To replace them, run the registration flow again:

  1. Go to https://my.fullclarity.com/register.
  2. Enter your Company ID and sign in with the Administrator or FC Portal Admin role.
  3. The registration completes and replaces the existing credentials with a freshly-generated pair.
  4. You'll receive the same registration confirmation email as the first-time flow.

What success looks like

  • The registration confirmation email arrives within a few minutes.
  • Portal-backed features (File Storage uploads, Certified Documents, Connect) resume working using the new credentials.
  • Previously-issued signed URLs may still work for their normal 48-hour window — new URLs are signed with the new credentials.

Gotchas

  • Users with active sessions need to sign in again. API credentials are cached in user sessions. After a credential refresh, each user needs to log out and log back in for their session to pick up the new credentials.
  • The old credentials stop working immediately. Don't refresh credentials during a busy upload period unless you're prepared to have users re-authenticate.
  • Re-registration is the only refresh path. There is no separate "rotate credentials" screen — the registration flow is the credential-management flow.
Last Updated: