HasEvents

The name of the author of the article.

The blog containing the article.

The text of the article's body, complete with HTML markup.

List of the article's comments.

Count of comments.

The date and time (ISO 8601 format) when the article was created.

A default cursor that returns the single next record, sorted ascending by ID.

The paginated list of events associated with the host subject.

A unique, human-friendly string for the article that's automatically generated from the article's title. The handle is used in the article's URL.

A globally-unique ID.

The image associated with the article.

Whether or not the article is visible.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

The date and time (ISO 8601 format) when the article became or will become visible. Returns null when the article isn't visible.

A summary of the article, which can include HTML markup. The summary is used by the online store theme to display the article on other pages, such as the home page or the main blog page.

A comma-separated list of tags. Tags are additional short descriptors formatted as a string of comma-separated values.

The name of the template an article is using if it's using an alternate template. If an article is using the default article.liquid template, then the value returned is null.

The title of the article.

The published translations associated with the resource.

The date and time (ISO 8601 format) when the article was last updated.

List of the blog's articles.

Count of articles.

Indicates whether readers can post comments to the blog and if comments are moderated or not.

The date and time when the blog was created.

The paginated list of events associated with the host subject.

FeedBurner provider details. Any blogs that aren't already integrated with FeedBurner can't use the service.

A unique, human-friendly string for the blog. If no handle is specified, a handle will be generated automatically from the blog title. The handle is customizable and is used by the Liquid templating language to refer to the blog.

A globally-unique ID.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

A list of tags associated with the 200 most recent blog articles.

The name of the template a blog is using if it's using an alternate template. Returns null if a blog is using the default blog.liquid template.

The title of the blog.

The published translations associated with the resource.

The date and time when the blog was update.

The number of publications that a resource is published to, without feedback errors.

A single-line, text-only description of the collection, stripped of any HTML tags and formatting that were included in the description.

The description of the collection, including any HTML tags and formatting. This content is typically displayed to customers, such as on an online store, depending on the theme.

The paginated list of events associated with the host subject.

Information about the collection that's provided through resource feedback.

A unique string that identifies the collection. If a handle isn't specified when a collection is created, it's automatically generated from the collection's original title, and typically includes words from the title separated by hyphens. For example, a collection that was created with the title Summer Catalog 2022 might have the handle summer-catalog-2022.

If the title is changed, the handle doesn't automatically change.

The handle can be used in themes by the Liquid templating language to refer to the collection, but using the ID is preferred because it never changes.

Whether the collection includes the specified product.

A globally-unique ID.

The image associated with the collection.

The ID of the corresponding resource in the REST Admin API.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

The products that are included in the collection.

The number of products in the collection.

Whether the resource is published to the app's publication. For example, the resource might be published to the app's online store channel.

Whether the resource is published to a specified publication.

The list of resources that are published to a publication.

The number of publications that a resource is published to, without feedback errors.

The list of resources that are either published or staged to be published to a publication.

For a smart (automated) collection, specifies the rules that determine whether a product is included.

If the default SEO fields for page title and description have been modified, contains the modified information.

The order in which the products in the collection are displayed by default in the Shopify admin and in sales channels, such as an online store.

The suffix of the Liquid template being used to show the collection in an online store. For example, if the value is custom, then the collection is using the collection.custom.liquid template. If the value is null, then the collection is using the default collection.liquid template.

The name of the collection. It's displayed in the Shopify admin and is typically displayed in sales channels, such as an online store.

The published translations associated with the resource.

The list of publications that the resource isn't published to.

The date and time (ISO 8601 format) when the collection was last modified.

The article associated with the comment.

The comment’s author.

The content of the comment.

The content of the comment, complete with HTML formatting.

The date and time when the comment was created.

The paginated list of events associated with the host subject.

A globally-unique ID.

The IP address of the commenter.

Whether or not the comment is published.

The date and time when the comment was published.

The status of the comment.

The date and time when the comment was last updated.

The user agent of the commenter.

The list of roles for the company contacts.

The list of contacts in the company.

The number of contacts that belong to the company.

The date and time (ISO 8601 format) at which the company was created in Shopify.

The date and time (ISO 8601 format) at which the company became the customer.

A default cursor that returns the single next record, sorted ascending by ID.

The role proposed by default for a contact at the company.

The list of the company's draft orders.

The paginated list of events associated with the host subject.

A unique externally-supplied ID for the company.

Whether the merchant added a timeline comment to the company.

A globally-unique ID.

The lifetime duration of the company, since it became a customer of the shop. Examples: 2 days, 3 months, 1 year.

The list of locations in the company.

The number of locations that belong to the company.

