Symptom
When attempting to start an archive in the Video API session using Video REST API calls, you receive an HTTP 415 Unsupported Media Type response status code.
Applies To
- Video API
- Archiving
- Video REST API
- HTTP 415
- Unsupported Media Type
Resolution
Make sure that the "Content-Type" header is included in your REST API request and has the "application/json" value associated with it.
Cause
This issue occurs when the user does not set the "Content-Type:application/json" in headers.
Additional Information
For more information about Archiving, see our Opentok Environment Developer Guides or Unified Environment Developer Guides.
Related to:
Articles in this section
- Checklist for when cycleVideo is not working in JavaScript
- Why Is My Video Camera Displaying a 4:3 Aspect Ratio Instead of 16:9 When Publishing in HD OR FHD resolution (1280x720)?
- How to use Completion handler for Exception Handling
- Firefox Pre-call test not supported
- Error Creating Session Using Vonage Video API .NET SDK
- Unable to Create Session Even Though API Key and Secret Are Valid
- HTTP 415 Error When Archiving Video Session
- Troubleshooting Invalid JWT When Creating a Video Session using REST API
- Camara Still in Use after Session Disconnect on Android
- Token Shows as Invalid