https://app.eraser.io/api), using an API token that a team admin (or an organization admin) creates in Eraser. Configview sends only GET requests. It never calls the render, create, update, archive or delete endpoints.
You will end up with 1 required secret (ERASER_API_TOKEN) and 2 optional ones (ERASER_TEAM_IDS, ERASER_AUDIT_API_KEY) in Configview when setup is complete.
Scope of this integration today. Configview reads the teams, the folders, metadata of every file (id, team, author id, folder, dates and the link-access setting), and on the Enterprise plan the members with their last 30 days of use, per-team usage totals and the audit log. It never reads or stores file content, diagrams, file links, AI prompts or generated output. A file title is kept only for files that anyone with the link can open, so a public file can be found and turned off.
Read this first: the token cannot be read-only
Eraser API tokens have no scopes. A team token can read, create, change and archive files in its team, and generate diagrams (which uses AI credits). Configview only sends read calls, but Eraser cannot enforce that. An organization API token covers every team. Tokens do not expire; delete the token in Eraser to cut access at once. API tokens exist on paid plans only.What the Eraser API does not tell Configview
There is no member list, role, admin flag, seat count, pending invite, 2FA or SSO status in the REST API. SCIM exists for Enterprise customers, but its token is the one your identity provider uses to provision accounts, so Configview does not use it. Roster questions are answered from the Enterprise usage report, which lists members with their email and activity. On other plans the roster tables stay empty. File authors, folder creators and audit actors are Eraser user ids, not email addresses, and no endpoint maps an id to an email. Configview therefore cannot say whose email owns a file; it can say which author ids have stopped updating files.What you need
- A paid Eraser plan (Enterprise for members, usage and the audit log)
- A team admin to create a team token, or an organization admin to create an organization token
Step 1: Open the Eraser page in Configview
https://{companyname}.configview.com/admin/integrations/eraser
Step 2: Create the token
- In Eraser open Team settings, then API Token, and click Generate Token. For several teams, an organization admin can instead open the Organization Dashboard, then API tokens, and create one organization token.
- In Configview paste it into
ERASER_API_TOKENunder Credentials and click the save icon. - Optional: set
ERASER_TEAM_IDSto a comma separated list of team ids to read only those teams. Leave it empty to read every team the token can act on. - Optional, Enterprise only: ask Eraser support for the tenant level audit API key and paste it into
ERASER_AUDIT_API_KEY. It is different from the team token. Without it the audit log is skipped.
Step 3: Connect and verify
- Click Connect. Configview creates its tables and schedules every collector at your default run time:
- Click Verify now. The health check reads the secret and calls
GET /api/teams.
Retry-After header.
Data Tables
Each table has arun_at column. Files and audit logs keep only the newest run; the others keep history.
Rate limits
Eraser publishes no rate limit. Configview paces at 60 requests per minute, reads files 500 per page and retries a 429 after theRetry-After header (30 seconds if absent). A team with 50,000 files needs about 100 file requests.
Known gaps and things to check on the first run
These come from Eraser’s published API docs; no live tenant has been tested yet.- Team id on every call. Configview passes
teamIdon every call, discovered fromGET /api/teams. Whether a team token accepts its ownteamIdis assumed. - Author format. The docs say
authoris a user id. If Eraser returns an email, the same column holds it. - Link access values.
publicly-viewable,publicly-editableandanyone-with-link-can-editcount as public.sso-readableandsso-editableneed a sign-in and are not counted as public. - Folders.
recursive=trueis sent so nested folders are included; the response is read as a plain array. - Usage report. Only on the Enterprise plan;
lastActiveis empty for anyone with no file view in the 30 day window, so it is not a true last sign-in. An organization token is asked once per team. - Audit log. Needs the separate audit key. Event metadata (it holds file names) is not stored. Configview reads the last 30 days, up to 300 pages of 1000 events.
- Page size and ordering. Files are requested newest-updated first, 500 per page, until
nextCursoris null.