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 “supabase management”

Supabase API

ResolvedProvenance: Officialanswered in 8.4 ms

By supabase.com · Verified

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

The whole answer, as JSON:

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

Spec details

API id
supabase.com/api
API Version
1.0.0
Spec
OpenAPI 3.0.0 · JSONfc33202345e876c03ac9a725d702e5d792c83bb272225ae9a83ef90fc1ef453b
Validity Issues
17 findings; none stops the Spec being used
  • must be equal to one of the allowed values: array, boolean, integer, number, object, string /components/schemas/V1CreateProjectBody/properties/release_channel/type ×5
  • Property propertyNames is not expected to be here /components/schemas/ApiKeyResponse_Output/properties/secret_jwt_template ×3
  • type must be boolean /components/schemas/DiskAutoscaleConfig_Output/properties/growth_percent/exclusiveMinimum ×3
  • Property $schema is not expected to be here /paths/~1v1~1projects~1{ref}~1jit-access/get/responses/200/content/application~1json/schema ×2
  • Property const is not expected to be here /paths/~1v1~1projects~1{ref}~1jit-access/get/responses/200/content/application~1json/schema/oneOf/1/properties/state ×2
  • Property contentEncoding is not expected to be here /components/schemas/V1UpdateFunctionBodyEszip
  • Property examples is not expected to be here /components/schemas/V1UpdateFunctionBodyEszip
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://supabase.com/openapi.jsonLast verified

How it was answered

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