SHIELDEX File 6.0 - Time Zone Detail Code Statistics API Specification (GET /statistics/detail-code)

# SHIELDEX File 6.0 - Time Zone Detail Code Statistics API Specification (GET /statistics/detail-code)

Query Period(from ~ to) The demining results that occurred during1 hour unitGroup by, for each time zonedetailCodeStar Count(count0 ~ count3, count-1returning as a JSON ArrayCustomer Integration Statistics APISpecification.

item	value
Document Version	6.2026.0813.01

Related Documents	role
Declassification Result Response Specification (detailCode)	`detailCode`Definition · SSOT of Calculation Rules
Decontamination Logarithm Table	`logReason`/ Result`code`Definition of SSOT

GuideThis API'sdetailCodeThe calculation rules are in the above result response specification (§6) andcompletely identicalThis document is thatdetailCodeDefines only the statistical endpoint that provides aggregated data by time zone.

1. Request Specification (Request)

item	value
Method	`GET`
Path	`/statistics/detail-code`
Actual call URL	`http://{서버IP}:8060/statistics/detail-code`(port 8060)
Authentication	No Token (Server-to-Server Integration)
Content-Type	None (GET, query string)

Customer system isport 8060Calls with. There is no Context-Path.

1.1 Request Parameters

name	type	Essential	format	Explanation
`from`	String	Essential	`yyyyMMddHHmmss`(14 characters)	Start Date and Time (this timeincluded)
`to`	String	Essential	`yyyyMMddHHmmss`(14 characters)	End of Inquiry Date and Time (This timeincluded)

item	rules
format	`from` / `to`is14-digit number
Error	Not a valid date and time or`from > to`back`400`
Query Criteria	DecontaminationRequest Time

1.2 Request Example

GET /statistics/detail-code?from=20260727090000&to=20260727105959

item	value
meaning	2026-07-27 09:00:00 ~ 10:59:59Statistics of the period

2. Response Specification

Data within the query period1 hour unit(yyyyMMddHH0000**)**Group by and for each time zonedetailCodeReturns the occurrence count of __PH_0__.

item	value
Response Format	`JSON Array`
HTTP Status	`200 OK`

2.1 Field Description

KEY	TYPE	Explanation
`date`	String	Standard time for the corresponding time zone (`yyyyMMddHH0000`)
`count0`	Number	`detailCode = 0`(No Hazard Factors/Safe) Count
`count1`	Number	`detailCode = 1`(Risk factors present) Number of cases
`count2`	Number	`detailCode = 2`(Vaccine Detection) Count
`count3`	Number	`detailCode = 3`(Not Supported/Exceptions·Blocked) Count
`count-1`	Number	`detailCode = -1`(Error) Count

item	rules
Field Name	`count` + `detailCode`value (`0`→`count0` … `3`→`count3`, `-1`→`count-1`)
Error Aggregation	`detailCode = -1` → `count-1`. `count4`not used
JSON Access	`count-1`is`obj["count-1"]`(point access`obj.count-1`not possible)
No code	If not available at that time`0`
Empty time slots	Included in the response without a request, all count is`0`
Sorting	`date`ascending

2.2 Response Example

[
  {
    "date": "20260727090000",
    "count0": 100,
    "count1": 1,
    "count2": 2,
    "count3": 0,
    "count-1": 0
  },
  {
    "date": "20260727100000",
    "count0": 100,
    "count1": 2,
    "count2": 5,
    "count3": 0,
    "count-1": 1
  }
]

Time Zone	meaning
`20260727090000`(09:00)	Safety 100 cases, 1 case with risk factors, 2 cases of vaccine detection
`20260727100000`(10 o'clock)	Safety 100 cases, Risk factors present 2 cases, Vaccine detection 5 cases,Error 1 case (`count-1`)

3. `detailCode` → `count`Mapping

detailCodeThe meaning and calculation rules areDecontamination Result Response Specification §6Wowsameand, this API has its value as followscountAggregate by bucket.

detailCode	meaning	Aggregation Bucket
`0`	No hazards (Safety)	`count0`
`1`	Risk factors present (suspicion·warning·danger·tampering)	`count1`
`2`	Vaccine (Virus) Detection	`count2`
`3`	Unsupported Files (Exceptions·Blocked)	`count3`
`-1`	Error	`count-1`

item	rules
Key Naming	`count` + `detailCode` (`-1` → `count-1`)
Not in use	`count4`(code value is different). Not included in the response

3.1 Summary of Output Rules (Same as Result Specification)

First, apply the matching rules.

Priority	condition	result
1	Explicit Log Reason	BelowLogin Reason Table
2	Reconstruction Complete (`200000`, `200001`)	belowRisk Level Table
3	Error	`detailCode = -1` → `count-1`
4	Others	`detailCode = 0` → `count0`

logReason → detailCode

Log Reason	detailCode	Aggregation
`200004`	`0`	`count0`
`200005`, `200006`, `200007`, `220355`, `230133`, `240355`	`1`	`count1`
`990003`	`2`	`count2`
`210211`, `230213`, `240215`	`3`	`count3`

Risk Level upon Completion of Reconstruction → detailCode (200000, 200001)

Risk Level (`threatLevelCode`)	meaning	detailCode	Aggregation
`1`	safety	`0`	`count0`
`2`, `3`, `4`, `6`	Doubt · Warning · Danger · Tampering	`1`	`count1`
`5`	serious	`2`	`count2`

4. Aggregation Logic

item	rules
Time Zone Grouping	Decontamination request time`yyyyMMddHH0000`Cutting with. Example)`09:00:00 ~ 09:59:59` → `20260727090000`
Aggregation Target	Only completed results (`code ∈ {0, 1, 2}`). In Progress(`code = 3`except
Empty time slots	Customer feedback`from` / `to`Use it as is. The section'sAll time zonesInclude in the response. If there is no request, count is all.`0`. Does not cut off the past, present, and future
Sorting	`date`(Timezone) Ascending
Aggregation Scope	within the inquiry periodOverall Demilitarization Results

5. Error Response

HTTP	condition	Body example
`400 Bad Request`	`from`/`to`Missing·Format error (not 14 digits·incorrect date and time)·`from > to`	`{ "code": 400, "message": "'from' is required (yyyyMMddHHmmss)" }`
`502 Bad Gateway`	Server internal processing failure	`{ "code": 502, "message": "statistics call failed: ..." }`

{
  "code": 400,
  "message": "'from' must be 14 digits (yyyyMMddHHmmss): 202607270900"
}

6. Call Usage Example and Expected Results

Actual deployment server (e.g:10.10.12.226, port 8060·http) is a complete example of querying the period from 2026-07-27 09:00:00 to 10:59:59.

6.1 Address (URL) Call Example

http://10.10.12.226:8060/statistics/detail-code?from=20260727090000&to=20260727105959

item	value
host	`10.10.12.226`Replace with the actual server
port	8060
firewall	Customer System → Server8060/tcp

6.2 curl call example

curl -G "http://10.10.12.226:8060/statistics/detail-code" \
     --data-urlencode "from=20260727090000" \
     --data-urlencode "to=20260727105959"

6.3 Expected Result Example (200 OK)

This is an example response to the above request.09시big and10시Big Two Time ZonedetailCodeA star count will be returned.

[
  {
    "date": "20260727090000",
    "count0": 100,
    "count1": 1,
    "count2": 2,
    "count3": 0,
    "count-1": 0
  },
  {
    "date": "20260727100000",
    "count0": 100,
    "count1": 2,
    "count2": 5,
    "count3": 0,
    "count-1": 1
  }
]

Time Zone	count0	count1	count2	count3	count-1	meaning
`20260727090000` (09:00:00~09:59:59)	100	1	2	0	0	Safety 100, Risk Factors Present 1, Vaccine Detection 2
`20260727100000` (10:00:00~10:59:59)	100	2	5	0	1	Safety 100, Risk factors present 2, Vaccine detection 5,Error 1

6.4 Parameter Error Example (400 Bad Request)

fromIf sent with less than 14 characters:

http://10.10.12.226:8060/statistics/detail-code?from=202607270900&to=20260727105959

{
  "code": 400,
  "message": "'from' must be 14 digits (yyyyMMddHHmmss): 202607270900"
}

7. Empty Time Slots · No Data Example

Even if there are no demining results completed within the inquiry period,Does not return an empty array. from / toAll time zones that belong to0Filling with the matter.

For example)from=20260727090000, to=20260727115959If there are no requests at 09:00 and 11:00 and data is only available at 10:00:

Time Zone	data	Response
09:00	None	all count`0`
10 o'clock	exists	Actual Count
11 o'clock	None	all count`0`

[
  {
    "date": "20260727090000",
    "count0": 0,
    "count1": 0,
    "count2": 0,
    "count3": 0,
    "count-1": 0
  },
  {
    "date": "20260727100000",
    "count0": 100,
    "count1": 2,
    "count2": 5,
    "count3": 0,
    "count-1": 1
  },
  {
    "date": "20260727110000",
    "count0": 0,
    "count1": 0,
    "count2": 0,
    "count3": 0,
    "count-1": 0
  }
]

Even if there is no data for the entire period, the same number of time zones will be used.count0~`count3·count-1` This returns an object that is 0.

8. Call Path

http://{서버IP}:8060/statistics/detail-code?from=yyyyMMddHHmmss&to=yyyyMMddHHmmss

item	value
port	8060
Context-Path	None

Change History

date	Document Version	Content
2026-08-13	6.2026.0813.01	No empty time slots included. Error(`detailCode = -1`) is`count-1`to aggregate (`count4`Unused). The response interval is the same as the request from / to. The calling URL is`:8060/statistics/detail-code`.
2026-08-06	6.2026.0806.05	Initial Release —`GET /statistics/detail-code`Time Zone Detail Code Statistics API

1. Request Specification (Request)​

1.1 Request Parameters​

1.2 Request Example​

2. Response Specification​

2.1 Field Description​

2.2 Response Example​

3. detailCode → countMapping​

3.1 Summary of Output Rules (Same as Result Specification)​

4. Aggregation Logic​

5. Error Response​

6. Call Usage Example and Expected Results​

6.1 Address (URL) Call Example​

6.2 curl call example​

6.3 Expected Result Example (200 OK)​

6.4 Parameter Error Example (400 Bad Request)​

7. Empty Time Slots · No Data Example​

8. Call Path​

Change History​