Skip to main content
POST
Re-fetches the directive’s content from its upstream source (for example a GitHub repo) and overwrites it in place. The directive keeps its id and its attachments, so everything already pointing at it picks up the new content; a rebuild is queued only when the content actually changed. If the upstream payload is identical, nothing is written and the response carries no_changes: true. Locked directives cannot be resynced. Required scope: context:write

Path Parameters

string
required
The directive ID to resync (e.g. dir_abc123).

Headers

string
required
Bearer token. Example: Bearer runtm_xxx
string
Scope to an organization.

Body

No fields. Send an empty object; the shape is reserved for future options.

Response

object
The directive resource after the resync.
boolean
true when the upstream content was identical and nothing was written.