Pulze API

Name: Pulze API API
Brand: Pulze API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingbearer7 EndpointsREST

For 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.

Quickstart

Get started with Pulze API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"review upcoming calendar events"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Pulze API API.

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

GET STARTED

Start building with Pulze API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Pulze API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Pulze API API for, with concrete tasks.

★ 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.

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.

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.

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 the Jentic vault. The OAuth flow itself is started via /oauth-authorize and completed with /oauth-token.

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

7 endpoints — jentic publishes the only available openapi specification for the pulze api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Pulze bearer tokens and OAuth refresh tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution access, and tokens are injected at request time so they never enter the LLM context window.

Intent-based discovery

Agents search by intent (for example, 'join a meeting' or 'review my upcoming calendar events') and Jentic returns the matching Pulze operations with their input schemas, including the OAuth callback parameters when calendar connection is needed.

Time to first call

Direct Pulze integration: 1-2 days for OAuth handling, bearer token storage, and event mapping. Through Jentic: under 1 hour once a Pulze bearer token is stored, since Jentic handles credential injection.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Calendly

Scheduling automation focused on booking links rather than meeting attendance.

Pick Calendly when the goal is booking new meetings; pick Pulze when the goal is to attend, review, and capture context from existing meetings.

Alternative

Fireflies.ai

Meeting transcription and notes platform with bot-based attendance.

Choose Fireflies for established transcription pipelines; choose Pulze when tighter integration with Pulze-managed records is needed.

Complementary

Zoom

Underlying meeting platform that Pulze copilots may join.

Use Zoom for meeting hosting and Pulze for meeting attendance, review, and record capture on top.

FAQs

Specific to using Pulze API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.