Products
Products
Video Hosting
Upload and manage your videos in a centralized video library.
Image Hosting
Upload and manage all your images in a centralized library.
Galleries
Choose from 100+templates to showcase your media in style.
Video Messaging
Record, and send personalized video messages.
CincoTube
Create your own community video hub your team, students or fans.
Pages
Create dedicated webpages to share your videos and images.
Live
Create dedicated webpages to share your videos and images.
For Developers
Video API
Build a unique video experience.
DeepUploader
Collect and store user content from anywhere with our file uploader.
Solutions
Solutions
Enterprise
Supercharge your business with secure, internal communication.
Townhall
Webinars
Team Collaboration
Learning & Development
Creative Professionals
Get creative with a built in-suite of editing and marketing tools.
eCommerce
Boost sales with interactive video and easy-embedding.
Townhall
Webinars
Team Collaboration
Learning & Development
eLearning & Training
Host and share course materials in a centralized portal.
Sales & Marketing
Attract, engage and convert with interactive tools and analytics.
"Cincopa helped my Enterprise organization collaborate better through video."
Book a Demo
Resources
Resources
Blog
Learn about the latest industry trends, tips & tricks.
Help Centre
Get access to help articles FAQs, and all things Cincopa.
Partners
Check out our valued list of partners.
Product Updates
Stay up-to-date with our latest greatest features.
Ebooks, Guides & More
Customer Stories
Hear how we've helped businesses succeed.
Boost Campaign Performance Through Video
Discover how to boost your next campaign by using video.
Download Now
Pricing
Watch a Demo
Demo
Login
Start Free Trial
HTTP methods define how a client communicates with a server and are essential to how video platforms manage content. Whether retrieving metadata, uploading a video, updating encoding settings, or deleting outdated content, each method (GET, POST, PUT, and DELETE) serves a specific role in the lifecycle of a video asset. GET – Reading Data Without Changing It The GET method is used to retrieve data from a server. It's read-only, it doesn’t modify anything on the server. Video platforms use GET to fetch video metadata, thumbnail images, playback URLs, and video chunks for streaming. Fetching Video Metadata Before a video plays, the platform often loads its title, description, tags, and duration. This populates the video card or detail page. GET /api/videos/123 HTTP/1.1 Host: media.example.com Accept: application/json Explanation : GET /api/videos/123 : Requests metadata for video ID 123. Host : The domain where the video content is stored. Accept : application/json: Asks the server to return the data in JSON format. Streaming Video Segments Most modern platforms stream videos using adaptive bitrates and segmented playback. Each segment (or chunk) is delivered via a GET request. GET /videos/123/720p/segment1.ts HTTP/1.1 Host: stream.example.com Explanation : GET /videos/123/720p/segment1.ts : Requests the first segment of video ID 123 in 720p resolution. Host : The streaming server providing the content. POST – Sending Data to Create Something New The POST method is used to submit data to the server to create something new. On a video platform, POST is used for uploading videos, starting encoding jobs, or creating user-submitted comments or metadata. Uploading New Video Content When a user uploads a video file, the client sends the video data to the server using POST. POST /api/upload HTTP/1.1 Content-Type: multipart/form-data Explanation : POST /api/upload : Initiates a video upload process. Content-Type : Multipart/form-data: Indicates the request includes a file and accompanying metadata. Starting Encoding Jobs After uploading, videos need to be encoded into various formats (like 1080p, 720p) for different devices and network speeds. This is triggered via a POST request. POST /api/encode HTTP/1.1 Content-Type: application/json { 'source_uri': 's3://uploads/video123.mov', 'outputs': [ { 'resolution': '1080p', 'codec': 'h264' }, { 'resolution': '720p', 'codec': 'vp9' } ] } Explanation : source_uri : Path to the original uploaded video file in cloud storage (e.g., S3). outputs : List of desired encoding formats. Each output includes a resolution and codec to define how the video should be processed. PUT – Updating or Replacing Existing Data The PUT method is used to update or replace an existing resource . On a video platform, this is used when updating video metadata or modifying encoding parameters for uploaded content. Updating Video Metadata If a content creator updates the title, description, or tags of their video, the platform uses a PUT request to replace the old data. PUT /api/videos/123/metadata HTTP/1.1 Content-Type: application/json { 'title': 'New Title', 'description': 'Updated video description', 'tags': ['education', 'HD'] } Explanation : PUT /api/videos/123/metadata : Updates the metadata of video ID 123. The body includes the new title, description, and tags to overwrite existing values. Reprocessing with New Encoding Settings Sometimes a video needs to be re-encoded (e.g., changing the codec). A PUT request can be sent to update the job configuration. PUT /api/encode/video123 HTTP/1.1 Content-Type: application/json { 'outputs': [ { 'resolution': '4K', 'codec': 'h265' } ] } Explanation : PUT /api/encode/video123 : Updates encoding settings for video ID video123. outputs : Specifies the new resolution and codec settings for the video to be reprocessed. DELETE – Removing Data from the Server The DELETE method is used to remove a resource from the server. Video platforms use it for removing uploaded content, clearing caches, or deleting outdated metadata. Deleting Videos Permanently When a user wants to remove their video, the platform sends a DELETE request targeting the specific video. DELETE /api/videos/123 HTTP/1.1 Explanation : DELETE /api/videos/123 : Permanently deletes video ID 123 from the server and its associated metadata. Using Soft Deletes for Safety Many platforms prefer 'soft deletes' to allow recovery later or to comply with moderation review workflows. This keeps the video in the system but makes it inaccessible to users. DELETE /api/videos/123 HTTP/1.1 X-Soft-Delete: true Explanation : X-Soft-Delete : true: A custom header that tells the server to flag the video as deleted without immediately erasing it. Differences Between Core HTTP Methods