Referencelatest · 0.1.2
Registry API
The HTTP calls behind the commands, for debugging and scripting.
Registry calls go to https://api.horizech.com with Authorization: Bearer <access token> when signed in. Responses are the envelope { Success, Data, ErrorCode, AdditionalErrorInformation }, except a successful download, which is the zip with X-Package-Version, X-Package-Channel and X-Package-File-Hash headers.
| Method | Path | Used by |
|---|---|---|
GET | /api/v1/packages | package list, finding --org |
GET | /api/v1/packages/:org/:code | package info, publish |
GET | /api/v1/packages/:org/:code/versions | package versions |
GET | /api/v1/packages/:org/:code/versions/:version/manifest | publish, promote |
GET | /api/v1/packages/:org/:code/versions/:version/download | download |
POST | /api/v1/packages | publish --create |
POST | /api/v1/packages/publish | publish |
POST | /api/v1/packages/:org/:code/promote | promote |
Publishing (multipart)
| Field | Value |
|---|---|
OrganizationSlug | The organization. |
Code | The package code. |
Channel | Always sent; dev by default. |
Manifest | package.hws from the zip (without a byte-order mark). |
File | The zip. |
ReleaseNotes | From --notes, when given. |
Identity provider
On https://horizech.com.