{
  "opencollection": "1.0.0",
  "info": {
    "name": "VideoAmp Public Data Stream Types API",
    "version": "2026-07-31"
  },
  "request": {
    "auth": {
      "type": "oauth2",
      "flow": "authorization_code",
      "authorizationUrl": "https://login.videoamp.com/authorize",
      "accessTokenUrl": "https://login.videoamp.com/oauth/token",
      "credentials": {
        "clientId": "{{clientId}}",
        "clientSecret": "{{clientSecret}}"
      }
    }
  },
  "items": [
    {
      "info": {
        "name": "dataStreamTypes",
        "type": "folder"
      },
      "items": [
        {
          "info": {
            "name": "List Data Stream Types",
            "type": "http"
          },
          "http": {
            "method": "GET",
            "url": "https://api.videoamp.dev/v1alpha/dataStreamTypes"
          },
          "docs": "### What\n\nReturns the catalog of supported Data Stream types. Each entry includes `name` (the kebab-case URL identifier), `enum_value` (the `dataStream.type` enum form), `display_name` (a human-readable label), and `description` (long-form prose tuned for LLM retrieval). The canonical `fields` schema is omitted — call `GET /dataStreamTypes/{dataStreamTypeName}` to retrieve it.\n\n### Why\n\nLets agents and UIs enumerate the types VideoAmp ingests. The list response is rich enough for an agent to rea"
        },
        {
          "info": {
            "name": "Get Data Stream Type",
            "type": "http"
          },
          "http": {
            "method": "GET",
            "url": "https://api.videoamp.dev/v1alpha/dataStreamTypes/:dataStreamTypeName",
            "params": [
              {
                "name": "dataStreamTypeName",
                "value": "",
                "type": "path",
                "description": "Kebab-case identifier for the type. Obtainable from 'GET /dataStreamTypes' (each entry's 'name')."
              }
            ]
          },
          "docs": "### What\n\nReturns the canonical definition of a single Data Stream type — display metadata (`name`, `enum_value`, `display_name`, `description`) and the canonical `fields` schema (each with `name`, `description`, `type`, `required`, `examples`, `aliases`).\n\n### Why\n\nMapping agents and onboarding UIs use this to learn the field set a provider feed must satisfy. Required fields gate transitioning the parent Data Stream to `PROVISIONING`.\n\n### When\n\nAfter picking a `type` from the list endpoint — f"
        }
      ]
    }
  ],
  "bundled": true
}