Skip to main content
VoicePing API Access and Integration — query meeting transcripts from your backend

​
Query VoicePing Transcripts From Your Backend

API Access is for server-to-server workflows — scheduled exports, CRM sync, dashboards, compliance archives. You create an API key in your workspace, grant it a set of scopes, and your backend calls the VoicePing API with a standard bearer token. If a person is asking questions through an AI client, use MCP Access instead. 
If a person is asking questions, use MCP Access.
If a server is fetching data, use API Access.

​
When to use API Access

Use caseExample
Scheduled exportsExport this week’s transcripts every Friday
Internal reportingBuild a weekly meeting summary report
CRM or PM workflowsPush transcript summaries into Salesforce or Asana
Compliance archivesStore meeting records in approved storage
DashboardsFeed transcript metadata into analytics systems

​
Create an API key

  1. Open workspace settings → External Access → API Access.
  2. Enable API Access Mode if it’s not already on.
  3. Click Create API key.
  4. Choose a name, the allowed IP address (recommended), the scopes the key needs, and a validity period.
  5. Copy the generated key immediately and store it in your secret manager. The full key is shown only once.
Create API key modal showing name, allowed IP, scopes, and validity fields
Never commit API keys. Keep them in environment variables or your secret manager. For extra safety, lock each key to a specific allowed IP address in the create-key modal — any request from another IP will be rejected even if the key is leaked.

​
Authenticate requests

Every request authenticates with a bearer token against https://api.voiceping.io: 
GET /api/v1/transcripts/search?q=pricing&limit=10 HTTP/1.1
Host: api.voiceping.io
Authorization: Bearer <VOICEPING_API_KEY>
Set the key once as the VOICEPING_API_KEY environment variable, and the samples below will pick it up automatically.

​
Quickstart — call the API in your language

The same two-step flow — search transcripts, then fetch one — in four languages. TypeScript is shown first; switch tabs for your stack. 
// Requires Node.js 18+ (for built-in fetch)
const apiKey = process.env.VOICEPING_API_KEY!;
const base = "https://api.voiceping.io/api/v1";
const headers = { Authorization: `Bearer ${apiKey}` };

// 1. Search transcripts
const searchRes = await fetch(
  `${base}/transcripts/search?q=pricing&limit=10`,
  { headers },
);
const { transcripts } = await searchRes.json();

// 2. Read the first result in full
const detailRes = await fetch(
  `${base}/transcripts/${transcripts[0].id}`,
  { headers },
);
const transcript = await detailRes.json();

console.log(transcript.title, transcript.content);

​
Next steps

External Access overview

Back to scopes, lifecycle controls, and event logs that apply to both MCP and API.

MCP Access for AI clients

If a person is asking questions through Claude, ChatGPT, Codex, Claude Code, or Gemini CLI, use MCP Access instead.