The 14(c) system will become a modern, digital-first service. Applicants will be provided an intuitive online experience, guiding them through the information needed to complete their application correctly.
Add new parameters for Date Ranges to the two API Methods as below (similar to ECF. See #943 ):
intervalInMinutes (Number type; Calculate the END dateTime based on the value; Default value = 5)
prevGeUtcDateTime (String type; Date Time value)
prevIntervalInMinutes (Number type: Calculate the END date time value for previous Date range)
API Method 1:
../api/integration/ids
Returns list of application ids.
Post body : “listType”: “application”; “version”: “1”, geUtcDateTime.
API Method 2:
../api/integration/list
Returns the JSON for the application.
Post body : “listType”: “application”; “version”: “1” ; includeMetadata:false (default is false when this param is not passed)
[ ] TODO: Serialization issue: API should return JSON without any serialization issues.
[ ] Return nested JSON,
[ ] One JSON schema for all Applications (use online tool)
[ ] Blank Array/Null values in JSON when not applicable.
API Method Specs
[ ] Relative routing path must include (after /api/):
[ ] GetApplicationIds Web API Method
Input: timestamp; Output: Returns all submitted application Ids >= timestamp
Route: /api/integration/14c/applications
Method: POST
[ ] GetApplication Web API Method
Input: application-id; Output: Returns JSON application data
Updated
Add new parameters for Date Ranges to the two API Methods as below (similar to ECF. See #943 ):
API Method 1: ../api/integration/ids Returns list of application ids. Post body : “listType”: “application”; “version”: “1”, geUtcDateTime.
API Method 2: ../api/integration/list Returns the JSON for the application. Post body : “listType”: “application”; “version”: “1” ; includeMetadata:false (default is false when this param is not passed)
API Method Specs