Skip to content

πŸ”Œ API Introduction

This page has a quick introduction to our API reference specifications, with some details on the reports states and outcomes and the person/folder’s status.

Authentication requires only the X-Api-Key header set up to your API key.

Every report executed goes through a series of states until completion. Possible state values are PENDING, PENDING_MANUAL_REVIEW (if enabled), COMPLETED, ERROR and INCOMPLETE. Each state might have an outcome PASSED, FAILED or INFO.

For a deeper insight on how the reports work, you can check the Reports States Workflow diagram in our guides.

StateDescription
PENDINGThe first state of all reports when a person is created, updated or reports update is triggered. It means that the checks are being performed.
PENDING_MANUAL_REVIEWReport is queued for Manual Review. It happens when automated checks have been performed, but the report needed a Manual Review (usually when there is a FAILED outcome from the automated checks).
COMPLETEDThis state represents the report has completed all checks and should include a final outcome (PASSED or FAILED) or only the data requested (for reports with outcome BODY - no decision making).
INCOMPLETEIt means that the report was not able to complete for some reason: input provided was not valid or not found in the sources/databases, the data found was not enough to reach a final outcome under the rules provided.
ERRORThis state means something went wrong with the check: sources may have been down for too much time or an internal error at Emptor’s API has happened.
OutcomeDescription
PASSEDThis outcome means that, under the rules provided by the customer (previously agreed upon or provided within the Create a Person request), no data was found to result in a FAILED outcome (e.g. no criminal records found).
FAILEDIt means that, under the rules provided by the customer (previously agreed upon or provided within the Create a Person request), enough information was found to result in a FAILED outcome (e.g. criminal records found).
INFOThis outcome means that the report was requested as informational only and will be limited to return a set of data, not a decision making outcome like PASSED or FAILED.

The folder is, basically, the aggregate of all the reports enabled for a given Person. Unlike the reports, which have state and outcome, the folder only has a status which includes values both from the reports states and outcomes as described below.

The folder status is the same as the Person status, which you can retrieve by making a request to the Get a Person Status endpoint.

For a deeper insight on how the Folders work, you can check the Folders Status Workflow chart in the Guides.

StatusDescription
PENDINGWhen all reports are in state PENDING.
PENDING_MANUAL_REVIEWWhen there are reports in PENDING_MANUAL_REVIEW state.
PASSEDWhen all reports are in state COMPLETED and at none of them resulted in a FAILED outcome.
FAILEDWhen all reports are in state COMPLETED and at least one of them resulted in a FAILED outcome.
INCOMPLETEWhen there are no reports in ERROR state, but at least one of them is in state INCOMPLETE.
ERRORWhen at least one report is in ERROR state or if there was a problem computing the status.

For every report executed, it passes through a series of states until completion. Those states are PENDING, PENDING_MANUAL_REVIEW (if enabled), COMPLETED, ERROR and INCOMPLETE. Each state might have an outcome PASSED, FAILED or INFO. You can see the transition between states in the following diagram.

Reports Flow

After creating a person, updating a person, or triggering reports update, the folder status logic can be determined with the following diagram.

Folder Status

If you have any questions, you can still contact us at support@emptor.io πŸ“§.