Retrieve form submissions with flexible identification options:
Form Identification (choose one):
formId: Direct form ID (e.g., “form-abc123”)formMetadataKey + formMetadataValue: Lookup by metadata (e.g., “erpFormId” = “form123”)Optional Site Filtering:
siteId: Filter by specific site IDsiteMetadataKey + siteMetadataValue: Filter by site metadatayear: Filter by specific yearYou can identify forms using either internal IDs or custom metadata key-value pairs, making it easy to integrate with external systems.
Response shape notes:
values grouped by (elementId, periodUnit).value becomes an array. Each array item includes:
recordedAt (for TIMESTAMP entries),formElementSubmissionId, status, and docs (supporting documents) for that specific row.value is the scalar value.Example response (trimmed):
[
{
"id": "fs-1",
"year": 2024,
"values": [
{ "elementId": "el-monthly", "periodUnit": 3, "value": 120.5, "status": "APPROVED" },
{ "elementId": "el-ts", "periodUnit": 3, "value": [
{ "value": 10, "recordedAt": "2024-03-05T10:30:00Z", "formElementSubmissionId": "fes-1", "status": "COMPLETED", "docs": [] },
{ "value": 15, "recordedAt": "2024-03-12T08:00:00Z", "formElementSubmissionId": "fes-2", "status": "APPROVED", "docs": [] }
]
}
]
}
]
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.