No provision is made in this API for producer-consumer communication. All such communication must be done independently of the API.
An example workflow is:
The producer posts the availability of specific images on a public website.
A potential consumer provides the producer with his/her tenant ID and email address.
The producer uses the Images v2 API to share the image with the consumer.
The producer notifies the consumer via email that the image has been shared and what its UUID is.
If the consumer wishes the image to appear in his/her image list, the Images v2 API is used to change the image status to
accepted.If the consumer subsequently wishes to hide the image, the Images v2 API may be used to change the member status to
rejected. If the consumer wishes to hide the image, but is open to the possibility of being reminded by the producer that the image is available, the Images v2 API may be used to change the member status topending.
Note that as far as this API is concerned, the member status has only two effects:
If the member status is not
accepted, the image will not appear in the consumer's default image list.The consumer's image list may be filtered by status to see shared images in the various member statuses. For example, the consumer can discover images that have been shared with him or her by filtering on
visibility=shared&member_status=pending.
