Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.github.com/en/graphql/guides/using-the-explorer below:

Using the Explorer - GitHub Docs

You can run queries on real GitHub data using the GraphQL Explorer, an integrated development environment in your browser that includes docs, syntax highlighting, and validation errors.

GraphQL Explorer is an instance of GraphiQL, which is a "graphical interactive in-browser GraphQL IDE."

You can use query autocompletion to help you build queries. In the main pane, within the curly brackets of your query, use control+space or shift+space to display the autocomplete menu.

All types in a GraphQL schema include a description field compiled into documentation. The collapsible Docs pane on the right side of the Explorer page allows you to browse documentation about the type system. The docs are automatically updated and will drop fields that are closing down.

Note

The Docs sidebar contains the same content that is automatically generated from the schema under GitHub GraphQL API documentation, though it is formatted differently in places.

Some example calls include variables written like this:

query($number_of_repos:Int!){
  viewer {
    name
     repositories(last: $number_of_repos) {
       nodes {
         name
       }
     }
   }
}
variables {
   "number_of_repos": 3
}

This is the correct format to submit the call using a POST request in a curl command (as long as you escape newlines).

If you want to run the call in the Explorer, enter the query segment in the main pane and the variables in the Query Variables pane below it. Omit the word variables from the Explorer:

{
   "number_of_repos": 3
}

There are many open source GraphQL client IDEs. For example, you can use Altair to access GitHub's GraphQL API. To access the GraphQL API with Altair, download and install it from altair-graphql/altair. Then, follow the configuration steps below.

1. Get an access token.
2. Launch Altair.
3. In the left sidebar, below the Altair logo, click Set Headers. A new window will open.
4. In the "Header key" field, enter Authorization.
5. In the "Header value" field, enter Bearer TOKEN, replacing TOKEN with your token from the first step.
6. Click Save in the bottom right corner of the window to save your authorization header.
7. In the "GraphQL Endpoint" field, enter your GraphQL URL, such as https://api.github.com/graphql.
8. To load the GitHub GraphQL schema, download the public schema.
9. In Altair, click on Docs on the top right, then the three dots and Load Schema...
10. Select the file public schema that you downloaded in an earlier step.

You can test your access by querying yourself:

query {
  viewer {
    login
  }
}

If everything worked correctly, this will display your login. You're all set to start making queries.

For questions, bug reports, and discussions about GitHub Apps, OAuth apps, and API development, explore the API and Webhooks category in GitHub's Community Discussions. The discussions are moderated and maintained by GitHub staff, and answered by the GitHub community.

Consider reaching out to GitHub Support directly using the contact form for:

• Guaranteed response from GitHub staff
• Support requests involving sensitive data or private concerns
• Feature requests
• Feedback about GitHub products

Because GraphQL is introspective, the Explorer supports:

• Intelligent typeaheads aware of the current schema
• Validation error previews as you type

If you enter a query that is not well-formed or does not pass schema validation, a popup warns you of an error. If you run the query, the error returns in the response pane.

A GraphQL response contains several keys: a data hash and an errors array.

{
  "data": null,
  "errors": [
    {
      "message": "Objects must have selections (field 'nodes' returns Repository but has no selections)",
      "locations": [
        {
          "line": 5,
          "column": 8
        }
      ]
    }
  ]
}

It's possible you might run into an unexpected error that is not related to the schema. If this happens, the message will include a reference code you can use when reporting the issue:

{
  "data": null,
  "errors": [
    {
      "message": "Something went wrong while executing your query. This is most likely a GitHub bug. Please include \"7571:3FF6:552G94B:69F45B7:5913BBEQ\" when reporting this issue."
    }
  ]
}

Note

GitHub recommends checking for errors before using data in a production environment. In GraphQL, failure is not total: portions of GraphQL queries may succeed while others fail.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4