The main contact for the company.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

The name of the company.

A note about the company.

The list of the company's orders.

The total number of orders placed for this company, across all its locations.

The total amount spent by this company, across all its locations.

The date and time (ISO 8601 format) at which the company was last modified.

The address used as billing address for the location.

The configuration for the buyer's B2B checkout.

The list of catalogs associated with the company location.

The number of catalogs associated with the company location. Limited to a maximum of 10000 by default.

The company that the company location belongs to.

The date and time (ISO 8601 format) at which the company location was created in Shopify.

The location's currency based on the shipping address. If the shipping address is empty, then the value is the shop's primary market.

A default cursor that returns the single next record, sorted ascending by ID.

The list of draft orders for the company location.

The paginated list of events associated with the host subject.

A unique externally-supplied ID for the company location.

Whether the merchant added a timeline comment to the company location.

A globally-unique ID.

Whether the company location is assigned a specific catalog.

The preferred locale of the company location.

The market that includes the location's shipping address. If the shipping address is empty, then the value is the shop's primary market.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

The name of the company location.

A note about the company location.

The list of orders for the company location.

The total number of orders placed for the location.

The phone number of the company location.

The list of roles assigned to the company location.

The address used as shipping address for the location.

The list of staff members assigned to the company location.

The total amount spent by the location.

The date and time (ISO 8601 format) at which the company location was last modified.

A list of addresses associated with the customer.

The addresses associated with the customer.

The total amount that the customer has spent on orders in their lifetime.

Whether the merchant can delete the customer from their store.

A customer can be deleted from a store only if they haven't yet made an order. After a customer makes an order, they can't be deleted from a store.

A list of the customer's company contact profiles.

The date and time when the customer was added to the store.

Whether the customer has opted out of having their data sold.

The default address associated with the customer.

The full name of the customer, based on the values for first_name and last_name. If the first_name and last_name are not available, then this falls back to the customer's email address, and if that is not available, the customer's phone number.

A list of events associated with the customer.

The customer's first name.

A globally-unique ID.

The image associated with the customer.

The customer's last name.

The customer's last order.

The ID of the corresponding resource in the REST Admin API.

The amount of time since the customer was first added to the store.

Example: 'about 12 years'.

The customer's locale.

The market that includes the customer’s default address.

Whether the customer can be merged with another customer.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

A unique identifier for the customer that's used with Multipass login.

A note about the customer.

The number of orders that the customer has made at the store in their lifetime.

A list of the customer's orders.

A list of the customer's payment methods.

Possible subscriber states of a customer defined by their subscription contracts.

The state of the customer's account with the shop.

Please note that this only meaningful when Classic Customer Accounts is active.

The statistics for a given customer.

Returns a list of store credit accounts that belong to the owner resource. A store credit account owner can hold multiple accounts each with a different currency.

A list of the customer's subscription contracts.

A comma separated list of tags that have been added to the customer.

Whether the customer is exempt from being charged taxes on their orders.

The list of tax exemptions applied to the customer.

The date and time when the customer was last updated.

Whether the customer has verified their email address. Defaults to true if the customer is created through the Shopify admin or API.

The number of times that the discount has been used. For example, if a "Buy 3, Get 1 Free" t-shirt discount is automatically applied in 200 transactions, then the discount has been used 200 times. This value is updated asynchronously. As a result, it might be lower than the actual usage count until the asynchronous process is completed.

The discount classes that you can use in combination with Shopify discount types.

The date and time when the discount was created.

The items eligible for the discount and the required quantity of each to receive the discount.

The items in the order that qualify for the discount, their quantities, and the total value of the discount.

The date and time when the discount expires and is no longer available to customers. For discounts without a fixed expiration date, specify null.

The paginated list of events associated with the host subject.

The date and time when the discount becomes active and is available to customers.

The status of the discount that describes its availability, expiration, or pending activation.

A detailed explanation of what the discount is, who can use it, when and where it applies, and any associated rules or limitations.

The discount's name that displays to merchants in the Shopify admin and to customers.

The date and time when the discount was updated.

The maximum number of times that the discount can be applied to an order.

A discount that's applied automatically when an order meets specific criteria. Learn more about automatic discounts.

The paginated list of events associated with the host subject.

A globally-unique ID.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

The underlying code discount object.

The paginated list of events associated with the host subject.

A globally-unique ID.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

A discount that's applied at checkout or on cart.

Discounts can be automatic or code-based.

The paginated list of events associated with the host subject.

A globally-unique ID.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

Whether or not to accept automatic discounts on the draft order during calculation. If false, only discount codes and custom draft order discounts (see appliedDiscount) will be applied. If true, eligible automatic discounts will be applied in addition to discount codes and custom draft order discounts.

