As a segment transcoding API user, I cannot use some of the values returned to me
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug (required)**
When create a new stream with the segment transcoding API, some of the values passed back cannot be used. These include:
* `streamKey`
* `playbackId`
* `userId`
* `renditions`
* `kind`
**Expected behavior (required)**
The API response should only contain the necessary information for a segment transcoding API user.
**To Reproduce (required)**
Steps to reproduce the behavior:
1. POST to the `livepeer.com/api/stream` endpoint
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the POST request to the `livepeer.com/api/stream` endpoint and inspect the response fields listed in the report: `streamKey`, `playbackId`, `userId`, `renditions`, and `kind`. The issue does not specify which information should remain, so clarify the required segment-transcoding response before changing it; done means the response contains only the agreed necessary fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100