To start playing with 42videobricks, you need to create an account here: Register.


42videobricks is free to test: you just need to register and you will be able to test our api in the sandbox.


42videobricks provides 3 distinct API environments (each environment has an isolated video storage):

  • sandbox ( the sandbox environment provide a free to use environment to test the api. This environment is limited for testing the api and has limitation such as (video upload size, video deletion after 24h and number of api calls)
  • production ( the production environment remove the sandbox limitations and is accessible after subscribing to the service. You pay as you use: billing is based on your usage of the platofrm. more on (www.42videobricks/pricing).
  • staging: ( the staging environment is similar to the production environment (data are isolated from production data) and can be used for testing your system before deploying in production.


Production and staging API are sharing the same usage plan.

API Keys

42videobricks API are protected by an authentication mechanism based on API key.

You need to set your API Key (as the "x-api-key" header) to each API call.

curl --request POST \
     --url <<SBX_SERVER>>/videos \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --header 'x-api-key: <my-sandbox-api-key>' \
     --data '
  "title": "My video title",
  "description": "My video desctiption",
  "public": false

Getting your API Keys

You can manage your api keys in the apikeys section of the admin: ApiKeys Admin

A default API key is created for sandbox environement but you can create more Apikeys.


Only subscribed account can create and use staging or production Apikeys.

When the subsciption is canceled, staging and production Apikeys are disabled.

Protect your API Keys


Apikeys are private and should be kept secret and not shared with anyone.

Apikeys are used in server-to-server communications only.

You should create as much apikeys you need and avoid reusing the same Apikeys for different environment or clients: it would allow you to easily replace a compromised Apikey.


Apikeys are restricted to their environements.

curl '<<SBX_SERVER>>/videos' \
  -H 'x-api-key: <my-sandbox-api-key> '

Api returns error HTTP error code 403 response when authentication fails due to:

  • "Missing Authentication Token": Apikey is missing
  • "Forbidden": Apikey is not allowed to access the ressource (wrong Apikey, bad environment or unactivated Apikey).

Limits & quotas

We have set limits in staging and production environement. If you reach this limitation please call our support.

Quotas for sanbox is low.

What’s Next