Developer API v1.0

Build Faster with Gusion CDN

Integrate high-performance media delivery and real-time processing into your stack with just a few lines of code.

Authentication

How to securely connect to our services.

The Gusion API uses API keys to authenticate requests. You can find your keys in theKey Manager. Include your secret key in the X-API-Key header for all requests.

Example Shell Request
curl -X GET https://api.gusion.in/v1/assets \
  -H "X-API-Key: gs_live_492a...821b" \
  -H "Content-Type: application/json"

Asset Management

Uploading and processing your media files.

1

Initiate the Upload

First, send your file's metadata to our gateway. We'll return a secure S3 presigned URL that you can use to push data directly to our storage.

POST /v1/assets/initiate
{
  "name": "cinema_4k_render.mp4",
  "size": 2147483648,
  "contentType": "video/mp4",
  "folderId": "fld_prod_882"
}
2

Push Binary Data

Perform a PUT request to the uploadUrl provided in step 1. For best performance, use a library that supports streaming uploads.

Binary PUT Upload
curl -X PUT "https://s3.amazonaws.com/gusion-assets/temp-upload-token..." \
  -T "local_video.mp4" \
  -H "Content-Type: video/mp4"

Global Delivery

Serving your content via our edge network.

Edge Optimized URLs
Every asset is automatically optimized for low-latency delivery across 180+ global nodes.
HLS VOD
Live Edge URL
https://cdn.gusion.in/{org_id}/{asset_id}/master.m3u8

< 12ms

TTFB Latency

214 Nodes

PoP Locations

Unlimited

Dynamic Scaling

Webhooks & Events

Real-time notifications for asset processing.

Configure webhooks to receive real-time HTTP POST payloads when certain events occur, such as when an asset finishes processing or transcoding.

Example Webhook Payload
{
  "event": "asset.processed",
  "data": {
    "assetId": "ast_9381...",
    "status": "ready",
    "url": "https://cdn.gusion.in/org_123/ast_9381/master.m3u8"
  }
}

Error Handling

Understanding API responses and codes.

Gusion API uses conventional HTTP response codes to indicate the success or failure of an API request.

2xx
Success

The request was successfully received and accepted.

400
Bad Request

The request was unacceptable, often due to missing a required parameter.

401
Unauthorized

No valid API key provided.

429
Too Many Requests

Too many requests hit the API too quickly.