Wistia
Move briefs, assets and sign-offs through Wistia without chasing between tools.
17 ways to read, 2 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Wistia, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Import media from URLApproval by rule
- Update media detailsApproval by rule
- List account stats by dayRead
Example flow
- Wistia · List account stats by dayDone
- Wistia · Import media from URLNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Wistia.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Wistia
- Wistia's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Wistia media, folders, subfolders, captions, tags and stats (account, folder, media, daily and engagement), plus media metadata updates and URL imports.
Wistia API docs- Source actions
- 17
- Destination actions
- 2
- Data types
- 15
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Account daily stats1
- List account stats by daySourceIncremental
Account-wide loads, plays and hours watched per day between two dates (inclusive).
Account stats1
- Get account statsSource
Account-wide loads, plays and hours watched.
Background jobs1
- Get background job statusSource
Status of an asynchronous Wistia job, such as a URL import.
Captions2
- Get captions in a languageSource
A media's captions in one language (JSON with SRT text).
- List captionsSource
Caption tracks across the account (or for one media), with SRT text unless only metadata is requested.
Events1
- List viewing eventsSourceIncremental
Viewing sessions (events) for the account or one media, with percent viewed and country. Viewer personal data is not mapped.
Folder stats1
- Get folder statsSource
Loads, plays and hours watched for the media in one folder (project).
Folders2
- Get folderSource
One folder (previously project).
- List foldersSource
Folders (previously projects) in the account. My Library folders are not included.
Media daily stats1
- List media stats by daySourceIncremental
Loads, plays and hours watched per day for one media between two dates (inclusive).
Media detailed stats1
- Get media statsSource
Loads, plays, play rate, hours watched, engagement, visitors and actions for one media.
Media engagement1
- Get media engagement graphSource
Engagement and rewatch data for one video, as used by Wistia's engagement graph.
Media imports1
- Import media from URLDestinationNot retried automaticallyApproval before production
Queues Wistia to download a media file from a public URL into a folder. Returns a background job to poll.
Media stats1
- Get media embed statsSource
Aggregated embed statistics for one video: page loads, visitors, plays and play rate.
Medias3
- Get mediaSource
One media with status, folder, tags and thumbnail.
- List mediaSource
Media in the account or one folder, filterable by type, tags, name and archive status.
- Update media detailsDestinationProvider duplicate protectionApproval before production
Updates a media's name, description and (replacing) tags.
Subfolders1
- List subfoldersSource
Subfolders (previously media groups) inside a folder.
Tags1
- List tagsSource
Tags in the account with how many media use each.
Access and limits
- Authentication
- Wistia API token
- Plans and access
- Any Wistia account. Only the Account Owner can create API tokens. Each token has its own permissions: reads need Read all folder and media data (and Read detailed stats for stats); updates and imports need Read, update & delete anything.
- Test environment
- Wistia has no sandbox. Use a test folder; imported media count toward the account's media limits.
- Rate limits
- 600 requests per minute per account across api.wistia.com and upload.wistia.com. Over the limit Wistia returns HTTP 429 with Retry-After, which Nexra honours. Move Media allows 10 requests per 5 minutes (not offered).
- Pagination
- page and per_page (default and maximum 100). Wistia returns plain arrays, so a page shorter than per_page ends the list.
- Provider events
- Wistia sends account webhooks for media and upload events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Never deletes, archives, moves, copies, swaps, trims, translates or restores media, and never deletes folders, subfolders, captions, localizations or tags.
- Caption purchases, localizations and extended audio descriptions charge the account and are not offered. Captions are read only.
- Folder, subfolder, sharing, customization, channel and brand writes are not offered, so Nexra never makes a folder public or changes who can see media.
- Binary uploads (upload.wistia.com) are not offered. Import media from a public URL instead; poll background_jobs.get for the result. Imports from vimeo.com and wistia.com are refused by Wistia.
- There is no updatedSince filter. Sort media and folders by updated (descending) and stop at records already seen.
- Stats events drop viewer personal data: IP address, organisation, city, region, coordinates, e-mail, first and last name and user-agent details are never mapped. Visitor keys are pseudonymous Wistia IDs.
- Events are kept for 2 years. Daily stats default to yesterday and today when no dates are given.
Developer reference
- Create the Wistia credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Wistia, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/wistia and the Connections API.