# Create release/tag for a specific branch via api

**URL:** <https://forum.gitea.com/t/create-release-tag-for-a-specific-branch-via-api/7271>\
**Category:** Gitea Usages\
**Created:** [May 14, 2023, 12:25pm UTC](https://forum.gitea.com/t/create-release-tag-for-a-specific-branch-via-api/7271 "2023-05-14T12:25:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![germgerm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/germgerm/32/2905_2.png) [@germgerm](https://forum.gitea.com/u/germgerm)\
**Post date:** [May 14, 2023, 12:25pm UTC](https://forum.gitea.com/t/create-release-tag-for-a-specific-branch-via-api/7271/1 "2023-05-14T12:25:24Z")

</div>

through the browser ui we can create a release for a specific branch,  
using the same endpoint (…/releases/new) and args fails,  
using the additional args ( tag\_target) with (…/releases) has no affect

Is creating a release for any branch other than the main something that was overlooked in the api or … what am I missing ?

---

<div class="post-metadata">

**Author:** ![germgerm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/germgerm/32/2905_2.png) [@germgerm](https://forum.gitea.com/u/germgerm)\
**Post date:** [May 16, 2023, 12:32am UTC](https://forum.gitea.com/t/create-release-tag-for-a-specific-branch-via-api/7271/2 "2023-05-16T00:32:51Z")

</div>

target\_commitish was the trick