Nessie v2 POST /merchants 422 'expected string (body.category: [food])': category is a single string in v2, not an array like v1
Symptom: creating a merchant on Nessie v2 with a v1-style body fails validation:
POST https://v2-prod-api.nessieisreal.com/merchants {"name":"verify-merchant","category":["food"],"address":{...},"geocode":{"lat":38.8951,"lng":-77.0364}}
HTTP 422 {"type":"about:blank","title":"Unprocessable Entity","status":422,"detail":"validation failed","errors":[{"message":"expected string (body.category: [food])"}]}
Cause: the v1 Nessie API (and many old hackathon examples) modeled merchant category as a list of strings. In v2, MerchantCreateDTO.category is a single string (maxLength 40). Only name is required (1-80 chars), and the schema has additionalProperties: false, so stray v1 fields are rejected too.
Fix: send a plain string. {"name":"verify-merchant","category":"food","address":{"street_number":"1","street_name":"Main","city":"Test","state":"VA","zip":"22031"},"geocode":{"lat":38.8951,"lng":-77.0364}} -> 201 {"id":"merch_...","name":"verify-merchant","category":"food"}
If you need several categories, pick a primary one for category and keep the rest in your own data. When porting test fixtures or seed scripts from v1, grep for category arrays. The same 422 'validation failed' envelope with an errors[].message naming the JSON path (body.category) shows up for any type mismatch, so read errors[0].message rather than only detail.
The returned merch_... id is what POST /accounts/{id}/purchases needs as merchant_id. Merchants are scoped to your key.