---
title: "Create a live ingest point"
method: POST
path: "/v2/sites/{site_id}/live/broadcast/ingest/"
tags: ["broadcast live"]
---

# Create a live ingest point

`POST /v2/sites/{site_id}/live/broadcast/ingest/`

## Request

- Base URL: `https://api.jwplayer.com`
- URL: `https://api.jwplayer.com/v2/sites/{site_id}/live/broadcast/ingest/`
- Auth: API key in header `Authorization`

Create a new live ingest point

For more product information, see [Get started with Broadcast Live](https://docs.jwplayer.com/platform/docs/broadcast-live-get-started-with-broadcast-live).

## Path parameters

- `site_id` string, required: Unique identifier for a resource

## Request body

- CreateIngestPointParameters: The parameters to create a new live ingest point
  - `ingest_format` 'rtmp' | 'rtp' | 'rtp_fec' | 'srt', required: Live ingest format Only a subset of ingest formats is supported to be used with ingest points.
  - `display_name` string, required: Friendly name used for identifying the ingest point in the JWX dashboard

## Response `200`

Success

- LiveIngestObjectSchema: Schema object for a live ingest point
  - `schema` string
  - `id` string: Unique identifier for a resource
  - `created` string: Date and time at which the resource was created
  - `last_modified` string: Date and time at which the resource was most recently modified
  - `type` string: Name of the type of resource.
  - `relationships` object: Ancilliary resources associated to the primary resource being read
  - `metadata` LiveIngestMetadata: Schema object for a live ingest points's metadata
    - `ingest_format` 'rtmp' | 'rtp' | 'rtp_fec' | 'srt': Live ingest format
    - `url` string: The URL for the ingest location A live ingest provides a reusable ingest address so that many streams can be ingested at the same location over time.
    - `display_name` string: Friendly name used for identifying the ingest point in the JWX dashboard
    - `version` integer: Numeric identifier that determines the behaviors supported by the live ingest point New live ingest points will always be created with the latest version.

## Other responses

- `400`: Invalid JSON request body
- `404`: Resource with ID supplied does not exist in account and object namespace

## Changes

- **2026-11-03** `9fad6bd5872e`: 2 info
  - added the media type `application/json` for the response with the status `400`
  - added the media type `application/json` for the response with the status `404`

[Operation history](https://skmtc.dev/jwplayer/apis/management-api-v2/changes/v2/sites/:site_id/live/broadcast/ingest/post.md)

---

[API](https://skmtc.dev/jwplayer/apis/management-api-v2.md) - [All operations](https://skmtc.dev/jwplayer/apis/management-api-v2/llms.txt) - [OpenAPI document](https://skmtc.dev/jwplayer/apis/management-api-v2/revisions/9fad6bd5872e?raw)