OpenGov Files API
Files in OpenGov Permitting & Licensing are managed in a two-step process: 1. **File Upload** - First, create a file entry to receive a pre-signed Azure Blob Storage URL - Use this URL to upload your file directly to Azure Blob Storage - The file is now stored but not yet associated with any entity 2. **File Association** - Associate the uploaded file with an entity (currently only Record Attachments) - The file is cloned when associated, allowing the same file to be reused across different entities - Each association creates a new file object with its own lifecycle This design allows for efficient file reuse while maintaining independent file management for each entity.
Documentation
Documentation
https://developer.opengov.com/docs/plc/overview
APIReference
https://developer.opengov.com/catalog/plc-api
APIReference
https://developer.opengov.com/catalog/bnp-api
APIReference
https://developer.opengov.com/catalog/pro-api
APIReference
https://developer.opengov.com/catalog/pro-purchase-order-api
APIReference
https://developer.opengov.com/catalog/pro-receipt-api
Documentation
https://developer.opengov.com/docs/vm/overview
APIReference
https://developer.opengov.com/catalog/vm-api
Documentation
https://developer.opengov.com/docs/eam/overview
APIReference
https://developer.opengov.com/catalog/eam-api
APIReference
https://developer.opengov.com/catalog/opendata-public-api
Specifications
Other Resources
ChangeLog
https://developer.opengov.com/docs/plc/changelog
Webhooks
https://raw.githubusercontent.com/api-evangelist/opengov/refs/heads/main/asyncapi/opengov-permitting-licensing-webhooks.yml
Idempotency
https://raw.githubusercontent.com/api-evangelist/opengov/refs/heads/main/conventions/opengov-conventions.yml
ChangeLog
https://developer.opengov.com/docs/vm/changelog
ChangeLog
https://developer.opengov.com/docs/eam/changes-log