Support

Where to get unblocked, clarify a spec, or escalate an incident. Channels are split by request type so we can route quickly.

Production incident

• Symptoms: API 5xx · slow responses · auth failures · missing data · telemetry not landing.
• Channel: LinkOStar ops Slack (#linkostar-ops). On-call phone for severity-1.
• What to send:
  • Time window in UTC
  • Failing endpoint and HTTP method
  • traceId from the response body (if present)
  • Tenant UUID (mask partially if it's sensitive)
  • Your supplier identity (don't send the API key itself)
• Response SLA: production incidents target a first response within 1 hour.

Integration questions / spec clarifications

• Symptoms: doc gaps · ambiguous behaviour · new endpoint request · best-practice check.
• Channel: GitHub Issue on the relevant repo, or Slack (#linkostar-dev).
• Response SLA: two business days.

Tracking breaking changes

• Check the Changelog page periodically.
• Register a supplier contact (Slack channel or email DL) with LinkOStar ops for proactive notices.
• Wire an OpenAPI spec diff into your CI — breaking changes break your client build before they break production.

Security

• Suspected key leak, auth bypass, or data exposure: do not use a public channel.
• Email: security@linkostar.sandevaux.com (placeholder — your actual contact is delivered with your credential bundle).
• If you have a PoC, attach a summary, not the dataset itself.

What you should have on file already

The credential handover sent to each supplier includes:

• Your supplier_uuid / tenant_uuid
• X-API-Key (production, plus staging if applicable)
• Operational contact (Slack / email)
• On-call escalation procedure

None of this lives on this public site — check your secret manager.

Feedback on these docs

Spotted a confusing phrase, a stale example, or a missing endpoint? PRs to linkostar-web/src/app/[locale]/(public)/docs/ are welcome. Small fixes are fine.