Integrations
Send photos on to PhotoShelter
If you deliver through PhotoShelter, GalleryID can hand finished galleries to it for you. Photos go over FTP with the names already embedded, then get filed into a PhotoShelter gallery through its API.
Before you start: PhotoShelter has to be enabled for your organization, and you need the PhotoShelter export permission.
Connect an account
Go to Org Dashboard → PhotoShelter and choose Add Destination. Fill it in this order, because the connection test is what loads your collection list.
- 1
Name it
Anything you will recognize later. Photographers who deliver to two PhotoShelter accounts keep one destination each. - 2
Add the API credentials
API Key, Email and Password. Agency accounts also need the Organization ID. - 3
Press Test Connection
This is not optional housekeeping. Until it succeeds the collection picker stays empty and reads Test connection to load collections. - 4
Add the FTP credentials
These are a different set from the API ones. PhotoShelter keeps them under Settings → FTP Access. Photos travel over FTP, so an export cannot run without them. - 5
Choose where galleries land
Pick a Default Collection and a Gallery Visibility of Private, Public or Unlisted. Leave Create gallery per event on and each GalleryID gallery gets its own on the other side.
Turn on the export
Under Export Options, tick Enable auto-export and finished galleries send themselves once facial recognition has run. A second option appears underneath: Export after names are written waits until the names are embedded in the files before anything leaves, which is usually what you want, because it is the difference between delivering captioned files and delivering bare ones.
What arrives
- •The original file, byte for byte. Nothing is resized or re-encoded on the way.
- •Whatever metadata is already embedded, which is why the wait-for-names option matters.
- •The filename as it stands in GalleryID. There is no separate naming pattern for this route.
Related