Journeys Receipts

The Devvit Journeys API responses include a receipt: a small feedback object that tells you what happened to a telemetry event.

This is not end-user messaging. It's implementation feedback so you can tell whether a Journey event was recorded, skipped, rejected, rate limited, or could not be confirmed.

Viewing receipts

Every Journey telemetry call now returns a receipt.

startJourney() returns:

{
  journeyId: string,
  receipt: {
    status: string,
    message: string
  }
}

Other Journey calls return:

{
  receipt: {
    status: string,
    message: string
  }
}

Covered calls:

• Start Journey
• Journey Progress
• Journey Interaction
• End Journey
• App Ready

Receipt fields

status is the machine-readable outcome. Use this for branching, tests, or tooling.

message is the human-readable diagnostic. You can log it or display it during implementation/debugging.

Upgrade note for existing devs

startJourney() changed from returning only the Journey ID information to returning the Journey ID plus a receipt. If you’re upgrading existing code, you may need to update any custom response types, mocks, or destructuring assumptions so they account for the new receipt field.

For example, code that only typed the response as { journeyId: string } should now expect:

{
  journeyId: string,
  receipt: {
    status: string,
    message: string
  }
}

Possible receipt outcomes

Status	Meaning	Current Message
JOURNEY_RECEIPT_VALID	Event was accepted and recorded.	Success: Event was recorded.
JOURNEY_RECEIPT_DENIED_NOT_ALLOWLISTED	Event was valid, but the app is not enabled for Journey telemetry yet.	Denied: Your app is not allowlisted for Journey telemetry yet.
JOURNEY_RECEIPT_DENIED_RATE_LIMITED	Event was valid, but skipped because the app sent too many events.	Denied: Event was rate limited.
JOURNEY_RECEIPT_DENIED_DUPLICATE	Event was valid, but skipped because it was already recorded.	Denied: Event was already recorded.
JOURNEY_RECEIPT_INVALID	Event payload was invalid and was not recorded.	Invalid: Event payload was not recorded.
JOURNEY_RECEIPT_UNSPECIFIED	Recording status could not be confirmed.	Unknown: Telemetry recording status could not be confirmed.

Example:

{
    "journeyId": "f7ece033-0247-407c-aede-8b65c7fd645c",
    "receipt": {
        "status": "JOURNEY_RECEIPT_DENIED_NOT_ALLOWLISTED",
        "message": "Denied: Your app is not allowlisted for Journey telemetry yet."
    }
}

That receipt is an indicator to reach out to the Devvit team for allowlisting. After allowlist, the dev sees:

{
    "journeyId": "f7ece033-0247-407c-aede-8b65c7fd645c",
    "receipt": {
        "status": "JOURNEY_RECEIPT_VALID",
        "message": "Success: Event was recorded."
    }
}

Important notes

A successful API response does not always mean the event was recorded. The receipt is the source of truth for the telemetry outcome.

Denied receipts are still useful: they tell developers the SDK call worked, but the telemetry event was intentionally not ingested.

If the client reuses an already-active Journey, it returns:

Already started: Reusing the active Journey; no new start event was recorded.

This means no new start event was sent because the client already has an active Journey session.