Listing Published Form Versions
Each entry of the version listing will contain some of the same duplicate keys with basic information about the Form: xmlFormId and createdAt, for example. This is done to match the data you'd receive if you'd requested each version separately.
This endpoint supports retrieving extended metadata; provide a header X-Extended-Metadata: true to additionally retrieve the Actor that each version was publishedBy.
Path parameters
The numeric ID of the Project
The xmlFormId of the Form being referenced.
Response
Ok
Example response
[
{
"projectId": 1,
"xmlFormId": "simple",
"name": "Simple",
"version": "2.1",
"enketoId": "abcdef",
"hash": "51a93eab3a1974dbffc4c7913fa5a16a",
"keyId": 3,
"publishedAt": "2018-01-21T00:04:11.153Z",
"createdAt": "2018-01-19T23:58:03.395Z",
"updatedAt": "2018-03-21T12:45:02.312Z"
}
]Changes
Changed in 4 of the 54 revisions of this API.15
- ○
added the optional property
items/allOf[subschema #2]/publishNotesto the response with the200statusresponse-optional-property-added
- ○
- ○
api operation id
Listing Published Form Versionsremoved and replaced withlistPublishedFormVersionsapi-operation-id-removed
- ○
- ○
removed the non-success response with the status
403response-non-success-status-removed
- ○
- ●
removed the optional property
items/allOf[subschema #2]/publishNotesfrom the response with the200statusresponse-optional-property-removed
- ○
api operation id
listPublishedFormVersionsremoved and replaced withListing Published Form Versionsapi-operation-id-removed
- ○
added the non-success response with the status
403response-non-success-status-added
This revision also has 11 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ●