GET
/
api
/
v1
/
locations
/
{locationId}
/
redirect
curl -X GET https://api.cravejs.com/api/v1/locations/687336d833c0e05514856061/redirect \
  -H "X-API-Key: YOUR_API_KEY" \
  -L -w "%{http_code} %{url_effective}" \
  --max-redirs 0

HTTP/2 302 Found
Location: https://storefront.example.com/location/downtown-pizza

Found. Redirecting to https://storefront.example.com/location/downtown-pizza

​
Path Parameters

​
locationId
string
required
The unique identifier for the restaurant location

​
Headers

​
X-API-Key
string
required
Storefront API key for authentication
curl -X GET https://api.cravejs.com/api/v1/locations/687336d833c0e05514856061/redirect \
  -H "X-API-Key: YOUR_API_KEY" \
  -L -w "%{http_code} %{url_effective}" \
  --max-redirs 0

HTTP/2 302 Found
Location: https://storefront.example.com/location/downtown-pizza

Found. Redirecting to https://storefront.example.com/location/downtown-pizza
This endpoint returns an HTTP 302 redirect response rather than JSON data. When following redirects is enabled in your HTTP client, it will automatically navigate to the storefront URL. The redirect URL will point to the location-specific ordering interface.Important for API Testing: When testing this endpoint in the playground or with API clients, ensure that automatic redirect following is disabled to see the actual 302 response with the Location header. Otherwise, you’ll receive the HTML content of the destination page.

Authorizations

​
X-API-Key
string
header
required

Path Parameters

​
locationId
string
required

The unique identifier for the restaurant location

Response

302
text/plain

Found. Redirecting to the storefront URL for the location.

The response is of type string.

Example:

"Found. Redirecting to https://storefront.example.com/location/downtown-pizza"