Sign in
webhook

Verify an Eli Lilly member and open a link session

Called server-to-server by the signup application after the member accepts the consent bullets and enters their email. Retrieves the member's profile from Eli Lilly using the correlation ID, verifies the submitted email matches it, and returns an opaque link-session token plus prefill fields. clinic_id names which Eli Lilly environment the member came from. Their dev, qa and staging gateways run in parallel and each is provisioned as its own clinic under its own hospital, so the clinic is what resolves the gateway to call. Omitting it falls back to the configured clinic. Returns 422 when the emails differ; the member-facing wording lives in the signup application.

post/webhooks/eli-lilly/link/profile

Request body

clinic_idinteger nullable

Which Eli Lilly environment this link belongs to, named by the clinic the member will join. Eli Lilly run several gateways in parallel (dev, qa, staging) and each is provisioned as its own clinic under its own hospital, so the clinic resolves the gateway to call. Optional: when omitted the configured ELI_LILLY_CLINIC_ID is used, which keeps existing callers working. The link session records the resolved programme, so /link/complete does not repeat it.

correlation_idstring required

Correlation ID issued by Eli Lilly, held server-side by signup

emailstring required

Email the member typed; verified against the Eli Lilly profile

Example request

{
  "consent": {
    "items": [
      {
        "document_key": "eli_lilly_terms_of_service",
        "document_version": "2026-07-01"
      }
    ],
    "locale": "en"
  }
}

Response

Member verified; link session opened

is_existing_memberboolean required

True when this email already has an RxFood account, so signup can show the existing-member confirmation rather than the new-account one

link_session_tokenstring required

Opaque handle to the server-side link session

Changes

No recorded changes to this endpoint across all 1 revision of this API.