2 Document Meta Data Request

post

/api/v1/document-meta

Organizations in the owner seat of a project are able to export documents via this API. This API provides the entire list of available documents, depending on the parameters specified by the user. These documents can extend over multiple projects. Documents available to the Owner:
  • GC documents - all documents signed on TPM, including invoice attachments, are available when the invoice is fully approved.
  • Subcontractor documents - all documents signed on TPM, including invoice attachments, are available when the GC invoice is fully approved and Open Book is enabled.
This API can support the export of different document types. These document types can be specified in the request sent to the API. The following are examples of document types to be exported, if selected:
  • Invoice
  • Sworn Statement
  • Lien Waiver
  • Conditional Lien Waiver
A successful request to this API will provide a listing of available documents for export. To export these records, individually, the user must use the Document-file API. If the user would like to export all available documents in a consolidated export, then the Export Documents API may offer a better option.

Request

Header Parameters
Supported Media Types
Request Body - application/json ()
  • application/json
Root Schema : schema
Type: object
Show Source
  • Allow to specify the from date in the date range to pull documents based on draw end date. If documentToDate is specified than this field cannot be null or empty. Date needs to be formatted as YYYY-MM-DD.
    Example: 2022-09-01
  • Allow to specify the to date in the date range, to pull documents based on the draw end dates. If documentFromDate is specificed, than this field cannot be null or empty. Date needs to be formated as YYYY-MM-DD.
    Example: 2023-03-01
  • If not provided, provides all types. Types include: invoice, swornstatement, invoicecover, condlw, uncondlw, uploadeduncondlw, uploadedcondlw, masiapproval, coattach, icattach, workinvoice, paymentschedule.
    Example:
  • Defaults to false. If set to true, the user must provide, at least, projectNumber as a field. If the user does not, the API returns with an error.
    Example: true
  • If set to true, will allow for the inclusion of draw documents prior to being approved by the owner.
    Example: true
  • If submitted must be provided in conjunction with vendor id and project number.
    Example:
  • TPM project number.
    Example: AT100
  • Must be provided if using the invoice number and project number fields.
    Example: brch002
Examples

Back to Top

Response

Supported Media Types

200 Response

Body ()
Root Schema : schema
Type: object
Show Source
Examples

Default Response

Links to working URLs
Back to Top