# Check a shift's application form

Runs the answers to a shift's application form through that form's own rules and
returns the values it accepted.
**Nothing is stored and no application is made.** This is the step before applying:
it tells you whether the answers will be accepted, so a form that is wrong is
caught while the person is still filling it in. Send the same answers as
`application_form` on the entry for this shift when you apply.
The fields it accepts are whichever ones your account has configured on the form
attached to this shift, under the codes you gave them, so they differ from account
to account and from shift to shift. A field that fails its rule comes back as a 422
keyed by that code. The response echoes the values back, with any file answers
replaced by the URL they were stored at.
A shift with no application form on it returns a 404.
`asLeader` decides which permission is checked before any of this happens: with it,
whether the person can lead the shift, and without it, whether they can take an
ordinary place on it. It changes nothing about the form itself, and it is not one
of the values returned.

Endpoint: POST /api/v2/event/shift/{shift_id}/submit-application
Version: 2.0.0
Security: default

## Path parameters:

  - `shift_id` (integer, required)
    The ID of the shift.

## Header parameters:

  - `Rosterfy-Platform` (string)

## Request fields (application/json):

  - `asLeader` (boolean)
    Check whether the person can lead this shift rather than take an ordinary place on it. The name is camelCase because that is what the endpoint reads.

## Response 200 fields (application/json):

  - `user:first_name` (string)

  - `user:last_name` (string)

  - `user:email` (string)

  - `user:dob` (string)

  - `user:terms` (integer)

  - `user:custom_multiselect_attribute` (string | null)