Send a message to the AI athlete assistant

curl --request POST \
  --url http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "message": "Which 3 am I waiting on payment for?",
  "scope": "deal",
  "deal_type": "job",
  "job_id": 42,
  "conversation_id": "550e8400-e29b-41d4-a716-446655440000",
  "session_id": "550e8400-e29b-41d4-a716-446655440000",
  "client_message_id": "8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18",
  "qa_scenario_run_id": "44444444-4444-4444-8444-444444444444",
  "portfolio_cursor": "<string>"
}
'

import requests

url = "http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat"

payload = {
    "message": "Which 3 am I waiting on payment for?",
    "scope": "deal",
    "deal_type": "job",
    "job_id": 42,
    "conversation_id": "550e8400-e29b-41d4-a716-446655440000",
    "session_id": "550e8400-e29b-41d4-a716-446655440000",
    "client_message_id": "8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18",
    "qa_scenario_run_id": "44444444-4444-4444-8444-444444444444",
    "portfolio_cursor": "<string>"
}
headers = {
    "Authorization": "Bearer <token>",
    "Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.text)

const options = {
  method: 'POST',
  headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
  body: JSON.stringify({
    message: 'Which 3 am I waiting on payment for?',
    scope: 'deal',
    deal_type: 'job',
    job_id: 42,
    conversation_id: '550e8400-e29b-41d4-a716-446655440000',
    session_id: '550e8400-e29b-41d4-a716-446655440000',
    client_message_id: '8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18',
    qa_scenario_run_id: '44444444-4444-4444-8444-444444444444',
    portfolio_cursor: '<string>'
  })
};

fetch('http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_POSTFIELDS => json_encode([
    'message' => 'Which 3 am I waiting on payment for?',
    'scope' => 'deal',
    'deal_type' => 'job',
    'job_id' => 42,
    'conversation_id' => '550e8400-e29b-41d4-a716-446655440000',
    'session_id' => '550e8400-e29b-41d4-a716-446655440000',
    'client_message_id' => '8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18',
    'qa_scenario_run_id' => '44444444-4444-4444-8444-444444444444',
    'portfolio_cursor' => '<string>'
  ]),
  CURLOPT_HTTPHEADER => [
    "Authorization: Bearer <token>",
    "Content-Type: application/json"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"strings"
	"net/http"
	"io"
)

