The Weflow Public API gives you programmatic access to the data Weflow Conversation Intelligence captures from your meetings — recordings, participants, video URLs, comments, clips, and interaction metrics. You can use it to push call data into a data warehouse, build custom dashboards, sync recordings into internal tools, or trigger workflows in other systems.

This article walks through how to authenticate, what's available today, and what's coming in the early May 2026 release.

The full interactive reference lives at api.getweflow.app/api/v1/docs.

To use the API you'll need:

The API base URL is:

Every request must include your API key in the Authorization header as a Bearer token:

If the key is missing or invalid, the API returns a 401 Unauthorized response. If your workspace doesn't have API access enabled, list endpoints return 403 Forbidden — in that case, contact support to enable it.

The API is rate limited per workspace. If you exceed the limit, you'll receive a 429 Too Many Requests response. We recommend implementing exponential backoff for any production integration and batching reads where possible (for example, paginating with a sensible page size rather than fetching one record at a time).

Everything in the API today is centered on recordings — the meetings Weflow has captured, transcribed, and analyzed. Each recording has a unique uid (UUID) that you'll use across all the endpoints below.

Returns a paginated list of recordings for your company, newest first.

Query parameters:

The response includes data (the recordings), total, nextCursor, and hasMore. To paginate, pass nextCursor back in your next request as the cursor parameter — and keep going while hasMore is true.

Example:

Returns full metadata for one recording, including:

This is the endpoint you'll typically call to enrich a recording in your system after spotting it in the list endpoint.

Returns pre-signed S3 URLs for the recording video:

Important: The URLs expire after 1 hour. Don't store them long-term. If you need a fresh URL, re-call this endpoint at request time.

Returns threaded comments left on the recording. The response is a flat list, but each comment includes a parentCommentUid and a replies array containing the UIDs of its replies — so you can reconstruct threads on your side.

Each comment includes the author (userUid, userName), timestamp position in the recording (timestampSeconds), the rich-text content, and the character range it's anchored to (startChar, endChar).

Returns all clips someone has saved from the recording. Each clip has a start and end (in seconds), a title, the text it covers, and the user who created it.

Useful for surfacing customer-highlighted moments, building libraries of objection-handling examples, or syndicating clips to enablement tools.

Returns per-participant conversation analytics:

These are the same metrics that power the coaching insights in the Weflow app — pulling them via API is how teams typically build custom rep scorecards or feed coaching data into a BI tool.

GET /recordings/{uid}/transcript

Returns the full transcript for a recording, grouped by speaker, with per-word timestamps where available. Each segment includes:

Returns an empty array if transcription never produced output (for example, a meeting with no audio captured).

Common uses: feeding transcripts into your own LLM workflows, archiving meeting content in a knowledge base, running custom search across calls, or training internal models on your sales conversations.

GET /recordings/{uid}/scorecards

Returns all cached scorecards for a recording, one per coaching template that has been run against it. Each scorecard contains:

Useful for piping scorecard outcomes into Salesforce as custom object records, building aggregate reporting across reps or teams in your BI tool, or triggering workflows when specific criteria fail (e.g., notify a manager when "next steps confirmed" is rated low).

GET /recordings/{uid}/trackers

Returns every tracker that has at least one match on the recording, along with the matches themselves. Each match includes the matched phrase, the keyword that triggered it, and its position (index) in the transcript.

Use this to surface where competitors, pricing terms, objections, or any other tracked keywords came up across your calls without having to parse the transcript yourself.

GET /recordings/{uid}/summary

Returns the AI-generated summary for a recording, based on a specific summary template.

Query parameters:

The response includes the summaryTemplateUid, the overall summary text, and a list of sections. Each section has a title and timestamped items linking back into the recording.
​

Returns 404 if the recording or template isn't found, or if a summary couldn't be generated for that combination.

GET /summary-templates

Returns every summary template available to your company, with uid, name, and an isDefault flag. Use a returned uid as the templateId query parameter on /recordings/{uid}/summary to fetch the corresponding summary.
​

This is the endpoint to call first if you want to generate multiple summary flavors per recording (e.g., one for CRM sync, one for executive review).

Errors follow a consistent shape:

Common status codes:

For most use cases, the flow looks like this:

If you run into anything unexpected — missing data, unclear errors, or a use case the API doesn't yet support — reach out to support@getweflow.com or use the in-app chat. We read every API feedback ticket and use it to prioritize the roadmap.