canonical: https://jentic.com/apis/base.customerpulze.com/customerpulze

# Base Customerpulze Pulze API

Jentic publishes the only available OpenAPI specification for the Pulze API, keeping it validated and agent-ready. Pulze (Zocra AI) is a meeting and calendar productivity API delivered via Supabase Edge Functions, exposing endpoints to join meetings, review upcoming calendar events, create and import records, and run an OAuth 2.0 authorization flow for connected calendars. The API is targeted at AI assistants and meeting copilots that need to coordinate scheduling, capture meeting context, and synchronise records across users.

## For AI agents

Join meetings, review calendar events, create and import records, and connect calendars via OAuth in the Pulze meeting productivity platform. Built for AI meeting copilots and scheduling assistants.

## Scope

Does not handle video meeting hosting, transcription storage, or CRM-side record routing - use for meeting attendance, calendar review, and record import via Pulze only.

## Capabilities

- Join a Pulze meeting on behalf of a user
- Review upcoming calendar events for a connected user
- Create new structured records tied to a user or meeting
- Import records in bulk through GET and POST variants of the records endpoint
- Run the Pulze OAuth 2.0 authorization flow to connect a calendar
- Exchange an OAuth authorization code for an access token

## Use cases

### AI Meeting Copilot Joining Sessions

Wire an AI meeting copilot to join Pulze-managed meetings via POST /meeting-join, where the copilot captures discussion context and produces follow-up records. The Pulze layer handles the join orchestration and links the meeting to the connected calendar account, leaving the copilot free to focus on transcription and summarisation. Suitable for sales, customer success, and recruiting workflows.

Example prompt: POST /meeting-join with the meeting identifier and the user's connected calendar context, then confirm the join status returned by the API.

### Calendar Review and Daily Briefings

Surface a daily briefing of upcoming calendar events through POST /calendar-review, summarising attendees, durations, and meeting context for the user. This pattern works well with morning email briefings, Slack summaries, or in-app prep cards before each meeting. The endpoint reads from the user's connected calendar via Pulze, which sits on top of Google or Microsoft OAuth integrations.

Example prompt: POST /calendar-review with the user identifier, then summarise the next five meetings with attendee count and duration in a daily briefing.

### Record Creation and Bulk Import

Create individual records via POST /create-record after meetings or pull records in bulk through GET /import-records and POST /import-records for migrations and backfills. This supports onboarding flows where existing data must be loaded into Pulze, as well as ongoing capture of meeting outputs as structured records. Records can be linked back to specific calendar events for later review.

Example prompt: POST /create-record with the meeting context and a structured payload, then GET /import-records to verify the new record is reflected in the user's record list.

### AI Agent Calendar Assistant via Jentic

Run an AI calendar assistant that connects a user's calendar via Pulze OAuth, then reviews events and joins meetings on demand. Through Jentic the agent searches for an intent like 'review my upcoming calendar events', loads the right Pulze operation, and executes the call with the bearer token held in your Jentic One instance. The OAuth flow itself is started via /oauth-authorize and completed with /oauth-token.

Example prompt: Search Jentic for 'review upcoming calendar events', execute POST /calendar-review for the current user, and respond with a list of the next three meetings and their attendees.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/meeting-join` | Join a Pulze meeting |
| POST | `/calendar-review` | Review upcoming calendar events |
| POST | `/create-record` | Create a new record |
| GET | `/import-records` | Get records data |
| POST | `/import-records` | Perform actions on records |
| GET | `/oauth-authorize` | Start the OAuth 2.0 authorization flow |
| POST | `/oauth-token` | Exchange an authorization code for an access token |

## Key resources

- **Meetings** — Operations to join meetings on behalf of connected users
- **Calendar** — Calendar review endpoints surfacing upcoming events
- **Records** — Create and import records tied to users and meetings
- **OAuth** — OAuth 2.0 authorization flow endpoints to connect external calendars

## Why Jentic

- **Setup:** Wiring the Pulze API by hand means managing a bearer token plus OAuth refresh flow, running the oauth-authorize and oauth-token exchange, and posting to the meeting and record endpoints yourself. Through Jentic you install once, import the Pulze API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Pulze takes its targets in the request body rather than as a resource in the URL path, so scope the agent to the operations it needs, such as reviewing the calendar or importing records. You choose that operation set, so joining a meeting or creating a record are not included unless you add them.
- **Credential handling:** Your Pulze bearer and OAuth refresh tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'join a meeting' or 'review my upcoming calendar events', and Jentic returns the matching Pulze operation with its input schema, including the OAuth callback parameters when calendar connection is needed, so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Calendly** — Scheduling automation focused on booking links rather than meeting attendance.
- **Fireflies.ai** — Meeting transcription and notes platform with bot-based attendance.
- **Zoom** — Underlying meeting platform that Pulze copilots may join.

## FAQ

### Why is there no official OpenAPI spec for the Pulze API?

Pulze (Zocra AI) does not publish an OpenAPI specification for its Supabase Edge Functions surface. Jentic generates and maintains this spec so that AI agents and developers can call Pulze via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Pulze API use?

The Pulze API uses HTTP bearer token authentication. Each request includes an Authorization header carrying a Pulze-issued bearer token. When called through Jentic, that token is held in the encrypted vault and injected at execution time, so the agent's context never sees the raw secret.

### How do I connect a user's calendar to Pulze?

Start the OAuth flow with GET /oauth-authorize, redirect the user to the returned authorization URL, then exchange the resulting code for an access token via POST /oauth-token. Once connected, the user's calendar is available to the calendar-review and meeting-join endpoints.

### Can a Pulze copilot join meetings automatically?

Yes. POST /meeting-join with the meeting identifier and connected user context to have a Pulze-managed copilot join on behalf of the user. The endpoint coordinates with the underlying calendar provider so that the copilot is admitted as a participant.

### What are the rate limits for the Pulze API?

Pulze does not publish formal numeric rate limits for its Edge Functions surface. Because the endpoints orchestrate external meeting and calendar providers, prefer event-driven calls (after a webhook or scheduled trigger) over continuous polling, especially for /calendar-review and /import-records.

### How do I review upcoming calendar events through Jentic?

Install the Jentic SDK with pip install jentic, search for 'review upcoming calendar events', and execute POST /calendar-review. Jentic injects the bearer token, calls Pulze, and returns the structured event list for the agent to summarise.

### Can I limit what my agent is allowed to do with the Pulze API?

Yes. Because you run Jentic One yourself, your own rules decide which Pulze operations and credentials your agent can use, and Pulze takes its targets in the request body rather than in the URL path, so you scope the agent to just the operations it needs. You might allow only calendar review through POST /calendar-review and record import through GET and POST /import-records, while leaving out POST /meeting-join and POST /create-record unless you add them. The stored bearer and OAuth tokens are injected at execution time only for the operations you have permitted.