We have added search functionality to the Connect v2 Customer API.
SearchCustomers
endpoint — retrieves groups of customer profiles based on a related characteristic. For example, retrieving all customers created in the past 24 hours.creation_source
field is now available onCustomer
entities. The creation source exposes the process that created a customer profile. For example, if a customer is created using the API, the creation source will beTHIRD_PARTY
.- Instant Profiles are now exposed in the following endpoints:
RetrieveCustomer
,SearchCustomers
,UpdateCustomer
,DeleteCustomer
.
- Fix SDK request property
adjustment_type
in V1 Adjust Inventory.
We have added sorting functionality to the Connect v2 Customer API, updated the Connect v1 Payments API to include information about surcharges and improvements to the Item data type.
- ListCustomers endpoint — now provides the ability to sort
customers by their creation date using the
sort_field
andsort_order
parameters.
The Payments API now returns information about surcharges applied to payments. The new functionality introduces the following new data types:
- SurchargeMoney datatype — The total of all surcharges applied to the payment.
- Surcharges datatype — A list of all surcharges associated with the payment.
- Surcharge datatype — A surcharge that is applied to the payment. One example of a surcharge is auto-gratuity, which is a fixed-rate surcharge applied to every payment, often based on party size.
We are constantly evaluating new languages to add. In the meantime, if the language you need is not supported, you can use our [Swagger pipeline](<%= articles__client_libraries_path%>#generatingwithswagger) to generate a custom SDK or continue sending JSON to the endpoint URLs directly.
Item will now provide two new properties:
category_id
— indicates if an item can be added to pickup orders from the merchant's online storeavailable_for_pickup
— indicates the item's category (if any).
The Transactions API in Connect v2 now includes payment and refund information from exchanges.
ListTransactions
now includes payment information from sales and exchanges and refund information from returns and exchanges.ListRefunds
now includes refunds that result from exchanges in addition to partial refunds and itemized returns through Square's Point of Sale applications.
The Payments API in Connect v1 now includes payment and refund information from exchanges.
ListPayments
now includes refunds that are generated from exchanges to account for the value of returned goods.ListRefunds
now returns an approximate number of refunds (default: 100, max: 200). The response may contain more results than the prescribed limit when refunds are made simultaneously to multiple tenders in a payment or when refunds are generated from exchanges to account for the value of returned goods.is_exchange
is added toV1Refund
andV1Tender
. Refunds and tenders marked in this way represent the value of returned goods in an exchange, rather than actual money movement.
- Updates user-agent header
BatchRetrieveOrders
will now return uncharged orders.
- For Catalog-backed line items, setting
CreateOrderRequestLineItem.base_price_money
will now override the catalog item variation's price. CreateOrderRequestModifier
s may now be created ad hoc using the newname
andbase_price_money
fields.
ordinal
is added toCatalogItemVariation
website_url
is added toLocation
tip_money
is added toTender
- Changed
object_type
andplaceholder_type
from lists to single values inV1PageCell
to mirror data model
The Transaction API now supports the following request objects:
additional_recipients
— data type representing an additional recipient (in other words, a recipient other than the merchant or Square) receiving a portion of a tender.
The new Reporting API includes two endpoints that let you pull information about distributions you have received as an additional recipient:
-
AdditionalRecipientReceivables
— returns a list of receivables (across all source locations) representing monies credited to the given location ID by another Square account using theadditional_recipients
field in a transaction. -
AdditionalRecipientReceivablesRefunds
— returns a list of refunded transactions (across all source locations) related to monies credited to the given location ID by another Square account using theadditional_recipients
field in a transaction.
RegisterDomain
endpoint activates a domain for use with Web Apple Pay.
Location.type
used to indicate whether or not the location object represents a physical space.
Charge
endpoint can charge a specific Order.
CreateOrder
endpoint creates an itemized order which can be referenced in messages to theCharge
endpoint.BatchRetrieveOrders
retrieves order objects referenced in one or more transactions based on the providedorder_id
.
Note: at this point, BatchRetrieveOrders only
returns information on paid orders made through Square's eCommerce APIs (Transactions, Checkout).
order
is removed from Transactionorder_id
is added to TransactionOrderLineItemDiscountType.UNKOWN
renamed toOrderLineItemDiscountType.UNKOWN_DISCOUNT
OrderLineItemTaxType.UNKOWN
renamed toOrderLineItemDiscountType.UNKOWN_TAX
ChargeRequest.idempotency_key
is restricted to max length 192ChargeRequest.card_nonce
is restricted to max length 192ChargeRequest.customer_card_id
is restricted to max length 192ChargeRequest.reference_id
is restricted to max length 40ChargeRequest.note
is restricted to max length 60ChargeRequest.customer_id
is restricted to max length 50CreateCheckoutRequest.redirect_url
is restricted to max length 800- Added
phone_number
andbusiness_name
to Location
- Documentation style and links fixes
- Document Getters and Setters for protected properties
- Support for pagination on V1 endpoints
- Include refund detail fields on V1 Refund model
- Bug Fixes for List Locations endpiont.
- Add functionality for Square Checkout.
- Improve error messaging for API connection failures.
- Initial release of the SDK