Revoke a share

POST 
/api/v1/shares/:share_id/revoke

As the publisher, revokes the whole share and every acceptance of it; terminal. Each project whose acceptance was active gets a share_revoked activity entry. As a grantee (project_id, or a credential scoped to it), revokes that project's own acceptance, which it may accept again later; while the project's own resources still name the shared resource (see GET /api/v1/shares/{share_id}/references), that answers 409 SHARE_IN_USE unless force=true. A publisher's revoke is never refused on that account. Idempotent.

Request

Responses

200

The share after the revoke, with the grantee's acceptance when a grantee revoked

401

Unauthorized

403

Forbidden

404

Share not found, not addressed to the project, or never accepted by it

409

SHARE_IN_USE: the grantee's resources still name the shared resource. error.meta.references lists them.