---
title: "Journey Signal"
method: POST
path: "/users/journey-signal"
tags: ["users"]
---

# Journey Signal

`POST /users/journey-signal`

## Request

- Base URL: `https://api.projectindi.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.projectindi.com/users/journey-signal`
- Auth: none declared

Read-only journey resolution - the same `_resolve` as classify, never recorded.

The mobile `af_complete_registration` gate needs the non-direct verdict
synchronously at SIGNED_IN, before the write-once `/classify-journey` has
necessarily run. It reads the authoritative answer here (all three signals -
clinic code, family invite by email, profile match by email) instead of
re-deriving a partial one client-side. The caller fails open, so a 500 just
lets the event fire.

## Request body

- JourneySignalRequest
  - `invite_code` string, nullable

## Response `200`

Successful Response

- JourneySignalResponse
  - `resolved_journey` string, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/projectindi/apis/indi-agent-api-first-principles.md) - [All operations](https://skmtc.dev/projectindi/apis/indi-agent-api-first-principles/llms.txt) - [OpenAPI document](https://skmtc.dev/projectindi/apis/indi-agent-api-first-principles/revisions/25a7813e21fd?raw)