Generated PR for Release: 11.0.0.20210513

Author: autobot

.github/workflows/maven.yml

@@ -0,0 +1,28 @@
+# This workflow will build a Java project with Maven
+# For more information see: https://help.github.com/actions/language-and-framework-guides/building-and-testing-java-with-maven
+
+name: Java CI with Maven
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+    branches: [master]
+
+jobs:
+  build:
+    env:
+      SQUARE_ENVIRONMENT: sandbox
+      SQUARE_ACCESS_TOKEN: ${{ secrets.SQUARE_SANDBOX_TOKEN }}
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up JDK 8
+        uses: actions/setup-java@v2
+        with:
+          java-version: "8"
+          distribution: "adopt"
+      - name: Build with Maven
+        run: mvn test -B

CHANGELOG.md

@@ -1,5 +1,39 @@
 # Change Log
 
+## Version 11.0.0.20210513 (2021-05-13)
+## New API releases
+
+* **Sites API.** The [Sites API](https://developer.squareup.com/reference/square_2021-05-13/sites-api) lets you retrieve basic details about the Square Online sites that belong to a Square seller. For more information, see [Sites API Overview.](https://developer.squareup.com/docs/sites-api/overview)
+
+
+* **Snippets API.** The [Snippets API](https://developer.squareup.com/reference/square_2021-05-13/snippets-api) lets you manage snippets that provide custom functionality on Square Online sites. A snippet is a script that is injected into all pages on a site, except for checkout pages. For more information, see [Snippets API Overview.](https://developer.squareup.com/docs/snippets-api/overview)
+
+The Sites API and Snippets API are publicly available to all developers as part of an early access program (EAP). For more information, see [Early access program for Square Online APIs.](https://developer.squareup.com/docs/online-api#early-access-program-for-square-online-apis)
+
+## API updates
+
+* **Payments API.**
+  * [CreatePayment.](https://developer.squareup.com/reference/square_2021-05-13/payments-api/create-payment) The endpoint now supports ACH bank transfer payments. For more information, see [ACH Payment](https://developer.squareup.com/docs/payments-api/take-payments/ach-payments).
+
+* **Loyalty API:**
+  * The [Loyalty API](https://developer.squareup.com/docs/loyalty-api/overview) has moved to the [general availability](https://developer.squareup.com/docs/build-basics/api-lifecycle#general-availability) (GA) state.
+  
+  * The [ListLoyaltyPrograms](https://developer.squareup.com/reference/square_2021-05-13/loyalty-api/list-loyalty-programs) endpoint is deprecated and replaced by the [RetrieveLoyaltyProgram](https://developer.squareup.com/reference/square_2021-05-13/loyalty-api/retrieve-loyalty-program) endpoint when used with the `main` keyword.
+  
+  * [LoyaltyAccount](https://developer.squareup.com/reference/square_2021-05-13/objects/LoyaltyAccount)  object. The `mappings` field is retired and replaced by `mapping`. 
+
+  * [LoyaltyAccountMapping](https://developer.squareup.com/reference/square_2021-05-13/objects/LoyaltyAccountMapping) object. The `type` and `value` fields are retired and replaced by `phone_number`.  
+    
+    Starting in Square version 2021-05-13: 
+    * `mappings` is not accepted in `CreateLoyaltyAccount` requests or returned in responses.  
+    * `type` and `value` are not accepted in `CreateLoyaltyAccount` or `SearchLoyaltyAccounts` requests or returned in responses.
+    
+    For more information, see [Migration notes.](https://developer.squareup.com/docs/loyalty-api/overview#migration-notes)
+  
+## Documentation updates
+* **Getting Started** Added step that shows how to use the API Logs to examine a transaction. 
+
+
 ## Version 10.0.0.20210421 (2021-04-21)
 ## New API releases
 

README.md

@@ -33,7 +33,7 @@ Install the client dynamically by adding a dependency to the POM for your projec
 <dependency>
     <groupId>com.squareup</groupId>
     <artifactId>square</artifactId>
-    <version>10.0.0.20210421</version>
+    <version>11.0.0.20210513</version>
 </dependency>
 ```
 
@@ -42,7 +42,7 @@ Install the client dynamically by adding a dependency to the POM for your projec
 Install the client by adding the following dependency to the build file for your project:
 
 ```
-implementation "com.squareup:square:10.0.0.20210421"
+implementation "com.squareup:square:11.0.0.20210513"
 ```
 
 ## API documentation
@@ -93,9 +93,13 @@ implementation "com.squareup:square:10.0.0.20210421"
 ### Financials
 * [Bank Accounts]
 
+### Online
+* [Sites]
+* [Snippets]
+
 ### Authorization APIs
 * [Mobile Authorization]
-* [O Auth]
+* [OAuth]
 
 ### Deprecated APIs
 * [V1 Employees]
@@ -337,9 +341,11 @@ You can also use the Square API to create applications or services that work wit
 [Refunds]: doc/api/refunds.md
 [Subscriptions]: doc/api/subscriptions.md
 [Mobile Authorization]: doc/api/mobile-authorization.md
-[O Auth]: doc/api/o-auth.md
+[OAuth]: doc/api/o-auth.md
 [V1 Employees]: doc/api/v1-employees.md
 [V1 Transactions]: doc/api/v1-transactions.md
 [V1 Items]: doc/api/v1-items.md
 [Team]: doc/api/team.md
 [Transactions]: doc/api/transactions.md
+[Sites]: doc/api/sites.md
+[Snippets]: doc/api/snippets.md

doc/api/catalog.md

@@ -548,7 +548,7 @@ CompletableFuture<ListCatalogResponse> listCatalogAsync(
 
 | Parameter | Type | Tags | Description |
 |  --- | --- | --- | --- |
-| `cursor` | `String` | Query, Optional | The pagination cursor returned in the previous response. Leave unset for an initial request.<br>See [Pagination](https://developer.squareup.com/docs/basics/api101/pagination) for more information. |
+| `cursor` | `String` | Query, Optional | The pagination cursor returned in the previous response. Leave unset for an initial request.<br>The page size is currently set to be 100.<br>See [Pagination](https://developer.squareup.com/docs/basics/api101/pagination) for more information. |
 | `types` | `String` | Query, Optional | An optional case-insensitive, comma-separated list of object types to retrieve, for example<br>`ITEM,ITEM_VARIATION,CATEGORY,IMAGE`.<br><br>The legal values are taken from the CatalogObjectType enum:<br>`ITEM`, `ITEM_VARIATION`, `CATEGORY`, `DISCOUNT`, `TAX`,<br>`MODIFIER`, `MODIFIER_LIST`, or `IMAGE`. |
 | `catalogVersion` | `Long` | Query, Optional | The specific version of the catalog objects to be included in the response.<br>This allows you to retrieve historical<br>versions of objects. The specified version value is matched against<br>the [CatalogObject](/doc/models/catalog-object.md)s' `version` attribute. |
 

doc/api/inventory.md

@@ -130,8 +130,8 @@ InventoryChange bodyChanges0 = new InventoryChange.Builder()
     .build();
 bodyChanges.add(bodyChanges0);
 
-BatchChangeInventoryRequest body = new BatchChangeInventoryRequest.Builder()
-    .idempotencyKey("8fc6a5b0-9fe8-4b46-b46b-2ef95793abbe")
+BatchChangeInventoryRequest body = new BatchChangeInventoryRequest.Builder(
+        "8fc6a5b0-9fe8-4b46-b46b-2ef95793abbe")
     .changes(bodyChanges)
     .ignoreUnchangedCounts(true)
     .build();

doc/api/loyalty.md

@@ -28,7 +28,7 @@ LoyaltyApi loyaltyApi = client.getLoyaltyApi();
 
 # Create Loyalty Account
 
-Creates a loyalty account. To create a loyalty account, you must provide the `program_id` and either the `mapping` field (preferred) or the `mappings` field.
+Creates a loyalty account. To create a loyalty account, you must provide the `program_id` and a `mapping` with the `phone_number` of the buyer.
 
 ```java
 CompletableFuture<CreateLoyaltyAccountResponse> createLoyaltyAccountAsync(
@@ -48,31 +48,18 @@ CompletableFuture<CreateLoyaltyAccountResponse> createLoyaltyAccountAsync(
 ## Example Usage
 
 ```java
-List<LoyaltyAccountMapping> bodyLoyaltyAccountMappings = new LinkedList<>();
-
-LoyaltyAccountMapping bodyLoyaltyAccountMappings0 = new LoyaltyAccountMapping.Builder()
-    .id("id0")
-    .type("PHONE")
-    .value("value2")
-    .createdAt("created_at8")
-    .phoneNumber("phone_number8")
-    .build();
-bodyLoyaltyAccountMappings.add(bodyLoyaltyAccountMappings0);
-
 LoyaltyAccountMapping bodyLoyaltyAccountMapping = new LoyaltyAccountMapping.Builder()
     .id("id6")
-    .type("PHONE")
-    .value("value8")
     .createdAt("created_at4")
     .phoneNumber("+14155551234")
     .build();
 LoyaltyAccount bodyLoyaltyAccount = new LoyaltyAccount.Builder(
         "d619f755-2d17-41f3-990d-c04ecedd64dd")
     .id("id2")
-    .mappings(bodyLoyaltyAccountMappings)
     .balance(14)
     .lifetimePoints(38)
     .customerId("customer_id0")
+    .enrolledAt("enrolled_at2")
     .mapping(bodyLoyaltyAccountMapping)
     .build();
 CreateLoyaltyAccountRequest body = new CreateLoyaltyAccountRequest.Builder(
@@ -119,8 +106,6 @@ List<LoyaltyAccountMapping> bodyQueryMappings = new LinkedList<>();
 
 LoyaltyAccountMapping bodyQueryMappings0 = new LoyaltyAccountMapping.Builder()
     .id("id4")
-    .type("PHONE")
-    .value("value6")
     .createdAt("created_at8")
     .phoneNumber("+14155551234")
     .build();
@@ -366,8 +351,12 @@ loyaltyApi.searchLoyaltyEventsAsync(body).thenAccept(result -> {
 
 # List Loyalty Programs
 
+**This endpoint is deprecated. **
+
 Returns a list of loyalty programs in the seller's account.
-Currently, a seller can only have one loyalty program.
+Loyalty programs define how buyers can earn points and redeem points for rewards. Square sellers can have only one loyalty program, which is created and managed from the Seller Dashboard. For more information, see [Loyalty Program Overview](https://developer.squareup.com/docs/loyalty/overview).
+
+Replaced with [RetrieveLoyaltyProgram](/doc/api/loyalty.md#retrieve-loyalty-program) when used with the keyword `main`.
 
 ```java
 CompletableFuture<ListLoyaltyProgramsResponse> listLoyaltyProgramsAsync()

doc/api/orders.md

@@ -21,12 +21,11 @@ OrdersApi ordersApi = client.getOrdersApi();
 
 # Create Order
 
-Creates a new [Order](/doc/models/order.md) which can include information on products for
+Creates a new [order](/doc/models/order.md) that can include information about products for
 purchase and settings to apply to the purchase.
 
-To pay for a created order, please refer to the
-[Pay for Orders](https://developer.squareup.com/docs/orders-api/pay-for-orders)
-guide.
+To pay for a created order, see
+[Pay for Orders](https://developer.squareup.com/docs/orders-api/pay-for-orders).
 
 You can modify open orders using the [UpdateOrder](/doc/api/orders.md#update-order) endpoint.
 
@@ -217,9 +216,9 @@ ordersApi.createOrderAsync(body).thenAccept(result -> {
 
 # Batch Retrieve Orders
 
-Retrieves a set of [Order](/doc/models/order.md)s by their IDs.
+Retrieves a set of [orders](/doc/models/order.md) by their IDs.
 
-If a given Order ID does not exist, the ID is ignored instead of generating an error.
+If a given order ID does not exist, the ID is ignored instead of generating an error.
 
 ```java
 CompletableFuture<BatchRetrieveOrdersResponse> batchRetrieveOrdersAsync(
@@ -402,19 +401,19 @@ ordersApi.calculateOrderAsync(body).thenAccept(result -> {
 
 Search all orders for one or more locations. Orders include all sales,
 returns, and exchanges regardless of how or when they entered the Square
-Ecosystem (e.g. Point of Sale, Invoices, Connect APIs, etc).
+ecosystem (such as Point of Sale, Invoices, and Connect APIs).
 
-SearchOrders requests need to specify which locations to search and define a
-[`SearchOrdersQuery`](/doc/models/search-orders-query.md) object which controls
-how to sort or filter the results. Your SearchOrdersQuery can:
+`SearchOrders` requests need to specify which locations to search and define a
+[SearchOrdersQuery](/doc/models/search-orders-query.md) object that controls
+how to sort or filter the results. Your `SearchOrdersQuery` can:
 
 Set filter criteria.
-Set sort order.
-Determine whether to return results as complete Order objects, or as
+Set the sort order.
+Determine whether to return results as complete `Order` objects or as
 [OrderEntry](/doc/models/order-entry.md) objects.
 
 Note that details for orders processed with Square Point of Sale while in
-offline mode may not be transmitted to Square for up to 72 hours. Offline
+offline mode might not be transmitted to Square for up to 72 hours. Offline
 orders have a `created_at` value that reflects the time the order was created,
 not the time it was subsequently transmitted to Square.
 
@@ -548,21 +547,21 @@ ordersApi.retrieveOrderAsync(orderId).thenAccept(result -> {
 
 # Update Order
 
-Updates an open [Order](/doc/models/order.md) by adding, replacing, or deleting
+Updates an open [order](/doc/models/order.md) by adding, replacing, or deleting
 fields. Orders with a `COMPLETED` or `CANCELED` state cannot be updated.
 
-An UpdateOrder request requires the following:
+An `UpdateOrder` request requires the following:
 
 - The `order_id` in the endpoint path, identifying the order to update.
 - The latest `version` of the order to update.
 - The [sparse order](https://developer.squareup.com/docs/orders-api/manage-orders#sparse-order-objects)
-  containing only the fields to update and the version the update is
-  being applied to.
+  containing only the fields to update and the version to which the update is
+  being applied.
 - If deleting fields, the [dot notation paths](https://developer.squareup.com/docs/orders-api/manage-orders#on-dot-notation)
-  identifying fields to clear.
+  identifying the fields to clear.
 
-To pay for an order, please refer to the
-[Pay for Orders](https://developer.squareup.com/docs/orders-api/pay-for-orders) guide.
+To pay for an order, see
+[Pay for Orders](https://developer.squareup.com/docs/orders-api/pay-for-orders).
 
 ```java
 CompletableFuture<UpdateOrderResponse> updateOrderAsync(
@@ -668,20 +667,20 @@ ordersApi.updateOrderAsync(orderId, body).thenAccept(result -> {
 
 # Pay Order
 
-Pay for an [order](/doc/models/order.md) using one or more approved [payments](/doc/models/payment.md),
+Pay for an [order](/doc/models/order.md) using one or more approved [payments](/doc/models/payment.md)
 or settle an order with a total of `0`.
 
 The total of the `payment_ids` listed in the request must be equal to the order
 total. Orders with a total amount of `0` can be marked as paid by specifying an empty
 array of `payment_ids` in the request.
 
-To be used with PayOrder, a payment must:
+To be used with `PayOrder`, a payment must:
 
 - Reference the order by specifying the `order_id` when [creating the payment](/doc/api/payments.md#create-payment).
   Any approved payments that reference the same `order_id` not specified in the
-  `payment_ids` will be canceled.
+  `payment_ids` is canceled.
 - Be approved with [delayed capture](https://developer.squareup.com/docs/payments-api/take-payments#delayed-capture).
-  Using a delayed capture payment with PayOrder will complete the approved payment.
+  Using a delayed capture payment with `PayOrder` completes the approved payment.
 
 ```java
 CompletableFuture<PayOrderResponse> payOrderAsync(

doc/api/sites.md

@@ -0,0 +1,36 @@
+# Sites
+
+```java
+SitesApi sitesApi = client.getSitesApi();
+```
+
+## Class Name
+
+`SitesApi`
+
+
+# List Sites
+
+Lists the Square Online sites that belong to a seller.
+
+__Note:__ Square Online APIs are publicly available as part of an early access program. For more information, see [Early access program for Square Online APIs](https://developer.squareup.com/docs/online-api#early-access-program-for-square-online-apis).
+
+```java
+CompletableFuture<ListSitesResponse> listSitesAsync()
+```
+
+## Response Type
+
+[`ListSitesResponse`](/doc/models/list-sites-response.md)
+
+## Example Usage
+
+```java
+sitesApi.listSitesAsync().thenAccept(result -> {
+    // TODO success callback handler
+}).exceptionally(exception -> {
+    // TODO failure callback handler
+    return null;
+});
+```
+