Bulk create/update applicants (upsert) / 申込者一括作成/更新 (upsert)

Creates or updates applicants in bulk.
申込者を一括作成または更新する。

Determination logic / 判定ロジック:

If a training_id + member_id pair already exists, it is updated; otherwise, it is created
training_id + member_id ペアが既存なら更新、なければ作成

Processing differs based on the training's application_format (FCFS vs LOTTERY)
training の application_format が FCFS/LOTTERY で処理が異なる

On FCFS creation, capacity and waitlist controls are triggered
FCFS 作成時は定員・キャンセル待ち制御が発動する

Validation / バリデーション:

Maximum 504 records per request / 1リクエスト最大 504 件

Duplicate training_id + member_id pairs are not allowed / training_id + member_id ペアの重複不可

For TEAM applications, team_id and applied_by (team leader) are required / TEAM 申込時は team_id, applied_by (チームリーダー) が必須

For TEAM payments, payment_type=TEAM and team_priority (positive integer, unique within team) are required /

TEAM 支払い時は payment_type=TEAM, team_priority (正の整数、チーム内ユニーク) が必須

If an application form template is configured, form data validation is also performed /

申込フォームテンプレートが設定されている場合はフォームデータのバリデーションも実施

Success response / 成功レスポンス: "OK" (HTTP 200)

Partial failure / 部分失敗: Rows with validation errors are skipped, but other rows are still processed (abort_on_error is always false via API)
バリデーションエラーがある行があっても他の行は処理される (abort_on_error は API 経由では常に false)

curl --location --request PUT '/trainings/applicants' \ --header 'api-key: <api-key>' \ --header 'Content-Type: application/json' \ --data '{ "applications": [ { "training_id": 0, "member_id": 0, "type": "INDIVIDUAL", "id": 0, "team_id": "string", "applied_by": 0, "payment_type": "INDIVIDUAL", "team_priority": 0, "status": "APPLIED", "application_form_response_data": {}, "application_form_response_data_manager": {} } ] }'

Bulk create/update applicants (upsert) / 申込者一括作成/更新 (upsert)

Request

Responses