Sign in
Settings

Get where third-party callbacks are sent

Changed on

Returns the base URL Temps hands to third parties that call back into it (email open/click tracking, git provider webhooks, SES/SNS delivery events, revenue webhooks, the Sentry DSN) and whether Temps can tell that URL is unreachable for them. Unlike a 404, configured: false means the feature exists but needs setting up; setup_path says where.

get/settings/public-ingress

Request

  • Base URL: /api (relative, and the document was published on a file host, not at the API’s origin)
  • URL: /api/settings/public-ingress
  • Auth: HTTP bearer

Response

Effective public ingress URL and its reachability

configuredboolean required

false when Temps can tell from its own configuration that a third party cannot reach effective_url. true is not a guarantee: a firewall, VPN or identity-aware proxy in front of the host is invisible from here.

effective_urlstring required

Base URL third parties are given, with no trailing slash. Callback paths (/api/webhook/git/..., /api/emails/...) are appended to it.

reasonstring nullable

Why callbacks will not arrive, when configured is false.

setup_pathstring nullable

Console path that fixes it, when configured is false.

source'explicit' | 'external_url_fallback' required

Where the effective ingress URL came from.

Example response

{
  "effective_url": "https://hooks.example.com",
  "setup_path": "/settings#public-ingress"
}

Changes