SYNX registry
The registry holds SYNX packages: reusable configs and schemas you install into a project. Reading is anonymous; publishing goes through the SYNX CLI. The format itself needs no connection to us at all — the parser is a published package (npm i @aperturesyndicate/synx-format), and the language is described in the SYNX guide.
Base URL https://synx.aperturesyndicate.com/apiEndpoints
| Method | Endpoint | Auth | |
|---|---|---|---|
GET | /packages | none | Search and list. ?q=, ?category=, ?limit= (1–200, default 50), ?offset= |
GET | /packages/:scope/:name | none | Package with all its versions |
GET | /packages/:scope/:name/:version | none | One version |
GET | /packages/:scope/:name/:version/download | none | The .tar.gz |
POST | /packages | CLI session | Publish a version |
DELETE | /packages/:scope/:name/:version | CLI session | Withdraw your own version |
Package names are scoped (@scope/name), versions are semver.
curl "https://synx.aperturesyndicate.com/api/packages?q=nginx"{ "total": 0, "packages": [] }The registry is new, and today it is empty.
Publishing
synx login
synx publishFor synx login, open synx.aperturesyndicate.com/api/auth/cli-token, sign in with your Syndicate account, copy the token and paste it when the CLI asks. The registry does not accept Dev Studio keys — it has its own session, and the token works as Authorization: Bearer … on the publish and withdraw endpoints. GET /api/auth/whoami tells you whose token it is.
synx publish validates the manifest, packs the package (up to 6 MB) and uploads it.
Errors answer {"error": "…"}: 400 for a bad name or version, 401 without a session, 404 for an unknown package.