Skip to main content
POST
Pull Upstream

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

repo_name
string
required

Repository name. Names that contain / or any other character that is not safe in a URL path segment must be URL encoded so the value occupies a single path segment. For example pierre/example is sent as pierre%2Fexample. Plain names such as example can be sent as-is. The server URL-decodes the value before resolving the repository.

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"