Sora2 Video Watermark Removal API

You can use the Sora2 video watermark removal API provided by our website through the methods described in this article to integrate this feature into your own application.

Obtain AccessToken

Before starting the integration, you need to obtain the AccessToken of this tool first. It will be used as the credential for your application to call this API.

After entering the application interface of this tool, find the "API Credential" menu in the left - hand menu bar and enter this page.

On the entered page, click the "Create" button, fill in the appropriate information in the pop - up window that appears, and submit.

In this way, you have created an AccessToken. You need to click the "Copy" button to save this token locally. Note that you must not make this token public to avoid unnecessary losses.

Submit Processing Requests via HTTP API

Next, you need to submit a watermark-removal request in your code. The following is sample mock code:

POST "https://www.fuuai.com/api/video-watermark-removal/{APP_ID}"
HEADERS
     Authorization: Bearer {ACCESS_TOKEN}
     Content-Type: multipart/form - data
     Accept: video/mp4
BODY(formdata)
     video_file: file

The APP_ID can be found in the URL address bar of the application page you visit on our website. After submitting the request, wait for the server's response. Finally, you will get a binary stream of an MP4 file. Save it locally, and it will be the video file with the watermark removed.

The above method is to complete the watermark removal by uploading a file. If you want to remove the watermark through the sharing link on the Sora official website, you can use the following method.

POST "https://www.fuuai.com/api/video-watermark-removal/{APP_ID}"
HEADERS
     Authorization: Bearer {ACCESS_TOKEN}
     Content-Type: application/json
     Accept: video/mp4
BODY(json)
     action_type: 'remove_sora_video_watermark_by_share_link'
     share_link: string

At this time, you do not need to upload a file object, which seems more convenient. However, due to restrictions from upstream service providers, this method has a limit on the number of times. If you encounter situations where the processing cannot be completed multiple times, it means you have encountered a limit-on-times issue. You can try again after waiting for a while.

Here are several points to note:

• The Content-Type used in the two methods is different. Please distinguish carefully.
• In the Headers, you need to pass in Accept as video/mp4 to obtain binary video data. Otherwise, you can only get a system file ID. Although you can also obtain the file itself using this ID, it requires one more step of operation, which is more troublesome.
• The data passed in the body of the two methods is different.

History

The historical records of processing using the API will be mixed with those processed on the application interface. This will be beneficial for you to view all records on our website in the future.

How to Charge?

The cost of using the API is the same as that of operating on the application interface. 48 points will be consumed for each video processed.