Send approved photos to your own display

Open the experience, select the Submissions tab, open the more options menu on the toolbar, and turn on Hold for Approval. From then on every new photo waits under Awaiting Approval until staff decide.

Staff review from the same tab: select photos and choose Approve or Reject, or open a photo and decide there. Approved photos reach Snapbar displays and your endpoint; rejected photos go nowhere.

Create a live API key with Manage notification endpoints and Read submissions in Integrations > Developer, as described in Create API keys.

Find the activation id. List the activations in the account and copy the id of the experience (its short_id and name match what the dashboard shows).

curl --fail-with-body \
  --header "Authorization: Bearer ${SNAPBAR_API_KEY}" \
  https://integrations.snapbar.com/v1/activations

# { "data": [ { "id": "2f5c1a8e-…", "short_id": "exp_Abc123Def456", "name": "Summer Launch", … } ], … }

Register your receiver for the approved event only, with the photos-only policy, scoped to that activation id. media_only delivers every approved photo whether or not the guest left contact details, and the envelope carries lead: null.

curl --fail-with-body \
  --request POST \
  --header "Authorization: Bearer ${SNAPBAR_API_KEY}" \
  --header 'Content-Type: application/json' \
  --data '{
    "url": "https://your-display.example.com/snapbar",
    "event_types": ["submission.approved"],
    "consent_policy": "media_only",
    "experience_ids": ["2f5c1a8e-7d3b-4e1f-9a6c-0b8d4e2f1a37"]
  }' \
  https://integrations.snapbar.com/v1/webhook-endpoints

Store the signing_secret from the response and verify every delivery with it, following Receive signed webhooks at your own endpoint. The endpoint is live as soon as it is registered.

Take a real photo through the experience. Confirm it appears under Awaiting Approval and that nothing reaches your receiver.

Approve it. After the 10-second retraction window, confirm your receiver gets a submission.approved delivery whose media array holds the finished photo. Reject a second test photo and confirm nothing arrives for it.

Check Integrations > Activity for a Delivered row per approved photo. A Retrying or Action needed row means your receiver did not answer 2xx; fix it and replay from there.

Pause your wall updater, keep durably accepting signed webhooks, and record the affected activation and old endpoint IDs. Fix and register a replacement endpoint, install its secret, and verify a synthetic send before resuming.

Drain GET /activations/{id}/submissions?approved_only=true&limit=100 through every next_cursor, without completed_after. Build a temporary set of submission IDs and visible media IDs. Do not clear the current wall after a failed or partial scan.

After a complete scan, upsert approved photos and remove cached submissions/media absent from that set. Full scans are not atomic snapshots: re-read any item changed by webhooks during the scan before applying it, process buffered IDs through GET /submissions/{id}, and repeat the scan to converge.

For an urgent removal, staff identify the submission ID in Activity, hide/reject/delete it in Snapbar as appropriate, and remove every associated file, thumbnail, wall entry, and CDN copy in the receiving system. Verify both the wall and a direct file URL. Keep a local suppression record so an older buffered webhook cannot restore it.

Use the runnable poller for incremental catch-up with overlap and periodic complete reconciliation. Approval after completion, regeneration, hiding, and deletion may not change completed_at, so incremental polling alone is not a removal feed. Agree a reconciliation interval and a named removal operator before opening the event.