Skip to main content

​
Overview

Use 9pic-media-sell when you take payment yourself and 9Pic supplies the photos. Guests see thumbnails and watermarked images. After you confirm a sale in your system, your backend calls Download Originals. Payment stays in your checkout. 9Pic does not process the card, create the order, or send the receipt. Also install API Skill and Participant App.

​
Install

To install every 9Pic skill, see Agent Skills.

​
Call Path

The browser never holds X-API-Key and never fetches originals until your backend has recorded a paid order.

​
Workflow

1

Find photos

Follow Participant App: Event Details flags, then Face Search and/or BIB Search. Persist bib or request_id.
2

Show previews only

Grid: thumbnail_url. Large view: img_url (watermarked). See the Image model. Do not send unwatermarked files to an unpaid guest.
3

Take payment

Your checkout, your provider, your receipts. 9Pic is not involved in this step.
4

Store the purchase

Persist order id, buyer, and which bib / request_id / image ids were sold — in your system.
5

Unlock originals

Your backend calls Download Originals using the identifier on that page. Generate presigned URLs on demand; do not cache them past expiry.

​
API Pages

​
Integration Notes

  • Originals only after you have confirmed the sale. The API key stays on your backend.
  • Until then, guests get thumbnail_url and img_url.
  • Import, process, and go-live are organiser pipeline endpoints — see Memories.
  • Flow, Certify, and Buzz have no public /ext/ API.

Participant App

Search and preview gallery before a sale.

Download Originals

Presigned unwatermarked files after a confirmed sale.

API Skill

Auth, envelope, backend-for-frontend.

Image model

thumbnail_url, img_url, original_url.