An HTTP payload contract specifies the request-body fields, data types, and JSON validity requirements that an endpoint accepts. In API testing, it turns a user story and Swagger schema into concrete risks to investigate. section 11.2.2
Branding update request
A PUT request to /branding/ should include branding data such as name, map coordinates, logoUrl, description, and contact details. Useful negative tests omit required fields, send incorrect types, or provide JSON that violates the Swagger schema. A successful request returns 200 OK; bad or missing data returns 400 Bad Request. section 11.2.2
{
"name": "string",
"map": {
"latitude": 0,
"longitude": 0
},
"logoUrl": "string",
"description": "string",
"contact": {
"name": "string",
"address": "strings",
"phone": "string",
"email": "string"
}
}
Inspect a representative payload shape, including nested map and contact objects, before designing valid and invalid requests. section 11.2.2
