Sign in
workspace

store the caller's own token for the remote deploy target

Changed on

The token is checked against the target's whoami before it is stored. target names the target the token was obtained for, and the request is refused if the workspace now points elsewhere, so a token is never sent to an instance it was not meant for.

post/w/{workspace}/remote_deploy/connect

Request

  • Base URL: /api (relative, and the document was published on a file host, not at the API’s origin)
  • URL: /api/w/{workspace}/remote_deploy/connect
  • Auth: one of:
    • HTTP bearer
    • API key in cookie token

Path parameters

workspacestring required

Request body

tokenstring required

Response

the stored connection

remote_emailstring required

identity the stored token has on the remote instance

proxy_keystring required

goes in every proxy URL, /w/{workspace}/remote_deploy/proxy/{proxy_key}/{route}

connected_atstring date-time required

Changes