Validate a compose file
  POST /api/v3/organizations/{organisation}/compose/validate    
 Accepts a docker-compose.yml file content, translates it into the internal compose definition format, and validates it. Supports image tag suffixing via the imageSuffix query parameter or by sending a JSON wrapper with yamlContent and imageSuffix fields. When provided, internal image tags are transformed to {containerName}-{suffix} format (e.g., ‘nginx-feature-xyz’).
Authorizations
Parameters
Path Parameters
The organisation ID
Query Parameters
Optional. Image tag suffix to apply during translation. Transforms internal image tags to consistent ‘{containerName}-{suffix}’ format (e.g., ‘nginx-pr-456’). External images are left unchanged. Useful for feature branch deployments.
Example
pr-456Request Body required
The docker-compose.yml file content. Can be sent as raw YAML string or as a JSON wrapper containing both yamlContent (string) and imageSuffix (string) fields. Query parameter imageSuffix takes precedence if both are provided.
object
The docker-compose.yml file content as a string
Optional image tag suffix (query parameter takes precedence)
Optional application name for context
Responses
200
Validation successful. Body contains the translated compose definition and any warnings.
object
Docker-compose YAML translated and validated successfully.The translated internal compose definition format
object
Optional warnings encountered during translation
[  "Service 'db' uses 'build' directive, image will be internal with a generated tag.",  "Volume 'cache' uses a relative path source, interpreted as logical volume name."]422
Invalid YAML input or validation failed
object
Invalid YAML