AmLang registry API

The extension catalog, the accounts that publish releases, and public bug reports and feature requests. Catalog reads and issue submissions need no credential.

APIs

Use https://tucan.amlang.net/api as the base URL for new API clients. All existing API paths without /api remain available with the same methods, data, and authentication. These are direct aliases, so POST, PUT, PATCH, and DELETE requests do not redirect. Browse extensions at /add-extensions and API documentation at /docs/api.

page	covers
Extension API	the data model, every endpoint, the JSON shapes, how to organise and pack an extension's files, and how to publish a release
User API	signing up with an emailed code, logging in for an access token, passing it, what each failure code means, and what your account can then do
Issues API	submit a bug report or feature request with a contact email; no account required

How it is shaped

An extension is identity — an id, a name, a description — and it is created once. Each of its versions is a release, owning everything that changes between releases: notes, permissions, menu items, and the resources it is made of. A resource is one file, either hosted here or declared as coming from Aminet or a URL.

That split is why an old release stays installable: nothing about it is overwritten when a new one is published. Approval applies to the extension and to each version independently, so a new version can be staged while the published one keeps serving.

Applications — the IDE itself, say — use the same table, versions and resources, listed separately under /applications so an app update never shows up as something to install as an extension.

Start here

curl "https://tucan.amlang.net/api/extensions"                       # the catalog: latest version of each
curl "https://tucan.amlang.net/api/extensions/bebbossh"              # identity + latest release info
curl "https://tucan.amlang.net/api/extensions/bebbossh/v"            # every published version
curl "https://tucan.amlang.net/api/extensions/bebbossh/v/1.0.0"      # one release, and its resources

Those need no credential. Publishing does — either the development secret in the URL or an admin token in a header, both described under Publishing.