Skip to content
ContractSpec
Start here

reference

Scoped social publication providers

Versioned provider execution carries tenant identity and durable local publication keys.

field.key.label
docs.tech.social-provider-v2
field.version.label
field.type.label
field.title.label
Scoped social publication providers
field.tags.label
social,marketing
field.owners.label
field.stability.label
public

V2 publication and status ports require tenant identity, account identity and a durable local idempotency key. Native API idempotency support is independent of that local key. Integrations must bind content, credentials and provider resources to the requested tenant before dispatch. Member-approved requests also carry the approved publicationKind, the owner actorId and the connectionId/connectionVersion the approval is fenced to; adapters refuse before any native effect when the current connection version differs or the plan does not match the approved kind. Partial or uncertain publication remains ambiguous. Multi-part adapters receive the named publishing grant and recheck it before every part. Optional resume crosses fresh authority and a fenced canonical continuation claim; status never publishes pending work.

The social runtime supports an explicit providersV2 map while preserving its legacy providers map. V2 takes precedence when configured; failures do not fall back to another publisher. Resolve legacy ambiguous receipts before switching provider implementations, or supply an explicitly authorized compatibility reader. Draft-only remains the default.