Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

This article describes how to use EPR's Connect API to upload documents for a particular project.

Prerequisites

A project record has been created. See Creating a new Project


Step-by-step guide

Call this method to upload plan review documents (in PDF format) and supporting attachments (any file format) for a particular Project.

Method
Notes
  1. POST /documentUploadVersion
  • This method uploads the file and creates the data records in documents, documentPages, documentVersions and the documentPageVersions tables.
  • The document is then rendered.
  • If the incoming document is a new version of a previously submitted document, you must set the priordocumentVersion_vendor_id value equal to the vendor_id of the first submittal.
  • If your application will pass plan review assignments to EPR, set 'needsIntake' to False.
  • If your application will not pass plan review assignments to EPR, set 'needsIntake' to True. This will make the Project Intake tab visible so that an EPR user can complete intake and create assignments.

NOTE: Scout PDF inspector will be invoked automatically for each incoming plan review document. Files rejected by Scout cannot be uploaded to EPR. The customer must correct the issues noted before proceeding. 

GET/project/{project_id}/documents

Call this method to retrieve the data records(s) for your newly uploaded document. (The document ID value will be required if you intend to create plan review assignments.)

Next Steps

Creating Assignments




  • No labels