posthog.com spec: hardcoded US host breaks EU accounts with a misleading 401 — servers should use a {region} variable (fix tested end-to-end)

[ash-jentic]

Problem

The PostHog spec (apis/openapi/posthog.com/posthog-api/1.0/openapi.json) hardcodes a single server:

"servers": [{ "url": "https://app.posthog.com" }]

PostHog is region-split: US and EU cloud projects live on different hosts (us.posthog.com / eu.posthog.com; app.posthog.com is a legacy US alias). A valid EU personal API key sent to the US host fails with upstream 401 "Personal API key found in request Authorization header is invalid." — an error that misattributes a host/region problem to the credential. An EU user following this spec can never succeed, and the error text sends them to debug the wrong thing (we lost significant time to exactly this).

Proposed fix (content change — hence an issue per AGENTS.md)

Express the region as an OpenAPI server variable so one catalogue entry serves both regions:

"servers": [
  {
    "url": "https://{region}.posthog.com",
    "variables": {
      "region": {
        "default": "us",
        "enum": ["us", "eu"],
        "description": "PostHog data region (US or EU) - must match your project's region; the wrong region returns 401 invalid key."
      }
    }
  }
]

• default: "us" preserves today's behaviour for existing US users (backward-compatible).
• The description matters: it surfaces in tooling as inline guidance for the exact failure mode.
• One entry, no separate us/eu spec duplicates.

Verified working

We tested this exact change end-to-end on a self-hosted Jentic One instance (2026-07-14): the credential UI auto-renders a Region dropdown from the variable, the broker substitutes it into the upstream URL, and a previously always-401 EU key returned 200 with real project data the moment requests hit eu.posthog.com. (TLS-level confirmation: server_hostname='eu.posthog.com'.)

Notes

• Same pattern already used correctly elsewhere in the catalogue: sentry.io ({region}.sentry.io), mailchimp.com ({dc}.api.mailchimp.com), atlassian.com ({your-domain}.atlassian.net) — PostHog just needs the same treatment.
• This is one instance of a general class (region-split SaaS: Mixpanel, Amplitude, Segment, Braze, SendGrid, PagerDuty, Intercom, …). Happy to follow up with the broader list if useful.
• Separately (not this issue): the spec declares only bearerAuth; PostHog also supports OAuth, which the spec omits — noting for completeness.

[github-actions]

❌ Failed to import OpenAPI specification

Error: Import service failed

Details: Traceback (most recent call last):
File "/opt/hostedtoolcache/Python/3.12.13/x64/bin/jentic-apitools", line 6, in
sys.exit(cli())
^^^^^
File "/opt/hostedtoolcache/Python/3.12.13/x64/lib/python3.12/site-packages/click/core.py", line 1569, in call
return self.main(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/hostedtoolcache/Python/3.12.13/x64/lib/python3.12/site-packages/click/core.py", line 1490, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "/opt/hostedtoolcache/Python/3.12.13/x64/lib/python3.12/site-packages/click/core.py", line 1970, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/hostedtoolcache/Python/3.12.13/x64/lib/python3.12/site-packages/click/core.py", line 1353, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/hostedtoolcache/Python/3.12.13/x64/lib/python3.12/site-packages/click/core.py", line 907, in invoke
return callback(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/hostedtoolcache/Python/3.12.13/x64/lib/python3.12/site-packages/jentic/apitools/cli/helpers.py", line 52, in wrapper
return fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^
File "/opt/hostedtoolcache/Python/3.12.13/x64/lib/python3.12/site-packages/jentic/apitools/cli/main.py", line 395, in import_cmd
meta=OASRequestMeta(
^^^^^^^^^^^^^^^
File "/opt/hostedtoolcache/Python/3.12.13/x64/lib/python3.12/site-packages/pydantic/main.py", line 263, in init
validated_self = self.pydantic_validator.validate_python(data, self_instance=self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pydantic_core._pydantic_core.ValidationError: 1 validation error for OASRequestMeta
label
String should have at least 1 character [type=string_too_short, input_value='', input_type=str]
For further information visit https://errors.pydantic.dev/2.13/v/string_too_short

Please check that your OpenAPI URL is accessible and contains a valid OpenAPI specification.

If you believe this is a bug with the import service or need additional support, please contact the development team at Jentic Community Discord (https://discord.gg/yrxmDZWMqB).

Alternatively create a new issue reporting the bug (https://github.com/jentic/jentic-public-apis/issues/new?template=BLANK_ISSUE).