GoToMeeting

{
  "service_type": "platform",
  "base_url": "https://api.citrixonline.com",
  "auth_method": "oauth2",
  "auth_config": {
    "flow": "authorization_code",
    "authorization_url": "https://api.citrixonline.com/oauth/authorize",
    "token_url": "https://api.citrixonline.com/oauth/access_token",
    "notes": "OAuth 2.0 via Citrix Online API. Legacy GoToMeeting API deprecated; migrated to GoTo (LogMeIn) developer platform."
  },
  "endpoints": [
    {
      "name": "Get Organizer",
      "method": "GET",
      "path": "/G2M/rest/organizers/{organizerKey}",
      "description": "Retrieve organizer account details"
    },
    {
      "name": "Create Meeting",
      "method": "POST",
      "path": "/G2M/rest/meetings",
      "description": "Schedule a new meeting for an organizer"
    },
    {
      "name": "Get Meeting",
      "method": "GET",
      "path": "/G2M/rest/meetings/{meetingId}",
      "description": "Retrieve meeting details"
    },
    {
      "name": "Update Meeting",
      "method": "PUT",
      "path": "/G2M/rest/meetings/{meetingId}",
      "description": "Update an existing meeting"
    },
    {
      "name": "Delete Meeting",
      "method": "DELETE",
      "path": "/G2M/rest/meetings/{meetingId}",
      "description": "Cancel a scheduled meeting"
    },
    {
      "name": "List Upcoming Meetings",
      "method": "GET",
      "path": "/G2M/rest/meetings",
      "description": "List upcoming meetings for an organizer"
    },
    {
      "name": "Get Attendees",
      "method": "GET",
      "path": "/G2M/rest/meetings/{meetingId}/attendees",
      "description": "List attendees of a meeting"
    },
    {
      "name": "Create Registrant",
      "method": "POST",
      "path": "/G2M/rest/meetings/{meetingId}/registrants",
      "description": "Register a participant for a meeting"
    },
    {
      "name": "Get Sessions",
      "method": "GET",
      "path": "/G2M/rest/meetings/{meetingId}/sessions",
      "description": "Retrieve session history for a meeting"
    },
    {
      "name": "Get Historical Attendees",
      "method": "GET",
      "path": "/G2M/rest/meetings/{meetingId}/attendees",
      "description": "Retrieve attendees for past sessions"
    }
  ],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "notes": "GoToMeeting is sold as a subscription (per-organizer tiers). API access is included with paid accounts; no separate API pricing tier historically for GoToMeeting. GoTo (rebranded) uses a per-plan model.",
      "tiers": [
        "Professional",
        "Business",
        "Enterprise"
      ]
    }
  },
  "rate_limits": {
    "notes": "Citrix Online historically enforced API rate limits (requests per day/hour) tied to account tier. Exact numbers not publicly documented after migration to GoTo developer platform."
  },
  "capabilities": [
    "Meeting provisioning and scheduling",
    "Meeting management (create, update, cancel, list)",
    "Organizer and user account management",
    "Attendee and registrant management",
    "Meeting session history and reporting",
    "Webinar management (GoToWebinar via same API family)",
    "GoToTraining and GoToAssist integrations",
    "OAuth 2.0 secure integration into third-party apps",
    "Embedding meeting join/start flows into existing infrastructure"
  ],
  "raw_analysis": "GoToMeeting (originally by Citrix, now part of GoTo / LogMeIn after acquisition) is a well-established web conferencing and online meeting platform aimed at businesses for virtual meetings, webinars, and collaboration. It is a mature product with a long-standing public REST API documented at developer.citrixonline.com (legacy) and now via GoTo's developer portal.\n\nThe API is a RESTful interface that allows seamless integration of GoToMeeting provisioning and meeting management into existing infrastructure or third-party applications. Key capabilities include scheduling/creating meetings, updating and cancelling them, listing upcoming meetings, managing organizers and attendees, and retrieving session/attendance reports. This makes it suitable for embedding conferencing into CRM, LMS, HR, scheduling, and telehealth workflows.\n\nAuthentication is OAuth 2.0 (authorization code flow) with organizer-level and account-level scopes. The old Citrix Online API endpoints (api.citrixonline.com) are largely deprecated following the GoTo rebrand, and developers are directed to the GoTo developer portal for current API keys and documentation.\n\nPricing is subscription-based per organizer (Professional, Business, Enterprise tiers); API access historically came bundled with paid plans rather than as a metered product, with rate limits tied to account tier.\n\nThe platform is mature and enterprise-ready, but its API ecosystem has undergone disruption due to the Citrix→LogMeIn→GoTo ownership and branding changes, so integration work should target the current GoTo developer documentation rather than legacy Citrix Online references."
}

0/3 tests passed

{
  "overall": 42,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 4.0,
    "response_parseability": 5.0,
    "error_clarity": 4.0,
    "doc_quality": 5.0,
    "auth_simplicity": 5.0,
    "latency": 2.0,
    "consistency": 3.0
  },
  "pricing_normalized": {
    "model": "subscription",
    "tiers": ["Professional", "Business", "Enterprise"],
    "api_access": "included_with_paid_plan",
    "notes": "No standalone API pricing; API bundled with per-organizer subscription. Costs scale with seat count, opaque for API-only automation use cases."
  },
  "issues": [
    "All three verification checks failed with DNS resolution errors ('Name or service not known') — platform domain appears unreachable or misconfigured, making runtime validation impossible.",
    "No accessible robots.txt or llms.txt — poor machine-readable discoverability for agents.",
    "DNS failures suggest either offsite infra instability or incorrect domain resolution, undermining consistency/reliability signal.",
    "Subscription-only pricing tied to per-organizer seats makes API automation cost-unpredictable for agent-driven workloads.",
    "Accessible tooling and embedded API paths (OAuth 2.0, join/start flows) are documented but rollout complexity hints at non-trivial first-run integration.",
    "No public latency signal obtainable due to DNS failure; degraded ability to benchmark responsiveness."
  ],
  "recommendations": [
    "Verify and stabilize DNS/public endpoint resolution; agents cannot verify uptime or fetch discovery docs when the host is unresolvable.",
    "Publish robots.txt and an llms.txt with clear capability/endpoint summaries to improve agent onboarding and token efficiency.",
    "Offer a documented usage-based or API-only pricing scheme so agents can reason about cost without seat-based subscription ambiguity.",
    "Provide a quickstart with copy-paste OAuth 2.0 flow and scoped token examples to raise first-try success.",
    "Surface a public status page and uptime transparency to improve reliability perception.",
    "Structure API responses and error payloads with consistent machine-readable schemas to improve response_parseability and error_clarity.",
    "Document known limitations (e.g., quota, tier-gated endpoints) explicitly to reduce agent trial-and-error."
  ]
}