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",
  "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",
    "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',
    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',
    '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  \"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  \"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  \"portfolio_cursor\": \"<string>\"\n}"

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

{
  "status": "success",
  "message": "Message Sent Successfully!",
  "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,
      "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": "The athlete needs 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=The%20athlete%20needs%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. The public request and two-item athlete/assistant response envelope are unchanged across both server-selected execution paths. *

Loop dispatch and rollback: After the global feature gate, athlete allowlist, request validation, idempotent replay lookup, and conversation lifecycle checks, the server-side AI_ATHLETE_ASSISTANT_LOOP_ENABLED flag selects the implementation. When enabled (the development default), messages use the bounded tool loop. Duplicate client_message_id execution remains serialized for longer than the bounded outbound request plus persistence and delivery side effects. When disabled, the existing v3 semantic-resolution and answer path remains available as a server-side rollback. The flag is operational configuration and is never accepted from the client.
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.
V3 rollback semantic routing and answer rendering: When the loop flag is disabled, the AI service owns free-text interpretation and returns an advisory typed resolution. Laravel validates the complete resolution shape, enforces confidence and authorization against backend-supplied candidates, verifies referenced-turn metadata, derives trusted continuity values, and reloads current authorized facts. The AI answer stage then renders the athlete response from that validated resolution and bounded current data. Raw model proposals are never exposed as public context_resolution.
V3 rollback mechanical fast paths: An authorized complete structured deal hint, an explicit portfolio_cursor, an exact server-rendered deal label, or an ordinal reference to a server-rendered deal list bypasses v3 free-text semantic interpretation. Structured hints support both partner jobs and athlete-owned fan requests; Laravel authorizes the referenced record before routing. Partial legacy fields are logged and discarded so the normalized request proceeds through v3 semantic routing.
V3 rollback safe fallback: Malformed, incomplete, unsupported, low-confidence, stale, or unauthorized semantic proposals become a generic clarification instead of selecting a guessed deal or status.
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.
V3 rollback fresh and anchored portfolio routing: A fresh portfolio request returns resolution_reason=portfolio_query, starts at offset zero, and has no referenced_turn_id or referenced_count; Laravel builds it from current authorized data. A status/count follow-up returns portfolio_follow_up only after referenced_turn_id matches a bounded assistant turn; Laravel reloads that turn’s server-owned portfolio_groups, derives referenced_count, and compares it with the current authorized total to produce count_mismatch. A natural portfolio_continuation must anchor a bounded assistant turn containing a valid server-owned continuation cursor. An explicit portfolio_cursor is separately validated as a mechanical continuation request. Continuation cursors apply only to truncated portfolio lists, not to oversized deal-ambiguity results, and do not promise that an arbitrary text list can be continued.
V3 rollback routing clarification: Ambiguous status references return resolution_reason=ambiguous, clarification_segments, choice_count=0, no deal quick buttons, and no clarification_draft. Ambiguous deal references expose no raw choices, but may return two or three authorized, ID-suffixed deal labels as quick buttons with choice_count set to the full hidden choice count. More than three deal matches are rendered as a text-only bounded list without a continuation promise. Athlete-facing copy uses deal-status language rather than internal continuity metadata names.
V3 rollback assistant help: portfolio_statuses, mogl_overview, support_contact, and knowledge_lookup route as context_mode=assistant_help with a validated help_topic. Canonical assistant-help proposals and enforced responses have no requested or resolved deal ID, deal type, portfolio metadata, history anchor, or clarification metadata; public array fields such as resolved_job_ids, requested_actions, and clarification_segments remain non-null empty arrays.
Quick buttons and proactive continuity: Loop turns always return quick_button_suggestions=[]. On the v3 rollback path, athlete-prompted responses remain empty except for the backend-owned ambiguous-deal routing clarification described above. Availability confirmation may persist a proactive welcome turn with the server-owned originating standard job and the labels Tell me about the deal and Rough schedule please. The labels express intent only and never carry identity authority. Bounded history projects the originating job as trusted selected_deal_id; the loop may inherit it only from that assistant history, and every get_deal/get_timeline call reauthorizes it. Detail uses current deal evidence; rough schedule uses current timeline evidence and athlete-local display dates. Missing, fan-scoped, malformed, or ambiguous continuity clarifies instead of silently selecting a job. Future routing replacements must preserve ENG-1180/ENG-1181 same-intent behavior.
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 backend-owned routing clarification is the exception: 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 review-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 “The athlete needs help resolving a payout issue.” and no deal metadata.
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",
  "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",
    "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',
    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',
    '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  \"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  \"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  \"portfolio_cursor\": \"<string>\"\n}"

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

{
  "status": "success",
  "message": "Message Sent Successfully!",
  "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,
      "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": "The athlete needs 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=The%20athlete%20needs%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 on both paths; it routes only the v3 rollback path and 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 routes only v3; 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 on both paths, 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.

Maximum string length: 255

Example:

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

session_id

string | null

Backwards-compatible alias for conversation_id.

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"

portfolio_cursor

string | null

Opaque v3 compatibility cursor from a truncated portfolio list. On the v3 rollback path it bypasses free-text semantic routing only after Laravel validates and decodes it. Loop turns resolve the message through the tool loop and do not promise cursor continuation for arbitrary lists.

Maximum string length: 512

Response

Message sent. Returns the unchanged two-item envelope containing the athlete message and assistant reply. The assistant item may include either a historical/v3 semantic context_resolution or a loop-1 trace 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

Example:

"success"

message

string

Example:

"Message Sent Successfully!"

data

object[]

Show child attributes

Core API

University API

Notifications API

Send a message to the AI athlete assistant

Authorizations

Body

Response