One REST API and an embed code. After that your client publishes and replaces videos themselves: no ticket lands on your desk to swap a video.
You ship websites for your clients, and this one wants video: no advertising, no third-party brand, no data leaving Europe. Videas gives you a REST API and an embed code to lay the brick once — then a complete interface, which your client runs afterwards without taking up your team's time.
Videas publishes its integration guides and the reference of its API, generated from its contract: the key, resumable uploads or uploads from a link, editing a media item, publishing on a channel, the errors and the limits are all written out, with their examples.
In Videas, the theme, the accent color and the logo are resolved at playback rather than frozen into the pasted code: your client changes them without a single page of the site moving.
The Videas player shows no advertising and sets no cookie, and the videos stay hosted inside Europe. Nothing goes out to an ad network or to any third party.
Media library, subtitles, analytics and player arrive alongside the API, in an interface that is already written. You have no dashboard to build before your client can use it.
In Videas, every media item gives you a script tag or an iframe to paste as is. The script resizes itself and picks up player updates without being copied again. The REST API, for its part, feeds the library and keeps it current from your own backend, and publishes on the channels.
Logo, accent color, light or dark theme: Videas resolves them at playback, from the workspace preset. Your client changes their brand without you touching a single page.
Your server opens the upload with the key; your client's browser only receives its address and a token that opens that one file and nothing else. The key itself stays with you.
Videas ships the media library, the folders, the permissions, the subtitles and the analytics alongside the API. Your client publishes, replaces and files their videos without any of it turning into a ticket on your side.
The embed code lays the Videas player inside your client's page, as a script tag or an iframe. The visitor never leaves the site and has no account to create.
The logo, the color and the theme come from the workspace settings: Videas applies them at playback, including to embeds that went live months ago.
Every client gets their own workspace in Videas, with their folders, their members and their permissions. You open it, you hand it over, and you step out of the loop.
The Videas player shows no advertising and sets no cookie, and the videos stay hosted inside Europe. That is what your client has to be able to answer on GDPR.
4,000 hof replays moved off Vimeo, played inside WordPress
BTLV moved more than 4,000 hours of replays away from Vimeo, and the embed codes across its WordPress pages were swapped one by one, with no loss of access for its subscribers.
0cookies and no advertising on the embedded player
Bodytime streams its programs inside its own coaching website, with a player in its own colors, and its team runs the catalog from the Videas interface with no particular technical skill.
4brands, each with its own video workspace
Magnard-Vuibert left Vimeo and gave each of its four brands a video workspace; the clips are embedded in digital textbooks, and every editorial team runs its own catalog.
Videas ships neither a plugin nor a ready-made connector: the integration is written, with the embed code or with the API. And the API sends no notification yet: your code polls it to learn that an upload is ready.
€0
per API call, whatever the volume
€0.20
per hour of video stored, every month
€0.02
per gigabyte streamed, first terabyte free every month after your first top-up
Videas has no subscription: your client tops up a prepaid credit wallet whenever they decide to, and nothing is drawn down in the months the site streams nothing. Thirty euros of credits cover, within one month, around thirty hours of video hosted, two terabytes streamed — the first one free from the month after the first top-up — and half an hour of automatic subtitling. API calls themselves are not billed: what they trigger is what draws down.
Yes: the Videas public API, /v1. It lists and counts the media of the library and the workspaces they are filed in, filtered by type, by workspace and by your own reference, and reads one media item with its tags and its custom fields. It adds files — sent from a server or a browser, or fetched from a link — and videos hosted on YouTube, Vimeo or Dailymotion, edits a media item's words, tags, custom fields and thumbnail, and publishes media on the organization's channels. Lists are walked page by page, with a cursor.
No. The API is plain HTTP and JSON, and the reference shows every call in cURL, Node.js and Python. Its OpenAPI 3.1 contract downloads to generate a client in your language, and any tus 1.0 client sends a large file resumably.
With a key of the organization, which an owner or an administrator creates in the Videas settings, choosing what it may do — read the library, feed it, edit its media, import videos from other platforms, read the channels, publish on them — and its expiry date, then send as a Bearer token on every request. The full value is shown only once, at creation, so put it straight into a secrets manager. A missing key returns 401, a missing permission returns 403.
No. Videas bills neither the request nor a block of calls: API access is included. What draws down the credit wallet is what your calls trigger, at the published rates — storing the files you upload, streaming to viewers, generating subtitles.
Yes, with no published figure: a request too many, from a key or its organization, gets a 429 with a Retry-After header saying how many seconds to wait before sending it again. The number of links waiting to be downloaded per organization is bounded the same way.
With POST /v1/uploads, which creates the media item at once and answers an upload address and token. Up to fifty mebibytes the file goes in one PUT; beyond, with the resumable tus protocol, in chunks: a dropped connection does not send you back to zero. A file already online need not go through you at all: give its link, and Videas downloads it. Ten gibibytes at most per file.
With the embed code Videas gives for each media item, as a script tag or an iframe: the Videas player sits in your client's page and plays the adaptive stream. The public API does not serve playback: it feeds the library, reads and edits what it holds, and publishes it on the channels.
By declaring the allowed domains in the workspace embed settings. Videas then refuses to render anywhere else. Subdomain wildcards are accepted, and organization-level domains cascade down to workspaces. List production with and without www, plus staging and any intranet, before you switch the restriction on.
The videos and their viewers' data stay inside Europe: Videas is a French company, GDPR compliant, and sells no data on. The player sets no cookie and shows no advertising — no pre-roll, no banner, no suggestion toward third-party content. That is the answer your client needs before ruling out a consumer platform.
That is the whole point. Once the integration is in place, they upload, file, replace and publish their media from the Videas interface, manage their team's permissions and read their analytics. The player theme, accent color and logo are resolved at playback: changing them touches no page of their site.
