# Review certificate data without creating anything.

**POST /api/v1/files/certificates/evaluate**


Runs the fields read off a certificate through the same review a submitted
certificate gets — your organization's insurance requirement, the same rules,
the same pass/fail messages — and reports what is still missing, phrased as
questions. Nothing is stored. Use it to check a certificate an assistant read
in a chat, then submit it with `POST /files/certificates` once it is complete.




## Servers
- Production server: https://api.1099policy.com (Production server)



## Parameters



### Body: application/json (object)

- **certificate** (object)
  The fields read off the certificate, in the shape `review_results.full` returns as `parsed_certificate_json`.

- **contractor** (string)
  Optional. The contractor (cn_…) the certificate belongs to; lets the review compare the insured name against the contractor.

- **entity** (string)
  Optional. Review against the requirement tied to this entity.

- **insurance_requirement** (string)
  Optional. Review against this requirement (ir_…).



## Responses
### 200
`verdict` ("approved" or "flagged" as things stand), `complete` (no open questions), `results` per rule with `result` and `message`, `missing` (`path`, `coverage`, `question`), `coverages_present`, `coverages_required`, the normalised `certificate`, and the `requirement` that was applied.


### 400
Malformed data, unknown contractor, or no insurance requirement.


[Powered by Bump.sh](https://bump.sh)