dotsy API
API by dotsy · rest
Build, edit and publish dotsy sites over HTTP. The dashboard, the dotsy CLI and the MCP server all use this API. Production base URL: https://api.dotsy.ai. The Try it console in this reference sends requests to the origin you are reading it on, so it needs no host setting. Authentication Send Authorization: Bearer <token> on every request. Three kinds of token work: - Account API key (pga_…). Create one in the dashboard or with POST /api/v1/account/keys. It acts as one account. - OAuth token. MCP clients that sign in with OAuth send their opaque access token in the same header. - Guest token (pgg_…). POST /api/v1/anon/sites returns one with a new site. It works on that one site only, and publish, rename, delete, domains, imports and asset writes need an account instead. To choose the workspace a request acts in, send X-Dotsy-Workspace: <workspace id or slug>. It applies to sign-in sessions and OAuth tokens. A pga_ key is tied to one account…
Endpoint: https://api.dotsy.ai/
Verification: observed. Source: crawl.
Capabilities (173)
- Early access settings for the active workspace
- Opt in or out of early access
- List the workspace's API keys
- Create an API key
- Change an API key's name scope or sites
- Revoke an API key
- Get the current account user and workspaces
- Read the signed-in person's email notification settings
- Change how often a workspace emails this person
- List recent notifications for the signed-in person
- Dismiss notifications
- Mark notification items read
- Snooze a Needs-you notification
- Needs-you and unread-update counts
- Your pinned sites
- Import pins from a browser
- Rename the workspace
- Resolve an old workspace URL
- List pending workspace invitations
- Invite a teammate to the workspace
- Cancel a pending workspace invitation
- List the workspace's members
- Remove a member from the workspace
- Change a workspace member's role
- Get the workspace plan and usage