Assign a Producer to Entities
Attach an existing producer to more of your entities
Already-associated entities are skipped, not rejected
Unlike Add a Producer, sending an entity the producer is already on is not an error. The two requests mean different things: “create this person” twice is a mistake worth a 409, while “make sure they are on these entities” twice is the same instruction, and a caller adding one branch to a list of five should not have to diff the list first.Scope
The producer must already be associated with at least one entity in your subtree, or the request returns 404 — you cannot pull an arbitrary producer id off the platform into your organization. Every id inentityIds must be in your subtree as well.
Send an 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"
Path Parameters
The unique identifier of the producer (the producerId returned by the List Producers endpoint).
"6627f2b5c2e0a51b8c0d4e7c"
Body
The entities to associate the producer with. Ids the producer is already associated with are skipped rather than duplicated, so the request is safe to repeat.
Contact email on the new associations
"example@test.com"
Contact phone number on the new associations
"+12155550100"
Job title on the new associations
"Producer"
States where this producer is a Designated Responsible Licensed Producer for the new associations.
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