Integrations

Your videos, working
on your own site.

searchferret doesn't stop at its own library. Published links unfurl into playable video in the tools your team already uses. A search widget puts your published videos behind a search box on your website. An embeddable recorder puts a record button in your app. And a search API lets you build whatever the first three don't cover.

14 days free. No card required. Unlimited teammates on every team plan.

Search widget

Video search on your site. One script tag.

Paste one script tag into your website and visitors can search your published videos by what was actually said in them. They type a word, get matching moments with transcript snippets, and jump straight to the right second of the right video.

A floating button, or an inline box
By default the widget adds a small search button in the corner of every page it's on. Prefer it in your layout? Point it at a div and it renders inline instead, wherever you want it.
It searches the words, not just the titles
Results come from the transcripts, along with titles, tags, and folders. If someone said "reset your password" 14 minutes into a video, searching those words finds that moment, with a link that starts playback right there.
Published videos, or your whole library
Out of the box the widget searches only the videos you've published. Give its key the Library search permission and it searches everything else too. Either way, videos marked private are never shown.

The whole integration:

<script src="https://searchferret.com/search-widget.js"
  data-searchferret-key="YOUR_API_KEY" async></script>

Your copy of this snippet, pre-filled with your key, lives in Settings → Integrations.

Embeddable recorder

A record button in your app. Recordings in your library.

Put a screen recorder behind any button on your site or web app. Visitors record their screen and talk it through, and the video lands privately in your library. Nothing for them to install, no account for them to make.

Bug reports that show the bug
A "Report a problem" button in your app replaces three paragraphs of "steps to reproduce" with a 40-second recording of the thing actually happening.
You know who recorded, and from where
Pass the user's name, email, and any metadata from your own app, and it's stored with the recording. The page URL comes along automatically.
Private by default
Recordings arrive in your library unpublished, visible to your team only. Auto-publishing to a public page is a separate permission you grant per key, deliberately.

One script tag, plus your button:

<script src="https://searchferret.com/embed.js"></script>
<button data-searchferret-embed="YOUR_API_KEY">
  Send feedback
</button>

Your copy of this snippet, pre-filled with your key, lives in Settings → Integrations.

Search API

The same search, as an API.

Everything the widget does, you can do yourself. One endpoint returns matching videos with titles, transcript snippets, timestamps, and watch URLs, ready to render however fits your product. Help centres, in-app help, chatbots... if it can make an HTTP request, it can search your videos.

Plain JSON over HTTPS
Send a query, get back matches with everything needed to link a user to the exact moment in the exact video. No SDK required.
Search your whole library, server-side
Keys with the Library search permission can search all your videos, published or not (private videos are never returned). Useful for internal tools and support desks, where the answer often lives in a video you never published.
Built for servers too
Keys without allowed domains work server-to-server only, so you can keep them out of the browser entirely and search from your own backend.

A search, from anywhere:

curl "https://searchferret.com/api/public/search/videos?q=onboarding" \
  -H "x-api-key: YOUR_API_KEY"

Your copy of this snippet, pre-filled with your key, lives in Settings → Integrations.

API keys

One key system behind the rest.

Link previews need no key at all. The widget, the recorder, and the search API are all powered by the same org-scoped API keys, created and managed in Settings → Integrations. You decide what each key can do and where it may be used from.

Domain allowlists
Each key lists the domains it may be used from. A key for your marketing site doesn't work anywhere else, so it's safe to put in your HTML.
Permissions per key
Search, library search, recording, and auto-publish are separate permissions. A key gets exactly the ones you tick, and nothing more.
Cycle or revoke any time
Every key can be disabled, cycled, or deleted from Settings the moment you want it gone. Requests are rate limited per key.

Frequently asked questions.

Pick one.
Paste it. Done.

Create a key in Settings → Integrations, copy the snippet, and your site has video search or a screen recorder before your coffee goes cold.