Account and API keys

Your OpenAuditor account connects your sign-in, API keys, usage counts and batch audits. Use the same email account when returning to an existing audit or managing an integration.

New accounts start free at $0, with no credit card required. To try a business example, go straight to the console. Create an API key when you are ready to connect another application.

Sign in with an email code

1. Open Sign in or Create an account and enter the email address you want to use.
2. Select Send code. Keep that browser window open while you check your inbox.
3. Enter the six-digit code in the browser that requested it, then select Verify and continue.
4. Creating an account opens the console with its preloaded invoice example; signing in opens the account page. If you followed a link to a specific destination, continue there instead.

A code expires after ten minutes, works once and allows at most five attempts. It depends on a challenge stored in the requesting browser, so a code requested in an ordinary window cannot simply be entered in a different browser or private session. Signing in with a new email address creates a separate account after the code is verified.

If the address is wrong or the code has expired, use Use another address or resend. You can request a new code once a minute, subject to additional sign-in limits. Check your spam or junk folder and follow any waiting period shown on the page.

Use the console without creating a key

The console uses your signed-in browser session. Its initial invoice example is ready to inspect; select Run verification when you want to submit it. You can also load another example, paste records or import a CSV or XLSX file without handling an API key. Follow the console guide for those options.

A session lasts up to 30 days. Sign out on the account page ends the current session. If the console reports that the session has ended, sign in again with the same account before continuing.

Create a key for an integration

Open the account page and check the signed-in email before creating a key. If you are new, create an account for API access to return directly to this page after sign-in.

1. On the account page, enter a descriptive New key name, such as “Expense review service.”
2. Select Create key. Use a name of 1 to 60 characters that you can recognize later.
3. Copy the value shown under Copy your new key and save it in your server's secret store or environment configuration.
4. Use it as an Authorization: Bearer credential when calling the API.

The full key is shown only at creation and cannot be retrieved later. The key list shows its name, creation date, expiry date and last-used date. Keep the secret value out of browser JavaScript, source control and shared documents.

A Free account can have five active keys; a paid plan may allow more, and your account page shows the limit in force. Keys expire after 365 days, and we email the account 14 days before each one does. Choose Read-only when creating a key for a dashboard or monitoring job: it can read audits, results and usage with GET requests, and any other request is refused with 403 read_only_key. If you have reached the limit, identify and revoke an unused key before creating another.

Use the quickstart to send a complete example, or import the Postman collection. The authentication guide covers headers and credential errors.

Replace or revoke a key

For a planned replacement, create a new key, update the integration's server-side configuration and confirm that requests succeed. Then select Revoke beside the old key and confirm the action. If the old key has been exposed, revoke it promptly and restore the integration with a replacement.

Revoked or expired keys no longer authenticate requests. Revocation does not delete the account's audits or cancel other active keys. Losing the readable key value requires creating a replacement; the account page cannot reveal it again.

API keys from the same account use the same audit access and quotas. A key created under a different email account does not gain access to existing audits from the first account.

Read your usage correctly

All keys and console activity share the account's limits. The Free plan includes 5,000 items and 1,000 model questions per day, plus 60 authenticated API requests per rolling minute. Your account page shows the applicable allowance if you have upgraded. Daily counts reset at 00:00 UTC. Creating more keys does not increase the allowance.

After either daily allowance is exhausted, you can still read existing audit progress and results, subject to the rolling request limit. New verifications and batches must wait for the daily reset. See Pricing and Limits before scheduling a large run. The billing guide explains paid upgrades when available, invoices and cancellation.

Find the right account for an audit

If an audit cannot be found, check which email account is signed in and which account owns the integration's key. Also check whether the audit was deleted or its result-retention window ended. The current console does not provide an audit-history list; keep the audit id and downloaded results from your review.

Use the batch-audit guide to retrieve a known audit through the API. The privacy notice explains retention and deletion.

Get account help

For sign-in errors, follow Troubleshooting. For an account-deletion request or an unresolved account issue, use the ERP.AI contact page and state that the request concerns OpenAuditor. Describe the issue without sending passwords for your email account, sign-in codes, API keys or session cookies.