Operator Outcomes

Not in scope for trial — outcomes endpoint reference

POST /v1/outcomes

Send Outcomes

cURL

curl --request POST \
  --url https://{host}/v1/outcomes \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "outcomes": [
    {
      "placement_id": "example-4390001",
      "gall_id": "example_gallery",
      "post_no": 31899120,
      "tier": "main",
      "placed_at": "2026-09-29T02:40:00+09:00",
      "picked_by": {
        "type": "operator"
      },
      "score_at_placement": 0.62,
      "views_at_placement": 1875,
      "up_at_placement": 40,
      "down_at_placement": 3,
      "comment_at_placement": 21,
      "readings": [
        {
          "age_h": 1,
          "observed_at": "2026-09-29T03:40:00+09:00",
          "views": 9120,
          "up": 66,
          "down": 8,
          "comment_cnt": 30
        }
      ],
      "hidden_at": null,
      "deleted_at": null,
      "deleted_by": null
    }
  ]
}
'

200

{
  "received": 1,
  "created": 1,
  "updated": 0
}

Not in scope for trial. This outcomes endpoint is reference material for later integration. Daily operator outcomes may be shared separately by agreement; they are not required through this endpoint for the current trial.

Supporting outcome data

DCinside said that outcomes for operator-placed posts can flow daily during rehearsal. The model does not place posts at this stage. Outcomes are useful supporting data, but DCinside did not list their delivery as a rehearsal pass condition.

The endpoint and field mapping below are retained for later review, outside the current trial integration scope. The formal live-trial choice between sending events as they occur and hourly batches can be settled later.

Requested data

• Board counts at 1, 6, 24 and 48 hours after placement: views, up-votes, down-votes and comments.
• Hide times and deletion events, when available.
• Who picked the post: operator or model version.
• Score at placement, when available, together with the original post identity.

The 1/6/24/48-hour ages are measurement times, not upload frequencies. Daily rehearsal uploads can carry readings from several measurement times. Proposed placement-baseline fields support interpreting net board growth and need payload confirmation.

Updates and current implementation

placement_id identifies a placement. The current handler replaces the stored placement record on a repeated ID; it does not merge partial readings automatically. For current smoke tests, send the complete known snapshot for that placement. Agree snapshot-versus-incremental semantics before integration.

The current request protection is 5,000 records, not the 1,000 previously written in this document. It is an engineering limit, not an agreed business quota. Storage is process-local and must not be treated as durable outcome delivery.

The schema supports model-picked records for later publishing stages. Rehearsal operator outcomes use picked_by.type = operator; hypothetical model picks are logged separately on DCinside’s side and are not actual placements.

Authorizations

Authorization · string · header · required

Proposed API key sent as the whole Authorization header value. Long-lived credential scope, handoff and rotation need confirmation. Per-endpoint scopes are not currently enforced.

Headers

Content-Encoding · enum<string>

Optional compression. Set to gzip only for a gzip-compressed body; plain JSON is also supported.

Available options: gzip

Body

application/json

outcomes · object[] · required

One record per placement. Current 5,000-record protection is an engineering limit, not an agreed quota. Daily operator-placed outcomes support rehearsal.

Maximum array length: 5000

Show child attributes

Response

200

application/json

Stored.

received · integer · required

Records in the request.

Required range: x >= 0

Example:

1

created · integer · required

Records stored as new placements.

Required range: x >= 0

Example:

1

updated · integer · required

Records that matched an existing placement_id and updated it.

Required range: x >= 0

Example:

0