Acknowledge legacy usage request

Outcome

Authenticates the request and acknowledges the supplied application id. Its legacy trackLaunch helper does not persist a usage event.

Before you start

• Verify the intended environment, authenticated identity and explicitly authorized ownership context.
• Discover the published dashboard:read permission and any required resource grant.
• Approve the actual effects before confirming the unchanged planned request. Fixture identifiers, recipients and provider responses authorize no live operation.

Discover the target

topolo whoami --json
topolo actions get app_topolo_one.track.create --detail --json

• appId: Exact canonical application/service identifier from the discovery expected by this action; a display name is not an id.

Request

POST /api/track

Inspect and test this action.

Input fields

Inspect nested fields.

Interpret the response

Inspect success as an acknowledgement only. It is not evidence of recorded analytics: this handler's legacy helper is a no-op. Actual launch analytics are recorded by launch.create.

Inspect the declared output schema and captured variants.

Worked examples

Actual exported One Worker with local Miniflare D1/KV. Authentication, application discovery, checkout, billing and remote widget providers are controlled synthetic responses; outbound access is sealed. No live provider outcome is established.

Save the reviewed input below as payload.json; substitute discovered identifiers and bind credential/resource context separately. CLI:

topolo actions validate app_topolo_one.track.create --data @payload.json --json
topolo actions plan app_topolo_one.track.create --data @payload.json --json
topolo actions call app_topolo_one.track.create --data @payload.json --confirm --detail --json

MCP planning and execution use the same reviewed input:

{
  "tool": "topolo_prepare_action",
  "arguments": {
    "actionId": "app_topolo_one.track.create",
    "input": {
      "appId": "fixture_legacy_track"
    }
  }
}

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_one.track.create",
    "input": {
      "appId": "fixture_legacy_track"
    },
    "confirm": true,
    "detail": true
  }
}

Successful response · HTTP 200

Input · payload.json:

{
  "appId": "fixture_legacy_track"
}

Captured response:

{
  "success": true,
  "message": "Usage tracked"
}

Inspect success as an acknowledgement only. It is not evidence of recorded analytics: this handler's legacy helper is a no-op. Actual launch analytics are recorded by launch.create.

Refused request · HTTP 401 · auth_error

Input · payload.json:

{
  "appId": "mail"
}

Captured response:

{
  "error": "Token validation failed"
}

Authenticate using the required credential type for this action; service-only actions require the registered Auth service identity.

Successful response · HTTP 200

Input · payload.json:

{
  "appId": "mail"
}

Captured response:

{
  "success": true,
  "message": "Usage tracked"
}

Inspect success as an acknowledgement only. It is not evidence of recorded analytics: this handler's legacy helper is a no-op. Actual launch analytics are recorded by launch.create.

Verify the result

• Inspect success as an acknowledgement only. It is not evidence of recorded analytics: this handler's legacy helper is a no-op. Actual launch analytics are recorded by launch.create.

Errors and recovery

• auth_error (HTTP 401): Authenticate using the required credential type for this action; service-only actions require the registered Auth service identity.

These are observed local refusals; inspect the raw error body because one SDK code can represent several handler messages. Preserve the request id when available.

Recovery boundary

Repeat the schema-valid request only if its acknowledgement is needed. Retrying this legacy action cannot repair missing analytics because it writes no event. Use the documented launch flow for actual launch tracking.

Evidence

Actual exported One Worker with local Miniflare D1/KV. Authentication, application discovery, checkout, billing and remote widget providers are controlled synthetic responses; outbound access is sealed. No live provider outcome is established.