Help center

Get an answer for any questions you may ask
about our service and cloud video encoding in general.

Technical FAQ

What is a webhook and how to test it?

A webhook is a POST HTTP request we make to your site when the job is completed. Learn more in the documentation.

To test it with curl:

curl http://yoursiteurl \
-v -X POST \
-H "Content-Type: application/json" \
-d '{"ping":"test"}'

We also provide the ping inspector available through the web interface to debug webhook requests. We advise you to use this tool to get started.

Are the videos hosted on Coconut public?

No, everything in your account is private.

Do you accept any kind of video content?

Yes, you can use Coconut to convert any kind of video content, including "adult" content. We don't have any content restrictions.

Do you provide live streaming?

No, we only encode completed video files. We do not support live stream sources like webcam or live channel streams as input.

How long do you keep the media on Coconut?

We keep the media for around 24 hours, with no distinction between source video and encoded video.

That should be more than sufficient, since 99% of the time you want us to upload the final video to your CDN right after the process is completed.

How long does it take to integrate Coconut into my application?

Integrating Coconut into your application is really fast thanks to our simple and fully documented API. It takes less than 5 minutes to get started thanks to our web interface.

We also provide many libraries in the most popular languages including Ruby, PHP, Python and .NET.

I need your server IPs to add them to my firewall whitelist

Please contact us for this matter.

Is there a file size limit?

No we don't have a file size limit nor a length limit.

Is there an API usage restriction?

There is no API restriction. however, if we see an abnormal peak in API requests, we may suspend your account temporarily (usually for one hour).

In case of a suspension, you will be notified immediately by an automated email and the API will be temporarily disabled as well (403 HTTP code).

Sometimes a script bug that you didn't know about can cause this kind of problem, so we want to make sure everything is fine on your side first. Please contact us if you have any questions regarding this matter.

Is it possible to embed videos from Coconut directly?

No, we don't deliver videos to the final users. You must use an external CDN like Amazon S3, Cloud Files, Azure, Rackspace, or your own HTTP servers.

Limitation of the Test environment

The only limitation to the test environment is that every encoded video is cut down to 5 seconds. To use the test environment, just authenticate your API requests with a Test API key.

Software Recommendation for HTTP streaming

If you plan to stream the video yourself, without using a CDN, we recommend nginx and its nginx MP4 module

Encoded videos are not available on the FTP destination

First check the following:

  • The Hostname must be public; no localhost!
  • User and password are correct
  • The port is correct
  • If you have a firewall, the port must be opened
  • You have space available on your FTP server
  • The user has the permission to write to the given directory
  • The passive mode, if used, must be correctly configured

You can test your FTP with the curl command line:

curl -v --disable-epsv -T yourfile "ftp://user:passwd@host.com/path"

You should now have all the information you need to know the exact problem.

Authentication issue with FTP delivery

If you have a special character in your username or password, character escaping will likely solve the problem.

Some common username problem:

  • The username has a domain name like user\domain => user%5Cdomain
  • The username is an email like you@yoursite.com => you%40yoursite.com

Delivery to Amazon S3 doesn't work

Check the following:

  • The bucket actually exists
  • The user has the right to write (PutObject and PutObjectACL permissions)

There is a problem with the source viedo URL

With the curl command line, we will check the HTTP headers:

curl -I 'http://yoursite.com/video/myvideo.mp4'

Check the following things:

  • It should return the status code 200 OK. Other code will fail.
  • The content type must be video/*, audio/* or application/*
  • The URL must be public. localhost won't work!

If you want to check an FTP URL:

curl -v -I "ftp://user:passwd@mysite.com/video.mp4"

You should have the connection detail printed in your console. Something like this:

* About to connect() to mysite.com port 21 (#0)
*   Trying 212.27.63.3...
* connected
* Connected to mysite.com (212.27.63.3) port 21 (#0)
< 220 FTP server
> USER user
< 331 Password required for user.
> PASS passwd
< 230 User user logged in.
> PWD
< 257 "/" is current directory.
* Entry path is '/'
> MDTM video.mp4
< 550 video.mp4: No such file or directory
* Given file does not exist
* Remembering we are in dir "video.mp4"
* Connection #0 to host mysite.com left intact
curl: (19) Given file does not exist
> QUIT
< 221 Goodbye.
* Closing connection #0

As you can see the file doesn't exist. The info should be self explanatory, and you will be able to fix your problem very quickly.

Do you support Dropbox transfers?

Yes, you must use the public URL for the video you want to convert.

To get the public URL of a file:

  • In the Dropbox folder on your computer or directly on the Dropbox website, just right-click on the video file.
  • If you are on your computer, select Dropbox under the menu choice. Note that if your are on Dropbox website, this step is not necessary.
  • Then click "Copy Public Link".

Do you provide a watch folders feature?

We do not provide this feature. If you move a file, it's just as easy to make an HTTP request when it's done. It will also provide you with greater flexibility.