mocop
Browse · Docs · Guide · Analyze

OTInstaller Registry API

API by OTInstaller · rest

Public reads need no sign-in and are cached at the edge (Cache-Control says for how long); every JSON read has an ETag, so If-None-Match gets a 304. Errors are {error: {code, message, hint, docs}} (https://otinstaller.com/schema/error-v1.json), with codes at https://otinstaller.com/docs/errors. 429s carry Retry-After. Signed-in calls take an ot_ token as a bearer token; each operation's x-scope names the scope a token needs. Times are Unix milliseconds. Guide: https://otinstaller.com/docs/api

Endpoint: https://api.otinstaller.com/v1

Verification: observed. Source: crawl.

Capabilities (164)

  • What changed across the registry newest first
  • An image from a README guide or docs page by SHA-256
  • Start a device sign-in as `ot login` does
  • Poll a device sign-in; answers status pending slow_down expired denied or…
  • End the browser session
  • Trade a CI run's OIDC ID token for a registry token (trusted publishing ot…
  • OAuth callback (redirects)
  • Start a browser sign-in (redirects)
  • Edit your comment (within 24 hours)
  • Withdraw your comment
  • How many visible packages match each facet value
  • Feedback to the team (anonymous unless signed in)
  • Flag a post or a tool request for a moderator
  • Search guides (as /tools?kind=guide)
  • A guide and its pages
  • A guide version
  • One guide page (?format=html or md)
  • Liveness check
  • Your import drafts
  • Start importing a repository (or up to 50)
  • An import draft
  • Change an import draft
  • Finish an import: a pull request or a registry-held manifest
  • Anonymous install count (one per address version and day)
  • Open broken outdated and wrong-information issues across the registry
About · Contact · Privacy