func main() {

	url := "http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat"

	payload := strings.NewReader("{\n  \"message\": \"Which 3 am I waiting on payment for?\",\n  \"scope\": \"deal\",\n  \"deal_type\": \"job\",\n  \"job_id\": 42,\n  \"conversation_id\": \"550e8400-e29b-41d4-a716-446655440000\",\n  \"session_id\": \"550e8400-e29b-41d4-a716-446655440000\",\n  \"client_message_id\": \"8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18\",\n  \"qa_scenario_run_id\": \"44444444-4444-4444-8444-444444444444\",\n  \"portfolio_cursor\": \"<string>\"\n}")

	req, _ := http.NewRequest("POST", url, payload)

	req.Header.Add("Authorization", "Bearer <token>")
	req.Header.Add("Content-Type", "application/json")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

HttpResponse<String> response = Unirest.post("http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat")
  .header("Authorization", "Bearer <token>")
  .header("Content-Type", "application/json")
  .body("{\n  \"message\": \"Which 3 am I waiting on payment for?\",\n  \"scope\": \"deal\",\n  \"deal_type\": \"job\",\n  \"job_id\": 42,\n  \"conversation_id\": \"550e8400-e29b-41d4-a716-446655440000\",\n  \"session_id\": \"550e8400-e29b-41d4-a716-446655440000\",\n  \"client_message_id\": \"8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18\",\n  \"qa_scenario_run_id\": \"44444444-4444-4444-8444-444444444444\",\n  \"portfolio_cursor\": \"<string>\"\n}")
  .asString();

require 'uri'
require 'net/http'

url = URI("http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat")

http = Net::HTTP.new(url.host, url.port)

request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'
request["Content-Type"] = 'application/json'
request.body = "{\n  \"message\": \"Which 3 am I waiting on payment for?\",\n  \"scope\": \"deal\",\n  \"deal_type\": \"job\",\n  \"job_id\": 42,\n  \"conversation_id\": \"550e8400-e29b-41d4-a716-446655440000\",\n  \"session_id\": \"550e8400-e29b-41d4-a716-446655440000\",\n  \"client_message_id\": \"8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18\",\n  \"qa_scenario_run_id\": \"44444444-4444-4444-8444-444444444444\",\n  \"portfolio_cursor\": \"<string>\"\n}"

response = http.request(request)
puts response.read_body

{
  "status": "success",
  "message": "Message Sent Successfully!",
  "metadata": {
    "evaluation_mode": false,
    "external_notifications_suppressed": false
  },
  "data": [
    {
      "sender": "assistant",
      "message": "MOGL connects athletes with brands for paid NIL opportunities.",
      "is_read": "1",
      "session_id": "550e8400-e29b-41d4-a716-446655440000",
      "turn_id": 546,
      "sender_id": null,
      "langsmith_trace_id": "ae592555-b6e3-4110-9176-35bebbb1ac73",
      "created_at": "2026-07-22T06:46:17Z",
      "conversation_id": "550e8400-e29b-41d4-a716-446655440000",
      "deal_type": null,
      "job_id": null,
      "response_type": "direct_answer",
      "source_ids": [
        "athlete_kb:what-is-mogl"
      ],
      "confidence": 0.9,
      "scope": "athlete",
      "context_mode": "assistant_help",
      "resolved_job_ids": [],
      "context_resolution": {
        "scope": "athlete",
        "context_mode": "assistant_help",
        "legacy_context_mode": "assistant_help",
        "requested_job_id": null,
        "resolved_job_id": null,
        "resolved_job_ids": [],
        "resolution_reason": "portfolio_follow_up",
        "confidence": 1,
        "candidate_count": 2,
        "truncated": false,
        "lifecycle_mode": "all",
        "portfolio_offset": 0,
        "response_mode": "detail",
        "requested_segment": null,
        "requested_actions": [],
        "referenced_count": 3,
        "count_mismatch": true,
        "referenced_turn_id": null,
        "help_topic": "knowledge_lookup",
        "clarification_segments": [],
        "clarification_required": false,
        "portfolio_groups": [
          {
            "segment": "awaiting_payment",
            "count": 3
          }
        ],
        "portfolio_group_candidates": [
          {
            "segment": "awaiting_payment",
            "count": 3
          }
        ],
        "displayed_job_ids": [
          2
        ],
        "deal_type": null,
        "choice_count": 0
      },
      "continuation_cursor": null,
      "abstain_reason": null,
      "support_request_summary": "I need help resolving a payout issue.",
      "support_action": {
        "type": "mailto",
        "label": "pre-filled in email here",
        "url": "mailto:athlete-support@mogl.online?subject=Help%20from%20the%20AI%20Athlete%20Assistant%20needed&body=I%20need%20help%20with%20a%20payout."
      },
      "quick_button_suggestions": [
        "<string>"
      ],
      "clarification_draft": {
        "id": 81,
        "status": "pending",
        "draft_text": "Hey Wonolo, I don't see any instructions about footwear for the Instagram Reel. Is it okay if I wear sandals in the video?",
        "athlete_snippet": "Hey Wonolo, I don't see any instructions about footwear for the Instagram Reel. Is it okay if I wear sandals in the vide",
        "created_at": "2026-07-22T06:46:17Z",
        "sent_chat_id": null,
        "sent_text": null,
        "sent_at": null,
        "responded_chat_id": null,
        "responded_message_text": null,
        "responded_at": null,
        "superseded_by_id": null,
        "brand_id": 4,
        "connection_id": 912
      },
      "superseded_clarification_drafts": [
        {
          "id": 81,
          "status": "pending",
          "draft_text": "Hey Wonolo, I don't see any instructions about footwear for the Instagram Reel. Is it okay if I wear sandals in the video?",
          "athlete_snippet": "Hey Wonolo, I don't see any instructions about footwear for the Instagram Reel. Is it okay if I wear sandals in the vide",
          "created_at": "2026-07-22T06:46:17Z",
          "sent_chat_id": null,
          "sent_text": null,
          "sent_at": null,
          "responded_chat_id": null,
          "responded_message_text": null,
          "responded_at": null,
          "superseded_by_id": null,
          "brand_id": 4,
          "connection_id": 912
        }
      ]
    }
  ]
}

{
  "message": "Unauthenticated."
}

{
  "message": "The given data was invalid.",
  "errors": {}
}

Send a message to the AI athlete assistant

Send a chat message to the AI assistant. Normal clients use the same request and two-item athlete/assistant response envelope; approved evaluation clients may additionally correlate a QA Scenario Lab run for cleanup. *

Loop dispatch: After the global feature gate, athlete allowlist, request validation, idempotent replay lookup, conversation lifecycle checks, and any server-handled Deal Folder reminder reply, every message uses the bounded tool loop. There is no server-side engine selection. Duplicate client_message_id execution remains serialized for longer than the bounded outbound request plus persistence and delivery side effects.
Loop routing: Free text, exact server-rendered quick-button labels, and ordinal references are interpreted by the loop through its authorized tool surface. A complete legacy scope=deal / deal_type / job_id tuple is still parsed, authorized, and logged for compatibility, but it does not choose the loop’s route or bypass tool authorization. Invalid or unauthorized complete tuples are rejected without numeric coercion.
Deterministic loop fast paths: Explicit MOGL Support requests and reviewed safe no-deal knowledge questions may return the same strict loop result without model or tool calls. All other loop turns use bounded model/tool budgets. Public source IDs are filtered to successful current-turn evidence; malformed or contradictory loop results fail closed rather than exposing untrusted data.
Loop portfolio parity: A fresh unqualified portfolio request is normalized to all lifecycles, the all segment, and offset zero. Overview output is grouped from canonical server counts across current and historical deals; count output uses the canonical requested-segment total rather than page length. List output preserves backend order and renders each deal once. Lists of three or fewer deals may include next-deliverable and next-action detail, while lists of four or more remain compact. Multiple actions compose in the fixed overview, count, list, guidance order. Athlete-facing active, open, current, and high-level in-progress requests use work_remaining (in_progress + resubmit_needed). Legacy active remains a deprecated compatibility count. The voided segment includes fully voided deals plus partial-void conditions; exclusive summary_counts.voided counts fully voided deals only.
Conversation handling: conversation_id is the canonical conversation identifier. session_id is accepted as a backwards-compatible alias. If neither is supplied, or the supplied conversation cannot be reused, the server creates a new conversation. Normal clients use message, client_message_id, and conversation_id or session_id. After idle session rotation, a tap that matches the current persisted Deal Folder nudge label is resolved server-side; clients do not send action IDs or reply-to turn IDs.
Evaluation cleanup correlation: Approved non-production evaluation athletes may provide qa_scenario_run_id together with one requested conversation UUID in conversation_id (or its session_id alias). Before Assistant dispatch, Laravel creates and manifests that exact dedicated session, canonically bound to the fixture-created job; a retry may reuse it only when it is already a Created session entity of the same run and athlete. This prevents fallback to another active athlete session and leaves failed processing cleanup-owned. Persisted portfolio turns and logs may have job_id=null; non-null values must match the fixture job. Normal athletes, mismatched runs/jobs/sessions, cross-athlete requests, and cross-run attachments fail validation. Clients cannot supply entity IDs.
Historical turns: Turns persisted by the retired v3 semantic-routing path remain readable through idempotent replay and history. They keep their stored context_resolution, quick-button labels, and clarification_draft linkage; no new turn is created by that path.
Quick buttons: AI answer-stage suggestions are suppressed, and athlete-prompted loop responses return an empty list. Historical v3 turns replay their persisted labels. Proactive assistant turns may also return up to three server-owned suggestions. Deal Folder reminder buttons name the deal and item; tapping a label, a brand-draft button, or a support button is handled by the existing chat, clarification-draft, and support-mailto paths (never auto-sent).
Hybrid answer contract (jobs only): In the answer stage, direct_answer_with_clarification returns both a factual answer and a persisted brand-message draft, and draft-bearing job responses return a non-null clarification_draft with no quick buttons. Brand draft text is validated natural brand-facing copy; machine-only clarification reasons/topics remain tracing metadata and known internal namespaces are repaired or rejected before persistence. A historical v3 routing clarification is the exception on replay: it may use response_type=clarification but returns clarification_draft=null and may expose bounded deal-choice buttons.
Contact support: Existing job-scoped support remains supported. A no-deal support request uses assistant_help / support_contact, returns job_id=null and resolved_job_ids=[], and may return response_type=escalation, a sanitized support_request_summary, and a proposal-only support_action mailto. The athlete must click, review, and send the email; the backend never sends it automatically. For example, “Please contact MOGL support about my payout” can return an escalation with the summary “I need help resolving a payout issue.” and no deal metadata. The athlete-facing label is pre-filled in email here.
Knowledge lookup: A safe no-deal KB question uses assistant_help / knowledge_lookup and returns a direct curated answer with its athlete_kb:* source IDs. It has job_id=null, resolved_job_ids=[], no support summary/action, no clarification draft, and no quick buttons. For example, “What is MOGL?” can return a direct MOGL overview sourced by athlete_kb:what-is-mogl.
Access control: Athlete must be allowlisted. Portfolio data is rebuilt from the authenticated athlete’s authorized jobs. Job-scoped questions require a non-cancelled application. Fan requests require ownership (fan_request_service.athlete_id). Returns 403 otherwise.

POST

athlete

ai-athlete-assistant

chat

Send a message to the AI athlete assistant

curl --request POST \
  --url http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "message": "Which 3 am I waiting on payment for?",
  "scope": "deal",
  "deal_type": "job",
  "job_id": 42,
  "conversation_id": "550e8400-e29b-41d4-a716-446655440000",
  "session_id": "550e8400-e29b-41d4-a716-446655440000",
  "client_message_id": "8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18",
  "qa_scenario_run_id": "44444444-4444-4444-8444-444444444444",
  "portfolio_cursor": "<string>"
}
'

