Integrations

CS Play integrates with CityScreen platform services and external systems. Configure integrations in Settings > Integration.

Your Organization OID is displayed at the top of the integration page — external services use it to identify your account.

CS Context

CS Context is the CityScreen supply-side platform (SSP) that connects your screen inventory to programmatic demand. It runs real-time auctions and contextual targeting for available ad slots.

Configuration

  1. Go to Settings > Integration > CS Context settings.

  2. Toggle Enabled.

  3. Fill in the Token and Url — the recommendation endpoint provided by your CS Context instance.

  4. Optionally enable BBDO CoT.

  5. Click Save, then Integrate to complete the connection.

For preparing screens and allocating programmatic slots, see Programmatic advertising.

Sedooh

Sedooh is a third-party verification service that independently confirms your ad plays actually happened.

Configuration

  1. Go to Settings > Integration > Sedooh settings.

  2. Toggle Enabled.

  3. A Token is generated automatically. Use Update token to regenerate or Delete token to revoke access.

  4. Enable Turn on by default for new advertising campaigns to automatically include new campaigns in Sedooh verification.

WebDAV access to photo captures

WebDAV exposes your organisation’s CamGrabber photo captures over a standard protocol, so you can pull them into your own storage or reporting without going through the web interface.

It is read-only: you can browse and download photo captures.

Turning it on

  1. Go to Settings > Integrations > WebDAV settings.

  2. Tick Enabled.

  3. Press Generate login and password.

The URL, the login and the password are all issued by the system and shown read-only on the same page — you do not choose them.

Generating credentials immediately invalidates the previous pair. Update whatever pulls the files before you press the button.

Share the new credentials only with people you know need the captures. When someone asks you to generate or send them, confirm who is asking first.

Connecting a client

Any standard WebDAV client will do — Finder, Windows Explorer, CyberDuck, WinSCP, cadaver, rclone. Enter the URL and the generated credentials; authentication is HTTP Basic. You see your own organisation’s directory.

How the tree is laid out

Captures are grouped by hour, then by campaign and advertisement:

<organisation id>/
└── camshots/
    └── 2025-09-23T110000/       one hour
        └── 622539/              campaign id
            └── 1285964/         advertisement id
                └── 2097_5428_7e4fd315_..._Dlia_HR_Iekatierinburgh_576kh432.jpg

The file name itself carries the player id, the frame id, the uuid of the ad play and the transliterated name of the advertisement — enough to match a photograph to a row in your ad play statistics without opening it.

Limits

The service is rate-limited on requests and on bandwidth, and your provider may close it during peak hours. Pull history outside the busy part of the day rather than in one burst at prime time.

Troubleshooting

Connection refused

Check that WebDAV is enabled in your settings. It requires the Enterprise tier — see License Tiers.

Authentication failed

Check that you are using the current credentials. If in doubt, generate a new pair.

The directory is empty

Captures exist only for hours in which a CamGrabber actually photographed an ad play. See CamGrabber Photo Reports for registering a grabber and setting its schedule.