Skip to main content
Enterprise only. Perplexity’s admin APIs exist only for Perplexity Enterprise organizations. Free, Pro and Max accounts, and the developer (Sonar) API keys, cannot read audit events or usage analytics, so there is nothing for ConfigView to collect from them. If you are not on Enterprise, skip this integration.
ConfigView reads your Perplexity Enterprise organization through two separate admin APIs on https://api.perplexity.ai, each with its own key that an organization admin creates. ConfigView sends only GET requests. It never changes anything in Perplexity. You can set one or both secrets. A collector whose secret is empty skips itself cleanly, so a customer who only has the Audit API, or only the Analytics API, still gets a working integration.
Scope of this integration today. ConfigView reads structured audit fields only: the actor’s email, the event type, the member, API key or connector the event touched, the IP address and the time. It does not read what anyone asked or what Perplexity answered, file names, or the titles of spaces, skills, workflows or projects.

What you need

  • A Perplexity Enterprise organization and an organization admin
  • For the audit key: audit logging switched on under Organization Settings > Data and privacy > Audit Log Settings. Events are recorded only while it is on, so there is no history from before you enabled it.
  • For the analytics key: the Analytics API switched on in Computer settings
If Create key is missing or says key creation is unavailable for your organization, contact your Perplexity account team to enable the Audit API.

Step 1: Open the Perplexity page in ConfigView

Open ConfigView in a second browser tab and leave it open: https://{companyname}.configview.com/admin/integrations/perplexity

Step 2: Create the keys

Audit API key (optional)
  1. In Perplexity open your organization settings, then Enterprise APIs
  2. Under Audit API > Audit log API keys choose Create key, name it (for example ConfigView) and confirm
  3. Copy the key now. Perplexity shows it once.
  4. In the ConfigView tab paste it into PERPLEXITY_AUDIT_API_KEY and save
The key is read-only with the single scope audit_logs:read, is bound to your organization, and does not expire. Revoke it on the same page to cut ConfigView off. Analytics API key (optional)
  1. In Perplexity open your organization’s Computer settings and find Analytics
  2. Turn on Analytics API, then choose Generate key
  3. Paste it into PERPLEXITY_ANALYTICS_API_KEY in ConfigView and save
Your organization has one active analytics key. Regenerating it revokes the previous one, and turning the toggle off revokes it permanently, so paste the new value into ConfigView whenever an admin regenerates it. The key is analytics-only, free and consumes no API credits.

Step 3: Connect and verify

  1. Click Connect. ConfigView creates its tables and schedules every collector at your default run time:
  1. Click Verify now. The health check tests each key that is set with one small call. An empty key is reported as skipped, not failed. The check fails only if a key that is set is refused, or if both keys are empty.
If a check fails:
  • 401. The key was revoked, regenerated (analytics), or is the wrong kind. Sonar API keys do not work here.
  • 403. The audit key lacks the audit_logs:read scope.
  • 404. Audit logging or the Analytics API is switched off for your organization. The collectors skip quietly until you turn it on.

Data Tables

Each table has a run_at column and keeps only the newest run.

Things worth knowing

No member or key list. Perplexity’s API has no endpoint for members, roles, SSO settings or API keys. Roles show up only as the old and new role in member_role_changed events, and a member appears only when they act or use credits. Audit metadata is filtered. Perplexity’s audit metadata can hold query text, answer text and file names. ConfigView keeps only a short allow-list of structured keys (target member, old and new role, API key id, connector name) and does not collect the content event types at all. Who reads the audit log. Every read through the Audit API is itself an event. ConfigView also requests those (audit_events_accessed) so you can see which key is reading your audit trail, including ConfigView’s own. Complete days only. The Analytics API serves finished UTC days, so today is never included. A zero in a recent day can mean the data has not synced yet. Windows. Audit events: the last 30 days, re-read every run, so a late-arriving event is picked up. Usage: the last 89 days. Rate limits. The Audit API allows 2 requests a second per organization across all audit keys. The Analytics API is limited per organization with no published number. ConfigView paces itself at 60 and 30 requests a minute, honors Retry-After and reads 500 events or 100 member rows per page.

What isn’t collected

  • Queries, answers, uploaded file names, Computer task results and browser-agent actions
  • Space, skill, workflow and project titles
  • API key values
  • Anything for non-Enterprise accounts or Sonar API keys