Org Web Adapter

hungryroot/jira/be_6792_update_discover_home_endpoint_to_return_contract_domain_in_pre_prod_envs.org

ID
f1f24fb4-40c7-44c1-b774-f176600ccbed

BE-6792 Update discover home endpoint to return contract domain in pre prod envs

- source :: https://hungryroot.atlassian.net/browse/BE-6792

- tags :: Hungryroot API Project

- epic :: EP-411 Eng Parking Lot

- sprint :: HR BE Sprint 101 HR BE Sprint 102

- status :: Status - Complete

- pull :: https://github.com/hungryroot/hungryroot/pull/12973

Tasks

DONE Review the implementation used to fix deep link URLS

workchorebe6792ep411hungryrootapisprint101
ID
3a8e0f17-c58a-0d50-c126-12838e3a2d7e

DONE Apply env-aware deep link formatting to logic for Disovery Home endpoint

workchorebe6792ep411hungryrootapisprint101
ID
abf2d561-70af-94cf-c232-f95efa2e2b10

DONE Address PR issues

workhungryrootapiep411be6792choresprint101
ID
816e755c-d695-3a81-a366-6d4ed1017986

DONE Fix broken tests

workhungryrootapiep411be6792choresprint101tests
ID
37311766-9b26-868b-1e2c-450d44ee7a02

DONE Test on Staging

workhungryrootprojectqabe6792ep411sprint102
ID
b8f9aaea-6ea4-03a2-5504-152866b65c19

Description

From Olex and Slack -

https://hungryroot.slack.com/archives/C0931FP8PQA/p1765208704399599

Also see linked ticket for historical knowledge.

A request from Olex (Mobile) indicates that the v2 Discovery Home Collections

endpoint on staging is still returning production-formatted deep link URLs:

https://api.staging.hungryroot.com/api/v2/discovery_home/customers/2588155/collections/?smartcart=0

We previously addressed this issue for Featured Collections, ensuring deep link

URLs correctly reflected the current environment (staging, prod, etc.). The same

fix now needs to be applied to this endpoint.

A software engineer should:

Review the implementation used to fix deep link URLs for the Featured

Collections endpoint.

Apply the same environment-aware deep link formatting logic to the v2 Discovery

Home Collections endpoint.

Confirm that all deep link URLs returned in the response reflect the proper

environment (staging, prod, QA, etc.).

Add or update automated tests to validate deep link correctness across

environments.

Coordinate with Olex and the mobile team to validate behavior on staging once

updated.

Document any shared helper or logic consolidation if applicable.

This ensures consistent and correct deep link behavior across endpoints used by

the mobile clients.