Add a delivery target
Formats: xmltv, schedule_json, playlist_json, transmission_xml, transmission_csv, transmission_json. A push target needs an https endpointUrl (private and internal addresses are refused) and answers with its signingSecret once — every delivery carries x-ingenee-signature: sha256=<HMAC-SHA256 of the body>. An sftp target takes endpointUrl sftp://host[:port]/folder/ (or a full file path), username and credential (a password or a private key), and optionally hostKeySha256. An s3 target takes s3://bucket/prefix/[?region=…], username (access key id) and credential (secret access key). A folder address gets a new timestamped file per delivery.
Scope: channels:write
apiKeyAuthorizationBearer <ik_live_…>An organisation API key from Settings → Organisation → API keys. Each operation names the one scope it needs — see https://developer.ingenee.ai/docs/authentication.
id*stringIdempotency-Key?stringAny unique string. A retry with the same key and the same request gets the first answer back instead of running twice (kept 24 hours).
length <= 255application/json- body
name*string1 <= length <= 80partnerKey?string"custom""custom""roku_dpf""samsung_tvplus""jsonld""lg""vizio""pluto""xumo""amazon""plex"format*string"xmltv""schedule_json""playlist_json""transmission_xml""transmission_csv""transmission_json"method*string"pull""https_push""sftp""s3"endpointUrl?stringurilength <= 2000nullauthHeaderName?string^[A-Za-z0-9-]+$length <= 60nullauthValue?string1 <= length <= 2000nulltrigger?string"on_publish""on_publish""manual"enabled?booleantrueusername?string1 <= length <= 200nullcredential?string1 <= length <= 16000nullhostKeySha256?string^SHA256:[A-Za-z0-9+/]{43}=?$nullOK
application/json- response
[key: string]?anycurl -X POST 'https://dev.app.ingenee.ai/api/v1/channels/string/delivery-targets' \ -H 'Content-Type: application/json' \ -d '{ "name": "string", "format": "xmltv", "method": "pull"}'{}