App proxies take requests to Shopify links, and redirect them to external links. This allows you to fetch and display data on a merchant's store from an external source.
You don't need to set up app proxies before publishing an app. If you add an app proxy to an app after you've published it, then existing installations of the app are updated automatically. You can add or update a proxy URL at any time in the Partner Dashboard, and you don't need to update the URL in individual online stores.
In the App proxy section, select a prefix from the Subpath prefix drop-down list.
Enter a sub path in the Subpath field:
These settings determine which HTTP requests to Shopify are proxied to the proxy URL entered in the next step. For example, if the sub path prefix is apps, and the sub path is store-pickup, then any path in your online store after https://admin.shopify.com/store/{shop}/apps/{app-name} will be proxied to the provided proxy URL.
Enter the URL of your proxy server in the Proxy URL field. This is the URL that will be proxied from the path that you entered in the previous step.
In this example, https://admin.shopify.com/store/{shop}/apps/my-app-proxy/app_path forwards to the proxy URL at https://my-app-proxy.com/app_proxy/app_path. Subsequent child routes included in the request are forwarded as well, so https://admin.shopify.com/store/{shop}/apps/my-app-proxy/child-route is forwarded to https://my-app-proxy.com/app_proxy/child-route.
Merchants can change the sub path or sub path prefix of app proxies. Merchants change the sub path prefix by toggling between a set of values provided by Shopify (/apps,/a,/community, or /tools). The combination of sub path prefix and sub path defines where the app proxy is accessed from a merchant's shop. Merchants can change this information to get a friendlier URL that appears to originate from the merchant's domain. The sub path doesn't affect the location of the proxy URL that you provide in the Proxy URL field.
The following examples show an app proxy definition:
proxy URL: https://proxy-domain.com/proxy
client IP: 123.123.123.123
shared secret: hush
When the following HTTP request is sent from the client, Shopify forwards the request using the specified proxy URL:
The forwarded request looks like the following:
The forwarded request adds the following parameters:
shop: The myshopify.com domain for the shop.
path_prefix: The proxy sub-path prefix at which the shop was accessed. In this case, it's /apps/awesome_reviews, which was replaced in the forwarded request URL with the proxy application's Proxy URL.
timestamp: The time in seconds since midnight of January 1, 1970 UTC.
signature: A hexadecimal encoded SHA-256HMAC of the other parameters, split on the "&" character, that is used to verify that the request was sent by Shopify. The signature is unencoded, sorted, concatenated and uses the application's shared secret as the HMAC key.
logged_in_customer_id: The ID of the logged-in customer. If no customer is logged in, then this value is empty.
Both the request method and request body are forwarded, meaning that content from the form submission and AJAX requests can be used in the proxy application. If this is the case, then the URL still contains the query parameters added by the proxy, such as shop, logged_in_customer_id, path_prefix, timestamp, and signature, even when the body also contains URL encoded parameters.
To verify that the request came from Shopify, you need to compute the HMAC digest according to the SHA-256 hash function and compare it to the value in the signature property. If the values match, then the request was sent from Shopify.
The following examples show how to calculate the digital signature when a customer is logged in and the logged_in_customer_id parameter is populated, and when no customer is logged in and the logged_in_customer_id is empty.
App proxies support Liquid, Shopify's template language. An app proxy response that contains Liquid will be rendered with store data into HTML like it was part of the store's theme.
If the HTTP response from the proxy URL has Content-Type: application/liquid set in its headers, then Shopify renders any Liquid code in the request body in the context of the shop using the shop's theme. Otherwise, the response is returned directly to the client. Also, any 30x redirects are followed.
