Integrations
Open the Admin Panel Integrations hub to connect EventHub, data warehouse connectors, and the API Console. Availability depends on plan and rollout.
The Integrations hub in the Admin Panel is where administrators connect PetroBench to corporate data systems and open the API Console for the organization.
This Admin Panel surface is rolling out and may not appear in every organization yet. When it is enabled for your plan, you will find it under Admin Panel > API & Integrations. Deep setup guides live in Enterprise Integrations.
Open Integrations
- Switch to Admin Panel
- Open API & Integrations > Overview (label may show as Integrations)
- Review featured connectors and category lists (Oil & Gas, Cloud & Data, Identity & Access, and related groups)
The hub shows totals for available and connected integrations when your org has access.
What you manage here
| Area | Purpose |
|---|---|
| Connector catalog | Browse integrations available to your organization |
| Connection status | See which connectors are enabled or coming soon |
| EventHub | Open sync configuration and logs for an active warehouse connection |
| API Console | Service tokens, webhooks, usage, and client connect configs |
Personal API tokens and Connected apps live under Settings. The Admin Panel hub is the organization-level developer surface.
EventHub and warehouse sync
For EventHub, Snowflake, and related sync workflows, use the Enterprise guides:
From the Admin Panel you typically:
- Open the connected integration card
- Review field mappings, sync schedule, and recent sync logs
- Resolve equipment match reviews when the connector queues low-confidence matches
On an individual synced well, engineers can View source data, Re-pull from source, or Reset from last sync. See EventHub on a Well.
Lower-confidence equipment matches from inbound sync are queued for admin review so engineers do not silently get the wrong pumping unit or rod grade.
API Console
API Console is the in-app home for organization API access. Open Admin Panel > API & Integrations > API Console.
It includes four tabs:
| Tab | Purpose |
|---|---|
| Service Tokens | Mint and manage division-owned tokens for servers and jobs |
| Webhooks | Register HTTP endpoints for platform events |
| Usage | Live request volume, plan limits, and monthly quotas |
| Connect | Copy-ready config for MCP clients and REST |
Usage
Usage shows API request volume, quotas, and token consumption for the current period.
Typical cards include:
- Organization and personal request counts, average response time, and error rate
- Plan limits - requests per minute, division aggregate, concurrent runs, daily token ceiling
- Monthly quotas - reads, writes, simulation runs, and webhook deliveries
- Daily activity plus top endpoints and consumers when traffic exists
Use this tab when diagnosing rate limits, quota pressure, or unexpected API errors. See also Rate limits.
Service Tokens
Service Tokens are long-lived credentials owned by the division, not a person. They keep working after the creator leaves.
Create a service token
- Go to Admin Panel > API & Integrations > API Console
- Open the Service Tokens tab
- Click Create service token
- Enter a Token name (for example,
Nightly Snowflake Sync) - Choose an Expiration (30 days, 90 days, or 1 year)
- Optionally set an IP allowlist
- Select Permissions (scopes) for Wells, Simulations, Equipment, and Organization
- Click Create service token
- Copy the plaintext token immediately - it is shown only once
From the row menu you can rename, rotate, or revoke a token. Each division has a capped number of active tokens (shown as used of total on the list).
Prefer service tokens for scheduled jobs and integrations. Prefer personal API tokens only when a single engineer is calling the API interactively.
Full auth details: API authentication.
Webhooks
Webhooks register HTTP endpoints that PetroBench calls when events occur (for example, well.created or simulation.failed).
- Open the Webhooks tab
- Click Add Webhook
- Enter the endpoint URL and select events
- Save, then use the send/test control to verify delivery
Connect
The Connect tab helps you point MCP clients (Claude, ChatGPT, Cursor), cURL, or Python at your workspace. Copy the config for your client, then replace the API key placeholder with a service token or personal key.
For step-by-step client setup, see Getting started and the MCP reference.
Who can access
| Action | HQ Admin | Division Admin | Region Admin |
|---|---|---|---|
| View Integrations hub | Varies by plan | — | |
| Configure EventHub | Varies by plan | — | |
| Open API Console (Usage, Connect) | Yes (own division) | — | |
| Manage Service Tokens | Yes (own division) | — | |
| Manage Webhooks | Yes (own division) | — |
Related
- Apps for installed applications and marketplace enablement
- Getting started with the API
- API authentication
- Rate limits
- RBAC for who can manage organization settings