Convert a submission
Joins a submission to the person who sent it and marks it converted. Send an empty object to make a new person from it: their name, email, and answers to questions about the person, and for a volunteer, foster, adoption or donor form the matching role (volunteer, foster, adopter or donor). That needs write on People, and is refused with 409 when somebody with the same email is already on file; the refusal carries their person_id, so you can link instead. Send a person_id to link a person already on file; that needs read on People. Either way it also needs write on the area of the form’s kind. A submission already joined to a person is refused with 409, and that includes one with an email, which is joined to a person by itself when it arrives (see converted_how). An answer the person record would refuse (an email, phone, number or date that is not one) is refused with 400 before anything is made, naming the answer in field; correct it with POST /api/forms/submissions//corrections and convert again. Once joined, any workflow your organization set to run when such a form is received starts for the person, then any set to run on a decision already made, and an adoption or foster form becomes its application record.
Authorizations
Response
The submission, as it now is, with its form's title, address and kind. It is not wrapped in a submission object, and has no assignees or application status.
One submission. The list also carries the form's title, address and kind, the application made from it, and the assignees; changing one returns the submission alone.
new until somebody reviews it; reviewed; converted once somebody converts it (see Convert a submission); spam, which is kept but left out of the list unless you ask for it. A submission caught by the spam trap on your public form arrives as spam. A submission joined to a person by itself when it arrived stays new, because nobody has reviewed it yet.
new, reviewed, converted, spam created when the person was made from this submission, linked when they were already on file. Null until the submission has a person, which happens when the address it carried confirms it (see verification_state) or when somebody adds them by hand.
created, linked, null Whether the address on the submission has confirmed it was them. A public submission creates no person, no application and no checklist until it does. not_required: no email address on it, or somebody added the person by hand. pending: waiting, and verification_sent_at tells you whether the email has actually gone out. verified: confirmed, by them or by a member of staff adding them. unreachable: they have opted out of your email or the address bounced, so nobody is coming and it is yours to decide.
not_required, pending, verified, unreachable What a form is for, which decides the area its submissions belong to and so which keys may read them. adoption_application, foster_application and surrender (a surrender request) are Animals; volunteer (a volunteer sign-up) is Shifts; donor is Fundraising; contact and general are People.
adoption_application, foster_application, volunteer, donor, surrender, contact, general 
