schedule content to broadsign control players via the broadsign control rest api

Steps

1. Request Broadsign Control API access for a specific domain user by emailing Broadsign services with the user ID — API access is provisioned per user, not self-serve signup
2. Generate an HTTP bearer token in Broadsign Control Administrator (user properties > credentials tab) for sandbox testing against api-sandbox.broadsign.com
3. For production, generate a private key, submit a certificate signing request (CSR) to Broadsign services, and assign the returned public key fingerprint to the API user (mutual-TLS auth against api.broadsign.com)
4. Use the REST method reference (Swagger UI at docs.broadsign.com/swag/swagger-ui-master) to find campaign, content, and player/loop endpoints
5. Import content, build/update a campaign or schedule, and assign it to the target players via the relevant REST endpoints
6. Validate fully in the sandbox domain before cutting over to the certificate-authenticated production domain