Issues, RFIs, and Punch API
These endpoints support day-to-day field coordination and closeout workflows. All routes are under/api/v1 and require authenticated member sessions.
Issues
Base routes:GET /projects/:projectId/issuesPOST /projects/:projectId/issuesPATCH /projects/:projectId/issues/:issueIdDELETE /projects/:projectId/issues/:issueId
RFIs
Base routes:GET /projects/:projectId/rfiPOST /projects/:projectId/rfiGET /projects/:projectId/rfi/:rfiIdPATCH /projects/:projectId/rfi/:rfiIdPOST /projects/:projectId/rfi/:rfiId/messagesPOST /projects/:projectId/rfi/:rfiId/attachments/presignPOST /projects/:projectId/rfi/:rfiId/attachments/complete
Punch lists
Base routes:GET /projects/:projectId/punchPOST /projects/:projectId/punchPATCH /projects/:projectId/punch/:punchIdDELETE /projects/:projectId/punch/:punchId
Field reports
GET /projects/:projectId/field-reportsPOST /projects/:projectId/field-reportsPATCH /projects/:projectId/field-reports/:reportIdDELETE /projects/:projectId/field-reports/:reportIdPOST /projects/:projectId/field-reports/send-email
Integration tips
- Sync IDs from your source system to PlanSync IDs in your own integration table
- Treat linked drawing/file version references as authoritative context
- Handle
402responses where plan-gated modules are not active