Retrieve Orders

Applies to: Orders API | Catalog API | Payments API

Learn how to retrieve orders, catalog attributes, and payments made on an order.

Link to section

Overview

Learn how to use the RetrieveOrder and BatchRetrieveOrders endpoints to retrieve one or more orders. For an order line item that is a catalog item, you learn how to use the Catalog API to access additional catalog attributes.

Link to section

Retrieve one or more orders

You can retrieve a single order or a set of orders using their IDs and the following endpoints. These endpoints return orders regardless of how or when they entered the Square ecosystem (Square Point of Sale, invoices, or the Orders API).

  • Use the RetrieveOrder endpoint to retrieve an order. You only provide an order ID in the request. The endpoint returns the order regardless of the business location where the order was created.

    Retrieve order

  • Use the BatchRetrieveOrders endpoint to retrieve a set of orders (within the scope of the current authorization's merchant ID). In the request, you provide a list of order IDs and an optional business location ID.

    • Location ID is specified - The endpoint returns only the orders in the specified list that are associated with the location.
    • Location ID isn't specified - The endpoint returns all orders specified in the list.

    Batch retrieve orders

Link to section

Retrieve catalog attributes of an order line item

When you create an order, a line item in the order can be a catalog item or an ad hoc item (see Create line items). For a catalog item, the resulting Order object stores the catalog_object_id and catalog_version of the item. You can use this information to access other catalog attributes using the Catalog API (RetrieveCatalogObject endpoint).

For illustration, sku and category_name information of the line item are retrieved. These attributes are part of CatalogObject as follows:

  • sku is now part of a CatalogObject of the ITEM_VARIATION type.
  • category_name now appears as the name field of the CatalogObject of the CATEGORY type.

You can access these CatalogObjects using the RetrieveCatalogObject endpoint (Catalog API) using the following steps:

  1. Make sure you have the catalog_object_id and catalog_version of the line item from your Order object.

  2. Call RetrieveCatalogObject by providing:

    • catalog_object_id as the object_id path parameter value.
    • catalog_version as the query parameter value. If the catalog_version isn't specified, the latest version is assumed.

    Retrieve catalog object

    In response, you get a Catalog object of the ITEM type. The following is an example response. The item_variation_data provides the sku.

    Note that the Catalog object in the response also provides the category_id of the object. You can use it to access the category name of the line item in the next RetrieveCatalogObject call.

  3. Call RetrieveCatalogObject by providing:

    • category_id as the object_id path parameter value (a category is also a Catalog object). Therefore, you specify the category ID as the ID of the Catalog object to retrieve.
    • catalog_version as the query parameter value.

    An example is shown:

    Retrieve catalog object

    In response, you get a Catalog object of the CATEGORY type. The following is an example response. The category_data provides the name of the category of your line item in the order.

    { "object": { "type": "CATEGORY", "id": "WBV5YL4R3DCHXVDFDQ22KPVU", "updated_at": "2021-07-12T19:02:57.355Z", "version": 1626116577355, "is_deleted": false, "present_at_all_locations": true, "category_data": { "name": "Burgers" } } }
Link to section

Retrieve the payments made on an order

When an order is paid, an order.tenders list is populated with a Tender object that provides details about the payment and refers to the Payment object that records the actual payment.

The following example shows the tenders field in an order with a single payment of $1.19. It was captured with a credit card. The details of the capture are recorded in a Payment whose ID is DXjUoKXdD1WPl19Gq52e3BQr4cMZY

To get the payment, call the GetPayment endpoint using the payment_id value from the tender object.

Get payment

Among the properties of a Payment object, you can find relevant payment information, such as the following:

  • Payment card details - For example, the time when the payment was authorized and then captured. If delayed capture is enabled for the payment, you can see the gap between authorization and capture. For a food and beverage business, this lets you know whether a server is closing tickets in a timely manner.
  • TeamMember - Who took the payment. This is usually the team member who was using the hardware that read the buyer's payment card to create the payment.
  • Card reader details - The device_details about the hardware (such as Square Terminal, Square Register, or a seller's mobile device) that read the payment card and created the payment.
  • Application details - Lets you know whether your application took the payment. The application ID in this sub-object should be compared with the application ID for the application you created in the Developer Console.
  • Customer - The payment.customer_id value is used to retrieve details about the buyer who paid for the order. This is usually the same person.

The response carries the Payment object. In the following example, the payment was taken on a Square Point of Sale that the seller named "Counter Terminal 1".

Link to section

See also