Bytes API
The public Developer API is the /api/v1/* API. It uses a workspace API key and is designed for trusted server-side integrations.
Bytes also provides a hosted MCP adapter for compatible assistants and a public Zapier integration. Both use supported public platform contracts rather than undocumented browser or Admin routes.
Current scope
- create, list, read, update and archive links
- retrieve the governed safe QR for an existing Link
- resolve Activity Groups
- assign links to Activity Groups
- manage workspace tags
- attach and remove link tags
API base URL
https://api.jaww.ws/api/v1
Public endpoints
| Method | Path | Purpose |
|---|---|---|
GET | /activity-groups | List or resolve workspace Activity Groups |
GET | /links | List workspace links |
POST | /links | Create a link, optionally assigned to an Activity Group |
GET | /links/{id} | Read one link |
GET | /links/{id}/qr | Retrieve the standard safe Link QR as PNG, SVG or PDF |
PATCH | /links/{id} | Update a link or reconcile its Activity Group |
DELETE | /links/{id} | Archive a link |
GET | /tags | List tags |
POST | /tags | Create a tag |
PATCH | /tags/{id} | Update a tag |
DELETE | /tags/{id} | Delete a tag |
POST | /links/{id}/tags | Attach tags |
DELETE | /links/{id}/tags/{tagId} | Remove a tag |
Zapier
Jawwws Bytes is available in the Zapier App Directory at:
https://zapier.com/apps/jawwws-bytes/integrations
The current integration supports New Link polling, Create Link, Find Link and Add Tag to Link using the maintained Developer API.
See the Zapier guide.
MCP and assistants
The supported hosted MCP resource is:
https://api.jaww.ws/mcp
It uses Bytes sign-in, explicit workspace selection and scoped OAuth permissions. Customer workspace API keys are not pasted into or stored by the hosted assistant connection.
Bytes is listed in the official MCP Registry as io.github.jawwws/bytes version 0.2.0.
See MCP and assistant connections.
CLI
npm install -g @jawwws/bytes-cli
bytes activity-groups list --slug blog
See the CLI guide.
API keys
Create keys in:
Workspace Settings -> Developer API
Each key belongs to one workspace.
Store keys in environment variables or a secrets manager. Never expose them in browser code, static pages, logs or screenshots.
Start building
- Getting started
- Authentication
- Create and manage links
- Retrieve a Link QR
- Activity Groups
- Zapier
- MCP and assistant connections
- Bytes CLI
- API reference
- OpenAPI
Do not build external integrations against undocumented dashboard routes.