# API to retrieve ingestion endpoints **URL:** \ **Category:** API\ **Created:** [June 14, 2019, 6:44pm UTC](https://staging-discuss.dev.twitch.com/t/api-to-retrieve-ingestion-endpoints/21491 "2019-06-14T18:44:03Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![DanielWearsNada](https://avatars.discourse-cdn.com/v4/letter/d/f1d935/32.png) [@DanielWearsNada](https://staging-discuss.dev.twitch.com/u/DanielWearsNada)\ **Post date:** [June 14, 2019, 6:44pm UTC](https://staging-discuss.dev.twitch.com/t/api-to-retrieve-ingestion-endpoints/21491/1 "2019-06-14T18:44:03Z")
Hello, I am wondering if there is a public API to get the following data, to programmatically create an RTMP url used to stream to a particular users account. If possible, I’d like to do the following with my application: -Authenticate a particular user -Retrieve a list of ingestion endpoints -Retrieve a stream key to append to the ingestion endpoint -Send data to said endpoint. Is this possible? Cheers 🙂 ---
**Author:** ![Dist](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dist/32/7192_2.png) [@Dist](https://staging-discuss.dev.twitch.com/u/Dist)\ **Post date:** [June 14, 2019, 7:30pm UTC](https://staging-discuss.dev.twitch.com/t/api-to-retrieve-ingestion-endpoints/21491/2 "2019-06-14T19:30:44Z")
Authentication: [https://dev.twitch.tv/docs/authentication/getting-tokens-oauth/#oauth-authorization-code-flow](https://dev.twitch.tv/docs/authentication/getting-tokens-oauth/#oauth-authorization-code-flow) Ingests: [https://dev.twitch.tv/docs/v5/reference/ingests/](https://dev.twitch.tv/docs/v5/reference/ingests/) Get stream key: [https://dev.twitch.tv/docs/v5/reference/channels/#get-channel](https://dev.twitch.tv/docs/v5/reference/channels/#get-channel) Sending data to that endpoint is just an RTMP connection, which you can do through ffmpeg directly or a library/app of your choice to handle that. ---
**Author:** ![DanielWearsNada](https://avatars.discourse-cdn.com/v4/letter/d/f1d935/32.png) [@DanielWearsNada](https://staging-discuss.dev.twitch.com/u/DanielWearsNada)\ **Post date:** [June 14, 2019, 8:46pm UTC](https://staging-discuss.dev.twitch.com/t/api-to-retrieve-ingestion-endpoints/21491/3 "2019-06-14T20:46:15Z")
Thank you so much! It seems the ingest API is only available with the v5 API, not the new socket-based API. Does that mean it’ll be deprecated soon? Cheers, Daniel ---
**Author:** ![Dist](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/dist/32/7192_2.png) [@Dist](https://staging-discuss.dev.twitch.com/u/Dist)\ **Post date:** [June 14, 2019, 9:09pm UTC](https://staging-discuss.dev.twitch.com/t/api-to-retrieve-ingestion-endpoints/21491/4 "2019-06-14T21:09:27Z")
The new API isn’t socket-based, it’s a REST API just like v3 and v5. But yes, being a v5 endpoint does mean that it is deprecated and currently there are no endpoints in the new API (Helix) for getting a list of ingest servers. ---
**Author:** ![DanielWearsNada](https://avatars.discourse-cdn.com/v4/letter/d/f1d935/32.png) [@DanielWearsNada](https://staging-discuss.dev.twitch.com/u/DanielWearsNada)\ **Post date:** [June 15, 2019, 12:59am UTC](https://staging-discuss.dev.twitch.com/t/api-to-retrieve-ingestion-endpoints/21491/5 "2019-06-15T00:59:55Z")
Oi, I have no idea where I got the socket idea. I must have gotten some wires crossed with another API. Anyways, thanks again. 🙂 ---
**Author:** ![system](https://d2spem0quai2ol.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://staging-discuss.dev.twitch.com/u/system)\ **Post date:** [July 15, 2019, 1:00am UTC](https://staging-discuss.dev.twitch.com/t/api-to-retrieve-ingestion-endpoints/21491/6 "2019-07-15T01:00:01Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.