Creative Compliance Standalone (CCSD)

Standalone Creative Compliance APIs — no accountId in the path. These endpoints proxy to the CCSD service and pass through cookies and/or x-api-key headers for authentication.

Parameters

Method	Path	Controller	Auth	Description
POST	/v2/ccsd/validateUser	creativeComplianceStandaloneValidateUser	form + cookie + `x-api-key`	Validate a CCSD user
POST	/v2/ccsd/quota	creativeComplianceStandaloneQuota	form + cookie + `x-api-key`	Get current usage quota
POST	/v2/ccsd/signup	creativeComplianceStandaloneSignup	form + cookie	Sign up a new CCSD user
GET	/v2/ccsd/activate	creativeComplianceStandaloneActivate	query + cookie	Activate a CCSD account (redirect-based)
POST	/v2/ccsd/cmValidation	creativeComplianceStandaloneCmValidation	JSON + cookie + `x-api-key`	Run standalone CM validation
POST	/v2/ccsd/upload	creativeComplianceStandaloneUpload	multipart + cookie + `x-api-key`	Upload a file for a compliance check
POST	/v2/ccsd/usageHistory	creativeComplianceStandaloneUsageHistory	form + cookie	Get usage history
POST	/v2/ccsd/decrementQuota	creativeComplianceStandaloneDecrementQuota	form + cookie	Decrement the usage quota
GET	/v2/ccsd/retrieveGuidelines	creativeComplianceStandaloneRetrieveGuidelines	query + cookie + `x-api-key`	Retrieve brand guidelines
POST	/v2/ccsd/feedback	creativeComplianceStandaloneFeedback	form + cookie + `x-api-key`	Submit compliance feedback
POST	/v2/ccsd/purchaseCredits	creativeComplianceStandalonePurchaseCredits	form + cookie + `x-api-key`	Purchase compliance credits

All CCSD endpoints are unauthenticated at the platform level (no accountId check). Authentication is handled downstream by the CCSD service via cookies and x-api-key**`.`**

Base URL:

{baseUrl} (e.g. https://session-apis.qa5.jivox.com).

All account-scoped paths use :accountId as the account identifier.

Last updated on

Was this page helpful?