Developer Help Center

Validating Releases

Use the validate resource to run an automated validation of a release's metadata. The validation process checks a release for various errors, some of which indicate there may be a problem and others which must be corrected before distribution can proceed.

  • Validation errors with a severity of 1 must be resolved before a release can be distributed.

  • Validation errors with a severity of 2 indicate a probable issue, but do not prevent distribution.

Warning

You are responsible for providing acceptable release metadata. Failing to correct inappropriate metadata will result in stores rejecting your releases and will ultimately result in a suspension of your distribution privileges.

POST /distribution/release/{releaseId}/validate

Table 1. URL Parameters

Parameter

Description

releaseId

The ID of the release to validate. This ID was returned in the /content/release/save request which created the release.



Table 2. Query String Parameters

Parameter

Description

token

Optional*

Access token returned upon authentication.

*Providing a token is mandatory, but alternatively, it can be provided as a header. See Authentication and Headers.



curl -X POST 'http://staging-api.revelator.com/distribution/release/540168/validate?Token=75b399be-a3e7-4785-b0e0-35064b77b7ac' 
Table 3. Response

Response Body

  • If the release has no errors: None

  • If the release has errors: See example.



[ 
    { 
        "objectId": 540168, 
        "objectType": "Release", 
        "field": "PosterImage", 
        "errorMessage": "Release level: The cover image for this release is missing.", 
        "value": null, 
        "severity": 1, 
        "errorCode": 11051 
    }, 
    { 
        "objectId": 540168, 
        "objectType": "Release", 
        "field": "Tracks", 
        "errorMessage": "Release level: The release must include at least one track.", 
        "value": null, 
        "severity": 1,
        "errorCode": 11081 
    } 
]