HTTP dataflow execution

The HTTP data plane stores registration state, dataflows and request logs. Its UI exposes runtime status and logs. Dataset authoring and consumer testing belong to applications such as Dataspace Starter.

The provider control plane selects a registered data plane by dataset ownership and its https://w3id.org/dspace-sig/profile/http-pull profile. It sends one start request with the transfer ID and private backend metadata. The data plane stores the flow and returns a proxy address, an expiring access JWT and a refresh grant. The consumer-pull side needs no local data plane.

Suspend, resume and terminate operations use the corresponding /dataflows/:id endpoints. Runtime completion and error notifications go to the tenant-scoped control-plane transfer callback API. API paths above are relative to the component's configured API base, including any subpath.

See configuration, data access credentials and dataset publication.

Call sdk.transfers.dataAccess(transferId) before sending each data request. The control plane serializes renewal for the transfer and persists the rotated credentials before returning its endpoint and headers. The application sends the request itself. After a 401, it may call dataAccess with { forceRefresh: true } and decide whether the data request is safe to retry.

Suspend, completion and termination revoke access and renewal. Resume returns fresh credentials and keeps the original backend metadata snapshot. Preserve the signing key and database across restarts, and deploy one HTTP data-plane replica. If the provider rotates a refresh grant but the consumer crashes before saving it, the old grant cannot be reused; starting a new transfer may be necessary.