import requests

url = "http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat"

payload = {
    "message": "Which 3 am I waiting on payment for?",
    "scope": "deal",
    "deal_type": "job",
    "job_id": 42,
    "conversation_id": "550e8400-e29b-41d4-a716-446655440000",
    "session_id": "550e8400-e29b-41d4-a716-446655440000",
    "client_message_id": "8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18",
    "qa_scenario_run_id": "44444444-4444-4444-8444-444444444444",
    "portfolio_cursor": "<string>"
}
headers = {
    "Authorization": "Bearer <token>",
    "Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.text)

const options = {
  method: 'POST',
  headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
  body: JSON.stringify({
    message: 'Which 3 am I waiting on payment for?',
    scope: 'deal',
    deal_type: 'job',
    job_id: 42,
    conversation_id: '550e8400-e29b-41d4-a716-446655440000',
    session_id: '550e8400-e29b-41d4-a716-446655440000',
    client_message_id: '8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18',
    qa_scenario_run_id: '44444444-4444-4444-8444-444444444444',
    portfolio_cursor: '<string>'
  })
};

fetch('http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_POSTFIELDS => json_encode([
    'message' => 'Which 3 am I waiting on payment for?',
    'scope' => 'deal',
    'deal_type' => 'job',
    'job_id' => 42,
    'conversation_id' => '550e8400-e29b-41d4-a716-446655440000',
    'session_id' => '550e8400-e29b-41d4-a716-446655440000',
    'client_message_id' => '8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18',
    'qa_scenario_run_id' => '44444444-4444-4444-8444-444444444444',
    'portfolio_cursor' => '<string>'
  ]),
  CURLOPT_HTTPHEADER => [
    "Authorization: Bearer <token>",
    "Content-Type: application/json"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"strings"
	"net/http"
	"io"
)

