Skip to main content

Search

HTTP 400 Error When Archiving Video Session

Avatar
Rama Ganesan
  • Updated

This article may be out of date! Please visit our new help center api.support.vonage.com

Symptom

When attempting to archive a Vonage Video API session, you receive an HTTP 400 Bad Request response status code.

Applies To

  • Vonage Video API
  • Archiving
  • HTTP 400
  • Relayed Session

Resolution

Archiving a Session That is Already Being Archived

Attempting to initiate archiving of a session that is already being archived will result in an HTTP 400 status from the REST API call that is used to start the archive or the start_archive call issued from a Server SDK. To avoid this, register a callback URL in your Vonage Video API Account and check the status of the archiveId to determine if the archive was successfully started.

Archiving a Relayed Session

Attempting to start archiving a Relayed session will result in an HTTP 400 level status from the REST API call that is used to start the archive or the start_archive call issued from a Server SDK. To avoid this, make sure you create Routed sessions if you wish to archive a session.

Archiving Before Session Has Connections

Attempting to start archiving a session before the session has any connections will result in an HTTP 400 level status from the REST API call that is used to start the archive or the start_archive call issued from a Server SDK and it will fail to create an archive. To avoid this, sessions can be set for automatic archiving when the session is created. Alternatively, make sure at least one client has connected to the session before attempting to start archiving.

Archiving Using Different API Key and Secret

Attempting to start archiving a session using an API key and secret that is different than the key and secret that were used to generate the session ID will result in an HTTP 400 level status from the REST API call that is used to start the archive or the start_archive call issued from a Server SDK and it will fail to create an archive. To avoid this, make sure to use the same credentials for all REST, Server SDK, and token generation actions related to a project.

Additional Information

For more information on archiving, see the Archiving developer documentation.

Related articles

Comments

0 comments

Article is closed for comments.