NOTE: Place this file inside your Magento pub/ directory to avoid CORS restrictions.

Configuration

To have a logged in customer when using GraphQL, you will have to get the customer token, and then using that token as a Bearer token for the Authorization parameter of each following request. The request will look like this:

After you get the token, you need to create a quote for the customer. With the following mutation you will create a quote if the user does not have a quote, or link a previously existing quote for the user if he created one.

Get Stripe Configurations show

This will return configurations like API keys, API version and button configs from the admin. The location parameter can have the values 'product', 'cart' or 'minicart'.

Get ECE Params show

This endpoint will return a resolve payload, which will be used in the resolve function for add to cart event, and also an element options component, which are cosmetic settings for the modal which will appear.

The parameters are the location from which the ECE is being initialized and the product ID, if it is initialized from a product page.

Add Product To Cart show

The parameters for the request are the following:

product: the ID of the product added
item: the ID of the product added
qty: the quantity you want to add to the basket
If the product is configurable super_attribute: an object containing key - value pairs of the configurable options ID and value or separate {...super_attribute[ID]: value...} row.
If the product is customizable options: formed in the same way as the super_attribute for configurable products
If the product is bundled bundle_option and bundle_option_qty: formed in the same way as for the previous product types

This is how the request components can be formatted. They will be kept in a JSON format and then added to the mutation, because based on the product type that you want to add, the structure can become more complex.

{
                "product": "PRODUCT_ID",
                "item": "PRODUCT_ID",
                "qty": 1

// Uncomment your preference and add the ID - value pairs for the options if you have other types of products

// 1st alternative for configurable products
                // "super_attribute": {
                //     "ID1": value1,
                //     "ID2": value2
                // },
                // 2nd alternative configurable products
                // "super_attribute[ID1]": value1,
                // "super_attribute[ID2]": value2,

// 1st alternative for customizable products
                // "options": {
                //     "ID1": value,
                //     "ID2": value2
                // },
                // 2nd alternative for customizable products
                // "options[ID1]": value1,
                // "options[ID2]": value2

// Options for the Bundle products
                // "bundle_option[ID1]": "value1",
                // "bundle_option[ID2]": "value2",
                // "bundle_option[ID3]": "value3",
                // "bundle_option[ID4]": "value1",
                // "bundle_option_qty[ID1]": "value",
                // "bundle_option_qty[ID2]": "value",
                // "bundle_option_qty[ID3]": "value",
                // "bundle_option_qty[ID4]": "value"
            }

After selecting the product and other options if necessary, they will be passed to the mutation as its' parameter.

Change the shipping address show

The newAddress parameter is taken from the event data

The result of the endpoint call will be used for resolving the processed event, which updates the totals on the ECE.

Change the shipping rate show

The address parameter needs to be the latest address processed in the 'address changed' so it's recommended the address be saved when it is handled. You will have this address from the init process for the ECE, either from when you add the address manually or have one already saved in your selected payment method.

The shipping method parameter is also taken from the processed event.