Example body
description: >- Original body. The current model does not read it. DCinside agreed to send the text once, and later model versions or the review sample may use it. Delivered files: `queue.body_html`. gallery_type: type: string enum: - main - minor - mini example: minor description: >- We look gallery type up in the gallery registry we hold. Send it for galleries added since that registry was built. A gallery missing from both is treated as unknown. category_id: type: integer minimum: 1 maximum: 47 example: 12 description: >- Gallery category. Same rule as `gallery_type`: we read it from the registry, and you send it for galleries added since. required: - gall_id - post_no - title - created_at - extracted_at - source - manual_flag - images_in_post description: >- A post that became a candidate. Sent once, in the first call after it enters the queue. EngagementRow: type: object properties: gall_id: type: string minLength: 1 description: Post key, together with `post_no`. example: example_gallery post_no: type: integer minimum: 1 description: >- Post number. Unique only within a gallery, so a post is always keyed by `gall_id` and `post_no` together. example: 31900001 observed_at: type: string format: date-time pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\+09:00$ description: >- When the counters were read from the gallery, to the minute, at or before `cycle_time`. The model takes the latest row at or before the cycle, and its growth features need that row within 10 minutes of the cycle. Delivered files: `engagement_ts.ts`. example: '2026-09-29T02:04:00+09:00' status: type: string enum: - ok - missing - nomap example: ok description: >- `ok` = read normally, `missing` = the post is gone, `nomap` = the gallery could not be mapped. A categorical input. A post whose latest status is `missing` or `nomap` is not scored. views: type: integer minimum: 0 description: >- Current view count. Inputs: the value, up-per-view, comments-per-view, and its rate and acceleration over 5, 15 and 30 minutes, which we compute from the series. example: 412 nullable: true up: type: integer minimum: 0 description: >- Recommendations, not the Send-to-Best counter. In v1 and v1.1 of the delivered files this column held the wrong counter, and v1.2 corrected it. example: 9 nullable: true down: type: integer minimum: 0 description: Down-votes. Feeds the down-vote share input. example: 1 nullable: true comment_cnt: type: integer minimum: 0 description: Comment count. example: 6 nullable: true rtb_vote: type: integer minimum: 0 description: The Send-to-Best vote counter, separate from `up`. example: 0 nullable: true required: - gall_id - post_no - observed_at - status - views - up - down - comment_cnt - rtb_vote description: Current counters of one pending post, as read from the gallery. CandidateScoreRow: type: object properties: gall_id: type: string minLength: 1 description: Post key, together with `post_no`. example: example_gallery post_no: type: integer minimum: 1 description: >- Post number. Unique only within a gallery, so a post is always keyed by `gall_id` and `post_no` together. example: 31900001 snapshot_at: type: string format: date-time pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\+09:00$ description: >- When the admin candidate-score table was read. The model uses the latest snapshot at or before the cycle, and how old it is is an input. Delivered files: `candidate_score_ts.snapshot_ts`. example: '2026-09-29T02:05:00+09:00' recommend_up_cnt: type: integer minimum: 0 description: >- Over-baseline recommendations, PC part. The model reads the sum of the PC, mobile and app parts, and that sum is missing if any one part is `null`. example: 3 nullable: true recommend_up_cnt_m: type: integer minimum: 0 description: >- Over-baseline recommendations, mobile part. The model reads the sum of the PC, mobile and app parts, and that sum is missing if any one part is `null`. example: 2 nullable: true recommend_up_cnt_a: type: integer minimum: 0 description: >- Over-baseline recommendations, app part. The model reads the sum of the PC, mobile and app parts, and that sum is missing if any one part is `null`. example: 1 nullable: true comment_cnt: type: integer minimum: 0 description: >- Over-baseline comments, PC part. The model reads the sum of the PC, mobile and app parts, and that sum is missing if any one part is `null`. example: 2 nullable: true comment_cnt_m: type: integer minimum: 0 description: >- Over-baseline comments, mobile part. The model reads the sum of the PC, mobile and app parts, and that sum is missing if any one part is `null`. example: 1 nullable: true comment_cnt_a: type: integer minimum: 0 description: >- Over-baseline comments, app part. The model reads the sum of the PC, mobile and app parts, and that sum is missing if any one part is `null`. example: 1 nullable: true hit_cnt: type: integer minimum: 0 description: >- Over-baseline views, PC part. The model reads the sum of the PC, mobile and app parts, and that sum is missing if any one part is `null`. example: 5 nullable: true hit_cnt_m: type: integer minimum: 0 description: >- Over-baseline views, mobile part. The model reads the sum of the PC, mobile and app parts, and that sum is missing if any one part is `null`. example: 4 nullable: true hit_cnt_a: type: integer minimum: 0 description: >- Over-baseline views, app part. The model reads the sum of the PC, mobile and app parts, and that sum is missing if any one part is `null`. example: 1 nullable: true dcbest_cnt: type: integer minimum: 0 description: >- Send-to-Best votes, PC part. The model reads the sum of the PC, mobile and app parts, and that sum is missing if any one part is `null`. example: 0 nullable: true dcbest_cnt_m: type: integer minimum: 0 description: >- Send-to-Best votes, mobile part. The model reads the sum of the PC, mobile and app parts, and that sum is missing if any one part is `null`. example: 0 nullable: true dcbest_cnt_a: type: integer minimum: 0 description: >- Send-to-Best votes, app part. The model reads the sum of the PC, mobile and app parts, and that sum is missing if any one part is `null`. example: 0 nullable: true memo_size: type: integer minimum: 0 description: >- Body size as the admin table counts it. A model input as delivered, so there is nothing to compute on DCinside's side. example: 1840 nullable: true upimg_cnt: type: integer minimum: 0 description: Uploaded image count from the same table. An input. example: 2 nullable: true upimg_height: type: integer minimum: 0 maximum: 32767 nullable: true example: 2410 description: >- Total pixel height of the uploaded images, capped at 32,767. An input. required: - gall_id - post_no - snapshot_at description: >- The admin candidate-score table's row for one pending post. The delivered table also has `is_extract`, `is_extract_g`, `category` and `regdate`, which the model does not read. Removal: type: object properties: gall_id: type: string minLength: 1 description: Post key, together with `post_no`. example: example_gallery post_no: type: integer minimum: 1 description: >- Post number. Unique only within a gallery, so a post is always keyed by `gall_id` and `post_no` together. example: 31900001 reason: type: string enum: - saved - hidden - deleted - aged_out example: hidden description: >- Why the post leaves the pending pool: `saved` (placed on a board), `hidden`, `deleted`, or `aged_out` (over 24 hours: DCinside applies a 24-hour age filter and sends a removal signal when a pending candidate crosses it). It stops being scored and stops appearing in responses. Delivered files: `queue.outcome`, `deletion`. tier: type: string enum: - main - light - night - app example: main description: Board tier. Required when `reason` is `saved`, otherwise omit. decided_at: type: string format: date-time pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\+09:00$ description: >- When the decision or deletion happened. Kept for reconciliation. Not a model input. Delivered files: `queue.decided_at`, `deletion.deleted_at`. example: '2026-09-29T02:01:10+09:00' reason_code: type: string example: quota_full description: >- Optional. The code the operator picked in DCinside's reason tool for a `saved` or `hidden` decision. The code list is still being agreed. Surf proposed `low_quality`, `stale`, `quota_full`, `duplicate`, `policy_violation` and `other` for hides. required: - gall_id - post_no - reason - decided_at description: A post leaving the pending pool. Counts: type: object properties: candidates: type: integer minimum: 0 example: 1 description: Rows received in `candidates`. engagement: type: integer minimum: 0 example: 2 description: Rows received in `engagement`. candidate_scores: type: integer minimum: 0 example: 1 description: Rows received in `candidate_scores`. removals: type: integer minimum: 0 example: 1 description: Rows received in `removals`. scored_now: type: integer minimum: 0 example: 1 description: Posts whose score was taken in this cycle. waiting: type: integer minimum: 0 example: 1 description: Results with status `waiting`. not_scored: type: integer minimum: 0 example: 0 description: Results with status `not_scored`. results: type: integer minimum: 0 example: 2 description: >- Rows in `results`: every pending post, including earlier scores repeated unchanged. required: - candidates - engagement - candidate_scores - removals - scored_now - waiting - not_scored - results description: Row counts for this cycle. ResultRow: type: object properties: gall_id: type: string minLength: 1 description: Post key, together with `post_no`. example: example_gallery post_no: type: integer minimum: 1 description: >- Post number. Unique only within a gallery, so a post is always keyed by `gall_id` and `post_no` together. example: 31900001 status: type: string enum: - scored - waiting - not_scored example: scored description: >- `scored` = the post has a score. `waiting` = it is still inside its 15-minute wait. `not_scored` = it cannot be scored, see `reason`. score: type: number nullable: true example: 0.62 description: >- The publish score: `w_v·P(views) + w_c·P(comments) + w_u·P(up) − w_d·downvote_share`, with the weights in force. `null` unless `status` is `scored`. p_views: type: number minimum: 0 maximum: 1 nullable: true example: 0.62 description: >- Chance that the post lands in the top quarter for views within its tier, day and time block. `null` unless scored. p_comments: type: number minimum: 0 maximum: 1 nullable: true example: 0.41 description: Same, for comments. `null` unless scored. p_up: type: number minimum: 0 maximum: 1 nullable: true example: 0.37 description: Same, for up-votes. `null` unless scored. downvote_share: type: number minimum: 0 maximum: 1 nullable: true example: 0.08 description: Predicted down-vote share. `null` unless scored. scored_at_cycle: type: string format: date-time pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:[0-5][05]:00\+09:00$ description: >- The cycle at which the score was taken. Present when `status` is `scored`. A score is taken once and repeated unchanged in later cycles until the post is removed. example: '2026-09-29T02:05:00+09:00' due_cycle: type: string format: date-time pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:[0-5][05]:00\+09:00$ description: >- The cycle at which a waiting post will be scored. Present when `status` is `waiting`. example: '2026-09-29T02:20:00+09:00' reason: type: string enum: - missing_title - missing_clock - post_unavailable - unknown_post example: missing_title description: >- Present when `status` is `not_scored`. `missing_title`: the title is empty. `missing_clock`: `created_at` or `extracted_at` is missing. `post_unavailable`: the latest engagement status is `missing` or `nomap`. `unknown_post`: the post appears in `engagement` without a candidate record. required: - gall_id - post_no - status description: The state of one pending post. Error: type: object properties: error: $ref: '#/components/schemas/ErrorBody' required: - error ErrorBody: type: object properties: code: type: string example: bad_request description: Machine-readable code. See Errors. message: type: string example: 2 fields failed validation description: Human-readable summary. fields: type: array items: $ref: '#/components/schemas/ErrorField' description: Every failing field, when the error is about the body. required: - code - message ErrorField: type: object properties: path: type: string example: candidates[0].created_at description: Path of the failing field. problem: type: string example: missing +09:00 offset description: What is wrong with it. required: - path - problem responses: BadRequest: description: >- The body is not valid JSON, or a field fails the schema. The error lists every failing path. Nothing is stored. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: bad_request message: 2 fields failed validation fields: - path: candidates[0].created_at problem: missing +09:00 offset - path: engagement[3].views problem: must be a non-negative integer or null Unauthorized: description: The API key is missing or unknown. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: unauthorized message: API key missing or unknown Forbidden: description: The key has no scope for this call. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: forbidden message: this key cannot call PUT /v1/weights Conflict: description: The id was already used with a different body. The first body stays. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: cycle_conflict message: cycle 20260929T0205 was already received with a different body TooLarge: description: Over the size or row limits. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: too_large message: candidates has 214 rows, the limit is 200 Unprocessable: description: >- The body is valid JSON and matches the schema, but the values are not acceptable. Nothing is stored. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: unprocessable message: cycle_time is not on the 5-minute grid fields: - path: cycle_time problem: must be a multiple of 5 minutes RateLimited: description: >- Too many calls. Wait for `Retry-After` seconds, then repeat the same call. headers: Retry-After: description: Seconds to wait. schema: type: integer example: 10 content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: rate_limited message: too many calls, retry in 10 s ServerError: description: Our failure. No scores. DCinside skips the cycle and our alert fires. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: server_error message: internal error securitySchemes: ApiKey: type: apiKey name: Authorization in: header description: >- The API key issued for the environment, sent as the whole header value. Two keys are valid during a rotation. ````