Upload images that are tied to a specific Exhibitor.
You must have the exhibitors
ConventionPrivilege to manage this,
or control an Exhibitor to manage images specific to that exhibitor.
Exhibitor Images are accessed via /api/exhibitorimage
.
See "Object Properties" in Introduction for basic shared properties.
Complete details in ExhibitorImageProperties. It also has these extra read-only properties:
A link to the location where the image is stored, minus the protocol (ie https).
A link to the location where a thumnail of the image is stored, minus the protocol (ie https).
See "Related Objects" in Introduction for how to use them.
The Exhibitor this exhibitor image belongs to.
The services used to fetch and manipulate exhibitor images.
This will search across all conventions. To search on a single convention see "Relationships" in Convention.
GET /api/exhibitorimage
Searches a partial name.
Returns:
{ "paging" : {...}, "items" : [ { "id" : "xxx", "filename" : "pic.jpg", ... }, ... ] }
POST /api/exhibitorimage
This is a special field that only exists for uploading the image. It should be an encoded image in the POST body as multipart/form-data
as specified in RFC-2388 (https://tools.ietf.org/html/rfc2388).
When you upload the image it will automatically be resized to 700px wide maintaining its aspect ratio. If you don't want a resize to occur then set this field to 1
.
Returns the same as a normal read.
GET /api/exhibitorimage/xxx
Returns:
{ "id" : "xxx", "filename" : "pic.jpg", ... }
PUT /api/exhibitorimage/xxx
Returns the same as a normal read.
DELETE /api/exhibitorimage/xxx
Returns:
{ "success" : 1 }