# Create build API returns null

**URL:** <https://drone.discourse.group/t/create-build-api-returns-null/7526>\
**Category:** Drone Support\
**Created:** [February 10, 2021, 8:53pm UTC](https://drone.discourse.group/t/create-build-api-returns-null/7526 "2021-02-10T20:53:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![neildevas](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/neildevas/32/2932_2.png) [@neildevas](https://drone.discourse.group/u/neildevas)\
**Post date:** [February 10, 2021, 8:53pm UTC](https://drone.discourse.group/t/create-build-api-returns-null/7526/1 "2021-02-10T20:53:38Z")

</div>

When I make a POST request to the Build Create API I receive a 200 with null response.

Here is the example endpoint I am requesting:  
[drone.example.com/api/repos/example-namespace/example-name/builds?branch=example-branch](http://drone.example.com/api/repos/example-namespace/example-name/builds?branch=example-branch)

The response: ` HTTP/1.1 200 OK cache-control: no-cache, no-store, must-revalidate, private, max-age=0 content-type: application/json expires: Thu, 01 Jan 1970 00:00:00 UTC pragma: no-cache vary: Origin x-accel-expires: 0 date: Wed, 10 Feb 2021 20:51:33 GMT content-length: 5 x-envoy-upstream-service-time: 94 server: istio-envoy null`

One thing I’m unsure of is if the `{namespace}` and `{name}` parameters I am passing are correct shown here:  
`POST /api/repos/{namespace}/{name}/builds `

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [February 10, 2021, 10:23pm UTC](https://drone.discourse.group/t/create-build-api-returns-null/7526/2 "2021-02-10T22:23:39Z")

</div>

> [@Drone-b2 panicking on failed auth?](https://drone.discourse.group/t/drone-b2-panicking-on-failed-auth/8730/1):
>
> When I make a POST request to the Build Create API I receive a 200 with null response.

the most common root cause is a `trigger` section in the yaml that is evaluating to false and therefore prevents a build from being scheduled. If you look at your Drone server logs (you may need to enable debug logging) you would likely see a detailed reason.