# Dgraph admin have different response patterns

**URL:** <https://discuss.dgraph.io/t/dgraph-admin-have-different-response-patterns/18642>\
**Category:** Dgraph Cloud / Slash GraphQL\
**Created:** [May 17, 2023, 3:22pm UTC](https://discuss.dgraph.io/t/dgraph-admin-have-different-response-patterns/18642 "2023-05-17T15:22:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![leonhma](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/leonhma/32/10421_2.png) [@leonhma](https://discuss.dgraph.io/u/leonhma)\
**Post date:** [May 17, 2023, 3:22pm UTC](https://discuss.dgraph.io/t/dgraph-admin-have-different-response-patterns/18642/1 "2023-05-17T15:22:19Z")

</div>

## This is a minor issue / feature request

So I was in the process of building CI that verifies the provided GraphQL Schema against dgraph and updates it. The endpoint `/admin/schema` always reponds with status `200` no matter the outcome of the requests, and only contains the response json field `errors` if an actual error happened. The `/admin/schema/validate` endpoint always returns the results inside the `error` field. The outcome of the action here can only be observed via the status code of the response.

---

<div class="post-metadata">

**Author:** ![MichelDiz](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/micheldiz/32/11873_2.png) [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)\
**Post date:** [May 17, 2023, 10:53pm UTC](https://discuss.dgraph.io/t/dgraph-admin-have-different-response-patterns/18642/2 "2023-05-17T22:53:45Z")

</div>

> [@leonhma](#):
>
> status `200`

This is by default in GraphQL Spec… Error handling in GraphQL does not take into account the HTTP standard. So it will always be 200.