PORTERS Connect API 9.3.0 includes the following feature enhancement.
The "Time" field type added in PORTERS 9.3.0 can now be handled by Read, Write, and Search operations of the Resource API.
No HTTP Header (X-P-ConnectAPI-Version) specification is required to use Time-type fields.
What is a Time-type Field?
A field that holds only a time value (hours and minutes). On the PORTERS screen, values can be entered in the range 00:00–47:59.
Its Field Type is "12 (DateTime)", the same as the DateTime field type.
In the database, values are stored as a date-time based on the reference date 1970/01/01. (24:00–47:59 is stored as 1970/01/02.)
【Example of values on the PORTERS screen vs. values in the database】
PORTERS Screen |
Value in Database |
| 09:00 | 1970/01/01 09:00 |
| 26:00 | 1970/01/02 02:00 |
Read
- Values of Time-type fields are output in the same format as DateTime fields, [yyyy/mm/dd HH:MM:SS].
Example: <Job.U_XXX>1970/01/01 09:00:00</Job.U_XXX> - Values are not output in HH:MM-only format.
If you need to display only the hours and minutes, please process the response on your side. - Unlike DateTime fields, no time zone conversion is performed.
Write (Create / Update)
- Specify the value of a Time-type field in the following format, including the reference date:
[1970/01/01 HH:MM:SS] (00:00–23:59)
[1970/01/02 HH:MM:SS] (equivalent to 24:00–47:59. Example: 26:00 → 1970/01/02 02:00:00) - If a date other than the reference dates (1970/01/01 or 1970/01/02) is specified, a validation error occurs and Code 103 is returned (HTTP status is 200).
Search (Read condition)
- When specifying a Time-type field in a condition, use the format that includes the reference date.
Example (15:00 or later and 26:00 or earlier): condition=Job.U_XXX:ge=1970/01/01 15:00:00,Job.U_XXX:le=1970/01/02 02:00:00 (URL encoding is required in practice) - If an invalid format is specified, a validation error occurs, Code 100 is returned, and the search is not executed (HTTP status is 200).
- The order (sort order) can be specified using the same specifications as for DateTime fields.
Distinguishing from DateTime Fields
In Field - Read, Time-type fields are retrieved with the same Field Type = 12 as DateTime fields.
Currently, there is no way to determine from the API response whether a given field is a Time-type field.
When handling Time-type fields via the API, please check the field's type in the PORTERS customization screen (Fields & Details) to confirm whether it is a Time-type field, and handle it individually by specifying the field's alias.
Impact on Existing API Integrations
In Field - Read (/v1/field), Time-type fields are retrieved with the same Field Type = 12 as DateTime fields.
Therefore, if a PORTERS administrator adds a Time-type field to a resource, and an existing integration program treats it the same as a DateTime field and writes an arbitrary date-time value (e.g., 2026/07/09 09:00:00), a Code 103 error will occur.
When writing a value to a Time-type field, please use the specification format that accounts for the reference date (e.g., 1970/01/01 09:00:00).
Note that it is not possible to programmatically determine whether a field is a Time-type field via the API. Therefore, please check with your PORTERS administrator to confirm which Time-type fields exist in the partitions targeted by your integration program.