func main() {

	url := "http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat"

	payload := strings.NewReader("{\n  \"message\": \"Which 3 am I waiting on payment for?\",\n  \"scope\": \"deal\",\n  \"deal_type\": \"job\",\n  \"job_id\": 42,\n  \"conversation_id\": \"550e8400-e29b-41d4-a716-446655440000\",\n  \"session_id\": \"550e8400-e29b-41d4-a716-446655440000\",\n  \"client_message_id\": \"8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18\",\n  \"qa_scenario_run_id\": \"44444444-4444-4444-8444-444444444444\",\n  \"portfolio_cursor\": \"<string>\"\n}")

	req, _ := http.NewRequest("POST", url, payload)

	req.Header.Add("Authorization", "Bearer <token>")
	req.Header.Add("Content-Type", "application/json")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

HttpResponse<String> response = Unirest.post("http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat")
  .header("Authorization", "Bearer <token>")
  .header("Content-Type", "application/json")
  .body("{\n  \"message\": \"Which 3 am I waiting on payment for?\",\n  \"scope\": \"deal\",\n  \"deal_type\": \"job\",\n  \"job_id\": 42,\n  \"conversation_id\": \"550e8400-e29b-41d4-a716-446655440000\",\n  \"session_id\": \"550e8400-e29b-41d4-a716-446655440000\",\n  \"client_message_id\": \"8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18\",\n  \"qa_scenario_run_id\": \"44444444-4444-4444-8444-444444444444\",\n  \"portfolio_cursor\": \"<string>\"\n}")
  .asString();

require 'uri'
require 'net/http'

url = URI("http://localhost/mogl/mogl-backend/api/athlete/ai-athlete-assistant/chat")

http = Net::HTTP.new(url.host, url.port)

request = Net::HTTP::Post.new(url)
request["Authorization"] = 'Bearer <token>'
request["Content-Type"] = 'application/json'
request.body = "{\n  \"message\": \"Which 3 am I waiting on payment for?\",\n  \"scope\": \"deal\",\n  \"deal_type\": \"job\",\n  \"job_id\": 42,\n  \"conversation_id\": \"550e8400-e29b-41d4-a716-446655440000\",\n  \"session_id\": \"550e8400-e29b-41d4-a716-446655440000\",\n  \"client_message_id\": \"8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18\",\n  \"qa_scenario_run_id\": \"44444444-4444-4444-8444-444444444444\",\n  \"portfolio_cursor\": \"<string>\"\n}"

response = http.request(request)
puts response.read_body

{
  "status": "success",
  "message": "Message Sent Successfully!",
  "metadata": {
    "evaluation_mode": false,
    "external_notifications_suppressed": false
  },
  "data": [
    {
      "sender": "assistant",
      "message": "MOGL connects athletes with brands for paid NIL opportunities.",
      "is_read": "1",
      "session_id": "550e8400-e29b-41d4-a716-446655440000",
      "turn_id": 546,
      "sender_id": null,
      "langsmith_trace_id": "ae592555-b6e3-4110-9176-35bebbb1ac73",
      "created_at": "2026-07-22T06:46:17Z",
      "conversation_id": "550e8400-e29b-41d4-a716-446655440000",
      "deal_type": null,
      "job_id": null,
      "response_type": "direct_answer",
      "source_ids": [
        "athlete_kb:what-is-mogl"
      ],
      "confidence": 0.9,
      "scope": "athlete",
      "context_mode": "assistant_help",
      "resolved_job_ids": [],
      "context_resolution": {
        "scope": "athlete",
        "context_mode": "assistant_help",
        "legacy_context_mode": "assistant_help",
        "requested_job_id": null,
        "resolved_job_id": null,
        "resolved_job_ids": [],
        "resolution_reason": "portfolio_follow_up",
        "confidence": 1,
        "candidate_count": 2,
        "truncated": false,
        "lifecycle_mode": "all",
        "portfolio_offset": 0,
        "response_mode": "detail",
        "requested_segment": null,
        "requested_actions": [],
        "referenced_count": 3,
        "count_mismatch": true,
        "referenced_turn_id": null,
        "help_topic": "knowledge_lookup",
        "clarification_segments": [],
        "clarification_required": false,
        "portfolio_groups": [
          {
            "segment": "awaiting_payment",
            "count": 3
          }
        ],
        "portfolio_group_candidates": [
          {
            "segment": "awaiting_payment",
            "count": 3
          }
        ],
        "displayed_job_ids": [
          2
        ],
        "deal_type": null,
        "choice_count": 0
      },
      "continuation_cursor": null,
      "abstain_reason": null,
      "support_request_summary": "I need help resolving a payout issue.",
      "support_action": {
        "type": "mailto",
        "label": "pre-filled in email here",
        "url": "mailto:athlete-support@mogl.online?subject=Help%20from%20the%20AI%20Athlete%20Assistant%20needed&body=I%20need%20help%20with%20a%20payout."
      },
      "quick_button_suggestions": [
        "<string>"
      ],
      "clarification_draft": {
        "id": 81,
        "status": "pending",
        "draft_text": "Hey Wonolo, I don't see any instructions about footwear for the Instagram Reel. Is it okay if I wear sandals in the video?",
        "athlete_snippet": "Hey Wonolo, I don't see any instructions about footwear for the Instagram Reel. Is it okay if I wear sandals in the vide",
        "created_at": "2026-07-22T06:46:17Z",
        "sent_chat_id": null,
        "sent_text": null,
        "sent_at": null,
        "responded_chat_id": null,
        "responded_message_text": null,
        "responded_at": null,
        "superseded_by_id": null,
        "brand_id": 4,
        "connection_id": 912
      },
      "superseded_clarification_drafts": [
        {
          "id": 81,
          "status": "pending",
          "draft_text": "Hey Wonolo, I don't see any instructions about footwear for the Instagram Reel. Is it okay if I wear sandals in the video?",
          "athlete_snippet": "Hey Wonolo, I don't see any instructions about footwear for the Instagram Reel. Is it okay if I wear sandals in the vide",
          "created_at": "2026-07-22T06:46:17Z",
          "sent_chat_id": null,
          "sent_text": null,
          "sent_at": null,
          "responded_chat_id": null,
          "responded_message_text": null,
          "responded_at": null,
          "superseded_by_id": null,
          "brand_id": 4,
          "connection_id": 912
        }
      ]
    }
  ]
}

{
  "message": "Unauthenticated."
}

{
  "message": "The given data was invalid.",
  "errors": {}
}

Authorizations

Authorization

string

header

required

JWT Bearer token authentication. Use the /api/login endpoint to obtain a token.

Body

application/json

message

string

required

The athlete's message to the assistant (max 2000 characters).

Maximum string length: 2000

Example:

"Which 3 am I waiting on payment for?"

scope

enum<string> | null

Legacy compatibility discriminator. With allowlisted deal_type and a strictly integral positive job_id it forms a complete tuple. The tuple is authorized and logged for compatibility; it does not direct loop tool selection. Partial tuples are logged and discarded.

Available options:

athlete,

deal

Example:

"deal"

deal_type

enum<string> | null

Legacy tuple type: job references a partner job and fan_req references an athlete-owned, non-deleted fan service request. The complete tuple is authorized but does not route the turn; the loop resolves the message through authorized tools.

Available options:

job,

fan_req

Example:

"job"

job_id

integer | null

Polymorphic legacy tuple ID: partner_jobs.id for job or fan_request_service.id for fan_req. Laravel authorizes and logs complete tuples, rejects invalid or unauthorized values, and never truncates decimal or floating-point values. The value does not direct loop routing.

Required range: x >= 1

Example:

42

conversation_id

string | null

Canonical ID of an existing conversation to continue. When qa_scenario_run_id is supplied, this (or session_id) must be a UUID and becomes the exact dedicated run-owned session; both aliases may be sent only when identical.

Maximum string length: 255

Example:

"550e8400-e29b-41d4-a716-446655440000"

session_id

string | null

Backwards-compatible alias for conversation_id. When qa_scenario_run_id is supplied, this (or conversation_id) must be a UUID; both aliases may be sent only when identical.

Maximum string length: 255

Example:

"550e8400-e29b-41d4-a716-446655440000"

client_message_id

string<uuid> | null

Idempotency key required for modern requests. Optional only for legacy payloads that include a non-null deal_type or job_id.

Maximum string length: 64

Example:

"8dc1b7b7-716e-4f26-b4fa-cc9c8d300c18"

qa_scenario_run_id

string<uuid> | null

Optional evaluation-only cleanup correlation. Requires one requested conversation UUID. Accepted only for a server-approved non-production evaluation athlete and a matching succeeded single-athlete run of an evaluation-correlated scenario (evaluation.recent_hire_support_escalation@1, files.mixed_deliverables@1, files.needs_review@1, or files.revision_requested@1) in the current environment. The server reserves that exact run-owned session before dispatch and derives all attached turn entity IDs from persisted data; clients cannot supply them.

Example:

"44444444-4444-4444-8444-444444444444"

portfolio_cursor

string | null

Deprecated compatibility field from the retired v3 path. It is still validated and accepted from released clients but does not route the turn; the loop resolves the message through its tools and does not promise cursor continuation for arbitrary lists.

Maximum string length: 512

Response

Message sent. Returns the two-item envelope containing the athlete message and assistant reply plus required server-derived evaluation metadata. Clients cannot enable, disable, or spoof metadata values: both booleans are false for normal athletes and true only for approved non-production evaluation athletes. New turns return a loop-1 trace context_resolution; replayed historical v3 turns return their stored semantic context_resolution; top-level compatibility fields remain available in both cases. Loop-1 portfolio turns may persist optional strict compact portfolio_state metadata inside context_resolution for trusted continuity, without exposing raw tool arguments or full results. No-deal support replies may include a sanitized support_request_summary and review-only support_action. Safe knowledge replies contain curated text/source IDs and omit support actions, drafts, and buttons.

status

string

required

Example:

"success"

message

string

required

Example:

"Message Sent Successfully!"

metadata

object

required

Server-derived evaluation and notification-safety metadata. Clients cannot enable, disable, or spoof these values. Both fields are false for normal athletes and true only for approved non-production evaluation athletes.

Show child attributes

data

object[]

required

Show child attributes

Core API

University API

Notifications API

Send a message to the AI athlete assistant

Authorizations

Body

Response