# GraphQL API Usability

We are hitting more and more cases where we need information from the backend which is not available or not easy to access in single query. It is time to start thinking how to improve the GraphQL usability.

*GitHub's graphql API will be used as example.*

## Accessing Data by more than 1 way.

In Alkemio a `challenge` is central part of the system as it is the `repository` in github. Challenges are grouped under Ecoverses (Hubs) as repositories have owner (user/organization).

In our API if a challenge have to be accessed the query must start from Ecoverse and drilled down it is the same for github's api. But github have the ability to get a repositor by just passing the owner name and the repository name. Similar way to select a challenge is not possible in our API.

Do we need it ? Yes/No