Skip to main content
GET

​
Overview

The Get Cycle Scores API returns the response that POST /v1/cycles produced for a cycle, byte for byte. It does not score anything and never changes what was stored, so it is safe to call as often as needed.
Use it when the cycle call timed out or the response was lost. Repeating POST /v1/cycles with the same cycle_id and the same body returns the same stored response, so either call works. This one needs no body.

​
When to use it

After a timeout

The scoring may have finished after DCinside stopped waiting. The stored result is here.

If scoring moves to polling

If synchronous scoring proves too slow, the cycle call replies 202 and the result is polled from this endpoint.
DCinside skips a cycle whose response does not arrive in time or does not match the cycle. Reading it later from here is for the record and for reconciliation, not for publishing late.

​
Request Attributes

​
string
required
The cycle id sent in the original call, YYYYMMDDTHHMM in KST, for example 20260929T0205. A cycle we never received returns 404 not_found.

​
Response Attributes

The body is the same CycleResponse object as in Score a Cycle: the envelope with counts and versions, and one row in results for every candidate that was pending in that cycle.

Authorizations

​
Authorization
string
header
required

The API key issued for the environment, sent as the whole header value. Two keys are valid during a rotation.

Path Parameters

​
cycle_id
string
required

The cycle id sent in the original call.

Pattern: ^\d{8}T\d{4}$
Example:

"20260929T0205"

Response

The response stored for this cycle.

​
cycle_id
string
required

Echoed from the request.

Pattern: ^\d{8}T\d{4}$
Example:

"20260929T0205"

​
cycle_time
string<date-time>
required

Echoed from the request.

Pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:[0-5][05]:00\+09:00$
Example:

"2026-09-29T02:05:00+09:00"

​
received_at
string<date-time>
required

Our clock when the call arrived.

Pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\+09:00$
Example:

"2026-09-29T02:05:03+09:00"

​
scored_at
string<date-time>
required

Our clock when scoring finished. The gap from received_at is the scoring time.

Pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\+09:00$
Example:

"2026-09-29T02:05:09+09:00"

​
model_version
string
required

The model that produced the scores. Every score can be traced to it and to weights_version.

Example:

"m0924-1"

​
weights_version
string
required

The publish-score weights in force for this cycle.

Example:

"w-1"

​
counts
object
required

Row counts for this cycle.

​
missing_feature_share
number
required

Share of the model's 62 tabular inputs that were missing across the posts scored in this cycle. A jump means bad data upstream.

Required range: 0 <= x <= 1
Example:

0.11

​
warnings
string[]
required

Extra fields we ignored, and anything else worth a look. Empty when clean.

Example:
​
results
object[]
required

One row per pending candidate. Scores given earlier are repeated unchanged, so DCinside keeps no score memory of its own. Removed posts are not returned.