Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell EMC PowerFlex Manager API Guide

PDF

Message body validation

Message bodies are subject to a wide range of validations. Capturing every validation rule is beyond the scope of this document but a few general rules are worth noting.

  • In general, validation failures generate exceptions and structured messages to isolate the violation. See the section on Exception handling for more details. Most validation exceptions return a 400 HTTP response, but some API methods generate specific HTTP response codes to indicate particular exceptions. The response codes are listed in the API reference in the Appendix.
  • Uniqueness validations - many models require unique names. Notable models include ServiceTempate, Deployment, Network, User. This violation returns a 409 HTTP response in these cases.
  • Relationship constraints - an exception occurs when you try, for example, to delete an entity that is in use by another entity.
  • If a ServiceTemplate contains a server component, and a hostname is supplied with a hostname_template (hostname generator), a validation exception is not generated. The preference is to use the hostname_template.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\