Add a Compliance Configuration
Create a configuration covering the states you name
You name states, not requirement ids
Send alineOfBusiness and a list of stateCodes. Together those select the Turris default compliance requirement for each state, so you never handle a requirement id.
lineOfBusiness is required, and its allowed values are published in the schema below. It is what makes the requirement lookup unambiguous: a state can have one default per line of business, so without it there would be nothing to choose between them.
What can go wrong
isTurrisDefault: false.Idempotency-Key header. See Idempotency.Headers
UUID to ensure idempotent request processing
"550e8400-e29b-41d4-a716-446655440000"
Alternative UUID header for idempotent request processing
"550e8400-e29b-41d4-a716-446655440000"
Body
Configuration name. Must be unique within the entity that owns it.
"P&C"
The line of business this configuration governs. Together with each state code it selects the Turris default compliance requirement to attach.
P&C Commercial, P&C Personal, Surplus Lines, Life & Health "P&C Personal"
The states this configuration covers. Each one attaches the Turris default requirement for that state and line of business. A state with no default for the chosen line of business returns 404, and a state listed twice returns 400.
AL, AK, AZ, AR, CA, CO, CT, DE, FL, GA, HI, ID, IL, IN, IA, KS, KY, LA, ME, MD, MA, MI, MN, MS, MO, MT, NE, NV, NH, NJ, NM, NY, NC, ND, OH, OK, OR, PA, RI, SC, SD, TN, TX, UT, VT, VA, WA, WV, WI, WY, GU, PR, VI, DC Free-text description
"Minimum authority for personal lines."
Which of your entities owns this configuration. Defaults to your own organization.
"6610b3d2c2e0a51b8c0d1f02"