Transitioning from v1 Items to Catalog APIs – Square Corner Blog – Medium

Item management can be an important piece of any application. Here is what you need to know if you are moving from the v1 items APIs to the new Catalog endpoints.

Earlier this year, Square released new catalog endpoints to help manage your items in a more streamlined and scalable way. You might be familiar with the v1 endpoints create,retrieve, update and delete (CRUD) operations with items and their associated variations, modifier lists, modifier options, discounts, fees, etc. Catalog endpoints streamline all of these different entities into a single CatalogObject type with new endpoints for doing batch operations for multiple items at once. As a result, managing items across multiple locations is much easier. For the rest of this post I’ll go over what these differences actually look like for a couple of operations.

Creating items & variations

Previously you only had available endpoints for creating new items, variations, modifiers, etc. Frequently you had to use all of them to create a new item, with complex chaining of requests to make sure that everything was associated correctly. Multiplying that workflow for all of the items in your account can quickly turn “importing your items” into waiting for a gazillion requests to finish as you create new items, variations, discounts, and modifiers, all in serial.

With the catalog endpoints, that workflow has been slimmed down into one endpoint, POST /v2/catalog/object, or upsert catalog object. While this might seem complex at first, catalog objects are very powerful and simplify the number of other calls that you need to make by adding multiple object types to the same request. You can now create your items in parallel to their variations, options, and modifiers, all while operating at great scale due to the batch endpoint options.

Let’s take a look at the code required to create a new item and a couple of variations.

Creating an item and variation with v1 item endpoints

Creating an item and variation with v2 Catalog endpoints

Retrieving items

This is another area where the Catalog endpoints can make a big difference, especially if you manage items for multiple locations.

Retrieving an item and variation with v1 item endpoints

Retrieving an item and variation with v1 item endpoints

At first glance, the two snippets look similar, but the little differences can make a big impact in how easy it is to manage a real world example. First of all, you don’t need a location to retrieve your items, since items are no longer necessarily scoped to individual locations. Further, you have the option of requesting all of the related objects with the $include_related_objects parameter, which includes all the related category, taxes, and modifier lists that apply to the item. The same operation with the v1 item’s endpoints would require you to call specific endpoints for each of the different properties you want to retrieve.

This is just a taste of what’s better about using the new Catalog APIs over the v1 items endpoints, so if you haven’t made the switch yet, give it a try and see how it might it simplify some of your code.

Square is also hiring now for our developer platform and more! Take a look at to see if there is an opportunity you might be interested in. Come work with us :).

Source link