Prepare app launch URL

Prepares an Auth SSO authorize URL without recording launch analytics or usage.

Outcome

Prepares an Auth SSO authorize URL without recording launch analytics or usage.

Before you start

Verify the intended environment, authenticated identity and explicitly authorized ownership context.
Discover the published launcher:read permission and any required resource grant.

Discover the target

topolo whoami --json
topolo actions get app_topolo_one.launch.get --detail --json

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

Request

GET /api/launch/{appId}

Inspect and test this action.

Input fields

Field	Required	Meaning	Constraints
`appId`	Required	Exact canonical application/service identifier from the discovery expected by this action; a display name is not an id.	{"type":"string","minLength":1}

Inspect nested fields.

Interpret the response

Inspect app.id, launchUrl and expiresAt, then follow Auth and the target application’s actual handoff. Preparing a URL does not prove target login or grant an entitlement.

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.launch.get --data @payload.json --json
topolo actions plan app_topolo_one.launch.get --data @payload.json --json
topolo actions call app_topolo_one.launch.get --data @payload.json --detail --json

MCP planning and execution use the same reviewed input:

{
  "tool": "topolo_prepare_action",
  "arguments": {
    "actionId": "app_topolo_one.launch.get",
    "input": {
      "appId": "fixture_launch_mail"
    }
  }
}

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_one.launch.get",
    "input": {
      "appId": "fixture_launch_mail"
    },
    "detail": true
  }
}

Successful response · HTTP 200

Input · payload.json:

{
  "appId": "fixture_launch_mail"
}

Captured response:

{
  "launchUrl": "https://auth.test.com/sso/authorize?redirect_uri=https%3A%2F%2Fmail.test%2Fauth%2Fcallback&state=12cf8b5b-d486-4fc6-bfd9-c0a851a49155&response_mode=sso_code&service=fixture_launch_mail&app_id=fixture_launch_mail",
  "app": {
    "id": "fixture_launch_mail",
    "name": "Mail",
    "description": "Launch Mail"
  },
  "expiresAt": "2026-10-06T01:44:00.920Z"
}

Inspect app.id, launchUrl and expiresAt, then follow Auth and the target application’s actual handoff. Preparing a URL does not prove target login or grant an entitlement.

Refused request · HTTP 401 · auth_error

Input · payload.json:

{
  "appId": "fixture_launch_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.

Verify the result

Inspect app.id, launchUrl and expiresAt, then follow Auth and the target application’s actual handoff. Preparing a URL does not prove target login or grant an entitlement.

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

An unused handoff URL expires. Use launch.create for an explicit launch that records analytics.

Launch Create: Create a launch for one app, recording the launch and returning where to send the user.