Guide 10 · Form ID & EDGAR Next Credentials

How to Save & Verify EDGAR Credentials in BluePrint

Once you have generated your EDGAR Next tokens on the SEC’s EDGAR Filer Management portal, store the workspace Filer API Token and CCC under Filer info › EDGAR account, save your personal 30-day User API Token, run a live credential check with EDGAR, and confirm Section 16 reporter readiness.

Workspace settings
/settings (Company Profile & Defaults)
Corporate credentials
/filings?section=edgar-account (Filer info › EDGAR account)
Section 16 readiness
/ownership/section16/reporters (Ownership › Reporting persons)
Team invitations
/team → Invite member

1. Confirm Workspace Settings & Company Profile

Before entering EDGAR tokens, confirm that your workspace’s registrant name and 10-digit CIK are set correctly.

Step 1

Open Settings in the left sidebar

Click Settings (/settings) near the bottom of the left sidebar. Here you can review your Company Profile, default XBRL taxonomy, and AI assistant preferences. Notice that EDGAR tokens are deliberately separated from general settings so they remain access-controlled under Filer info › EDGAR account.

app.blueprint-filing.com
The Workspace Settings page showing Company Profile, Defaults, and AI Assistant configuration.
The Workspace Settings page showing Company Profile, Defaults, and AI Assistant configuration.Sample data — fictitious company

2. Save the Filer API Token & CCC under Filer info › EDGAR account

Corporate EDGAR credentials are stored once for the workspace under Filer info › EDGAR account (/filings?section=edgar-account).

Step 2

Open Filer info › EDGAR account

Click Filer info in the left sidebar and select the EDGAR account tab. The page is organized into four cards: Filer API token, CCC (CIK Confirmation Code), Your personal EDGAR user token, and Check credentials with EDGAR.

app.blueprint-filing.com
The Filer info › EDGAR account page displaying the four credential cards.
The Filer info › EDGAR account page displaying the four credential cards.Sample data — fictitious company
Step 3

Save or replace the 1-year Filer API Token

In the Filer API token card, paste the 1-year Filer API Token generated on the SEC’s EDGAR Filer Management dashboard and click Save token (or Replace token when rotating an existing token). Once saved, BluePrint encrypts the token with AES-256-GCM and displays only a masked token ID label (derived from the token’s public identifier header or last four characters), the expiration date, and who saved it—never displaying stored secret values in the UI.

app.blueprint-filing.com
The Filer API token card showing a saved token with Replace token and Remove actions.
The Filer API token card showing a saved token with Replace token and Remove actions.Sample data — fictitious company
Step 4

Save or replace the 8-character CCC

In the CCC (CIK Confirmation Code) card, enter the company’s 8-character case-sensitive CCC and click Save CCC (or Replace CCC).

app.blueprint-filing.com
The CCC (CIK Confirmation Code) card showing a saved CCC with Replace CCC and Remove actions.
The CCC (CIK Confirmation Code) card showing a saved CCC with Replace CCC and Remove actions.Sample data — fictitious company

3. Save your personal 30-day User API Token

Under EDGAR Next, every individual who initiates a test or live submission (or runs a live credential check) must present their own personal 30-day User API Token.

Step 5

Click Add your personal token and paste your 30-day token

In the Your personal EDGAR user token card, click Add your personal token. A right-hand drawer opens explaining how to generate your 30-day token on the EDGAR Filer Management dashboard. Paste the token into the Personal user API token field and click Save my token.

app.blueprint-filing.com
The Personal EDGAR user token drawer with step-by-step instructions and the Save my token button.
The Personal EDGAR user token drawer with step-by-step instructions and the Save my token button.Sample data — fictitious company
Save button guard: The Save my token button remains disabled until a token string is pasted into the input field. Your personal token is tied strictly to your user account—other members of the workspace cannot see or transmit with your personal token.

4. Run Check credentials with EDGAR

Before filing day, verify that your saved Filer API Token and personal User API Token are accepted by the SEC’s EDGAR API.

Step 6

Click Check with EDGAR

In the Check credentials with EDGAR card at the bottom of Filer info › EDGAR account, click Check with EDGAR.

app.blueprint-filing.com
The Check credentials with EDGAR card with the Check with EDGAR button.
The Check credentials with EDGAR card with the Check with EDGAR button.Sample data — fictitious company
Step 7

Understand the verification response or refusal banner

If both the workspace Filer API Token and your personal 30-day User API Token are saved and valid, EDGAR confirms that your tokens are active and authorized for the workspace CIK. If you click Check with EDGAR before adding your personal 30-day token, BluePrint displays a clear refusal banner: “No personal EDGAR user API token is saved for your account.”

app.blueprint-filing.com
Clicking Check with EDGAR without a saved personal token displays a clear refusal banner naming the missing personal user API token.
Clicking Check with EDGAR without a saved personal token displays a clear refusal banner naming the missing personal user API token.Sample data — fictitious company

5. Check Ownership readiness & invite teammates

The same workspace Filer API Token and personal 30-day User API Token also power the Section 16 and Section 13 ownership desks.

Step 8

Verify the EDGAR readiness checklist in Ownership › Reporting persons

Open Ownership › Section 16 › Reporting persons (/ownership/section16/reporters) and scroll to the EDGAR readiness card. It checks off the workspace Filer API Token (`Set`), prompts you with Add your personal token if your 30-day token is not yet saved, and lists each reporting person’s CIK, CCC, and POA readiness.

app.blueprint-filing.com
The EDGAR readiness card on Ownership › Reporting persons showing workspace token status and per-reporter readiness.
The EDGAR readiness card on Ownership › Reporting persons showing workspace token status and per-reporter readiness.Sample data — fictitious company
app.blueprint-filing.com
Clicking Add your personal token from Ownership › Reporting persons opens the same personal token drawer.
Clicking Add your personal token from Ownership › Reporting persons opens the same personal token drawer.Sample data — fictitious company
Step 9

Invite teammates without requiring EDGAR tokens up front

When you invite colleagues, auditors, or outside counsel via Team › Invite member (/team), teammates can join the workspace to draft, redline, and review tags immediately—only the person who actually clicks Submit to EDGAR needs a personal 30-day User API Token.

app.blueprint-filing.com
The Invite team member dialog on the Team page.
The Invite team member dialog on the Team page.Sample data — fictitious company

Try this workflow in BluePrint today.

Forms 3, 4 and 5 are always free, Form 144 and Schedules 13D/13G are free on every plan, and every BP-Free workspace includes a one-time AI test-tagging evaluation on your most recent publicly filed 10-K.

Need help with a live filing? Talk to us.