Authentication

SignStream authentication is handled through an API key mechanism. Each request to the SignStream API must include a valid API key in the request headers.

API Key

When you create a SignStream account, you will be provided with an API key. Pass this key in the X-API-KEY header of each request.

Example Request

curl -X POST "https://ai.api.production.signapsesolutions.com/v2/generate" \
-H "Content-Type: application/json" \
-H "X-API-KEY: YOUR_API_KEY" \
-d '{
  "content": {
    "type": "text",
    "data": "Hello, welcome to our service."
  },
  "output": {
    "format": "mp4",
    "delivery": {
      "method": "download"
    }
  }
}'

Playing Back Protected Media

Your API key authenticates calls to the SignStream API. It does not authenticate media playback — manifests and video segments are served from a CloudFront CDN and protected by CloudFront signed URLs instead.

What you get back

• Signed manifest URLs. manifests.hls, manifests.dash, and manifests.pip on a live session response each arrive pre-signed and ready to hand to a player.
• Signed URLs inside the manifest. Every segment, partial segment, init segment, and preload-hint URL in a live manifest is signed individually, for both the signer-only and picture-in-picture streams. A player needs no extra configuration to fetch them.
• Signed access cookies. The create-session response also sets CloudFront access cookies (Secure, HttpOnly) scoped to the session, for players that prefer cookie-based access.

If playback returns 403

• Check you are using the URL exactly as returned, query string intact.
• Check the URL has not expired — re-fetch the session.
• If you proxy media through your own server, forward the full query string, and forward the CloudFront cookies if you rely on cookie-based access.

Where to Find Your Key