Skip to content
SwaggerBot
Get an API keyGet a key

Resolved

The name is one API, and its Spec is confirmed to describe it: here it is, with where it came from.

You looked up “github”

GitHub v3 REST API

ResolvedProvenance: Officialanswered in 289.7 ms

By github.com · Verified · Stale: a Lookup queues a new Verification

curl -o openapi.json https://swaggerbot.dev/api/specs/3177ad6a86ca04c57a9bef3fc24e28a339efb8eb040c6f950af3d3ed2fee7fa3/published

The whole answer, as JSON:

curl -X POST https://swaggerbot.dev/api/lookup -H "Content-Type: application/json" -d '{"name":"github"}'

Spec details

API id
github.com/github-v3-rest-api
API Version
1.1.4
Spec
OpenAPI 3.0.3 · JSON3177ad6a86ca04c57a9bef3fc24e28a339efb8eb040c6f950af3d3ed2fee7fa3
Validity Issues
None
Normalized Form
Download the Normalized Form · one bundled document in the current OpenAPI version

Alternate Specs

None: the Current Spec is the only one.

Sources

  • Provenance: Officialhttps://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.jsonLast verified

How it was answered

Answered from the Index in 289.7 ms; no later step was needed.

The six steps of a Lookup
  1. IndexSpecs verified before. Answered in milliseconds, no key needed.Answered here
  2. APIs.guruThe public directory of API descriptions.Not needed
  3. Developer PortalFound with a web search.Not needed
  4. Vendor domainKnown paths, apis.json, then a shallow crawl.Not needed
  5. GitHubThe Vendor's organisation first, then the rest.Not needed
  6. JudgedIs it the API you meant, and its Spec? Not sure means we say so.Not needed

Look up another API