Skip to main content
POST
Pull Upstream

Authorizations

Authorization
string
header
required

JWT bearer token signed with your organization's registered signing key. There is no OAuth authorization server; you mint tokens yourself and the token's scopes claim carries the granted permission scopes. Public scopes: git:read (read repository contents), git:write (write branches, commits, tags, and notes), repo:write (create and manage repositories), org:read (list an organization's repositories). Each operation's security requirement names the scopes it requires. See https://code.storage/docs/getting-started/authentication for how to mint tokens.

Body

application/json

Optional sync hints. Most callers can omit the body entirely and simply trigger the next upstream pull.

Optional parameters for triggering a sync from the configured upstream.

after
string

Optional opaque token from a previous pull-upstream response. Reserved for compatibility with future incremental syncs.

ref
string

Optional branch or tag to pull from the configured upstream. Defaults to the repository's tracked default branch.

Example:

"main"

Response

Sync trigger accepted. The repository sync runs asynchronously.

Acknowledgement that an upstream sync has been initiated; the sync itself runs asynchronously.

message
string
required

Human-readable status message.

Example:

"Repository sync initiated successfully"