Whether discount codes are allowed during checkout of this draft order.

The custom order-level discount applied.

The billing address of the customer.

Whether the billing address matches the shipping address.

The date and time when the draft order was converted to a new order, and had it's status changed to Completed.

The date and time when the draft order was created in Shopify.

The shop currency used for calculation.

The custom information added to the draft order on behalf of the customer.

The customer who will be sent an invoice.

A default cursor that returns the single next record, sorted ascending by ID.

All discount codes applied.

The email address of the customer, which is used to send notifications.

The list of events associated with the draft order.

Whether the merchant has added timeline comments to the draft order.

A globally-unique ID.

The subject defined for the draft invoice email template.

The date and time when the invoice was last emailed to the customer.

The link to the checkout, which is sent to the customer in the invoice email.

The ID of the corresponding resource in the REST Admin API.

The list of the line items in the draft order.

A subtotal of the line items and corresponding discounts, excluding include shipping charges, shipping discounts, taxes, or order discounts.

A custom field, including its namespace and key, that's associated with a Shopify resource for the purposes of adding and storing additional information.

A list of custom fields that a merchant associates with a Shopify resource.

The identifier for the draft order, which is unique within the store. For example, #D1223.

The text from an optional note attached to the draft order.

The order that was created from the draft order.

The associated payment terms for this draft order.

The assigned phone number.

The list of platform discounts applied.

The purchase order number.

The payment currency used for calculation.

The purchasing entity.

Whether the draft order is ready and can be completed. Draft orders might have asynchronous operations that can take time to finish.

The time after which inventory will automatically be restocked.

The shipping address of the customer.

The line item containing the shipping information and costs.

The status of the draft order.

The subtotal, of the line items and their discounts, excluding shipping charges, shipping discounts, and taxes.

The comma separated list of tags associated with the draft order. Updating tags overwrites any existing tags that were previously added to the draft order. To add new tags without overwriting existing tags, use the tagsAdd mutation.

Whether the line item prices include taxes.

Whether the draft order is tax exempt.

The list of of taxes lines charged for each line item and shipping line.

Total discounts.

Total price of line items.

The total price, includes taxes, shipping charges, and discounts.

The sum of individual line item quantities. If the draft order has bundle items, this is the sum containing the quantities of individual items in the bundle.

The total shipping price.

The total tax.

The total weight in grams of the draft order.

Fingerprint of the current cart. In order to have bundles work, the fingerprint must be passed to each request as it was previously returned, unmodified.

The date and time when the draft order was last changed. The format is YYYY-MM-DD HH:mm:ss. For example, 2016-02-05 17:04:01.

Whether the draft order will be visible to the customer on the self-serve portal.

The list of warnings raised while calculating.

A list of additional fees applied to an order, such as duties, import fees, or tax lines.

A list of sales agreements associated with the order, such as contracts defining payment terms, or delivery schedules between merchants and customers.

A list of messages that appear on the Orders page in the Shopify admin. These alerts provide merchants with important information about an order's status or required actions.

The application that created the order. For example, "Online Store", "Point of Sale", or a custom app name. Use this to identify the order source for attribution and fulfillment workflows. Learn more about building apps for orders and fulfillment.

The billing address associated with the payment method selected by the customer for an order. Returns null if no billing address was provided during checkout.

Whether the billing address matches the shipping address. Returns true if both addresses are the same, and false if they're different or if an address is missing.

Details of an order's cancellation, if it has been canceled. This includes the reason, date, and any staff notes.

The date and time in ISO 8601 format when an order was canceled. Returns null if the order hasn't been canceled.

The reason provided for an order cancellation. For example, a merchant might cancel an order if there's insufficient inventory. Returns null if the order hasn't been canceled.

Whether an order can be manually marked as paid. Returns false if the order is already paid, is canceled, has pending Shopify Payments transactions, or has a negative payment amount.

Whether order notifications can be sent to the customer. Returns true if the customer has a valid email address.

Whether an authorized payment for an order can be captured. Returns true if an authorized payment exists that hasn't been fully captured yet. Learn more about capturing payments.

The total discount amount applied at the time the order was created, displayed in both shop and presentment currencies, before returns, refunds, order edits, and cancellations. This field only includes discounts applied to the entire order.

Details about the sales channel that created the order, such as the channel app type and channel name, which helps to track order sources.

The IP address of the customer who placed the order. Useful for fraud detection and geographic analysis.

Whether an order is closed. An order is considered closed if all its line items have been fulfilled or canceled, and all financial transactions are complete.