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 “Asana”

Asana

ResolvedProvenance: Officialanswered in 50.1 ms

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

curl -o openapi.yaml https://swaggerbot.dev/api/specs/e4867e9cd131efa48ae91297e14b0ddd045c1ac767a90a9d84a3ce99ca07f73a/published

The whole answer, as JSON:

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

Spec details

API id
asana.com/asana
API Version
1.0
Spec
OpenAPI 3.0.0 · YAMLe4867e9cd131efa48ae91297e14b0ddd045c1ac767a90a9d84a3ce99ca07f73a
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/Asana/openapi/master/defs/asana_oas.yamlLast verified

How it was answered

Answered from the Index in 50.1 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