Create & update season data

JOOR allows for custom Seasons to be created which can be used to categorize your collections (linesheets) and orders. You’ll also be able to filter your reports and orders by these custom seasons, which helps to isolate important data for your records.

Creating Seasons

Use the CREATE /seasons endpoint to create seasons, which will be associated with your collections. Season at JOOR has the following data points:

name - season name ex. SPRING 2022
year - season year ex. 2022
external_id - an id by which the season is identified in your system

[
  {
    "name": "SPRING 2022",
    "year": 2022,
    "external_id": "SP22"
  }
]

A CREATE /seasons response will provide a JOOR season id. JOOR season ids are used in the UPDATE /seasons and CREATE /collections requests. You can choose to store the season id or ask JOOR to provide it whenever you need it using the GET /seasons endpoint.

{
    "data": [
        {
            "id": "33615",
            "name": "SPRING 2022",
            "external_id": "SP22",
            "year": 2022
        }
    ],
    "errors": []
}

Updating Seasons

The UPDATE /seasons request is essentially the same as a CREATE /seasons request with one exception, it requires a JOOR season id so the system knows which season to update. If you saved the JOOR season id when the seasons were created then you can use it in the UPDATE /seasons request; however, if you don't have it then you will have to use the GET /seasons endpoint.

Let's walk through retrieving a season id from JOOR and updating the seasons:

Use the GET /seasons endpoint to see all available seasons and their ids.

For example, https://apisandbox.jooraccess.com/v4/seasons?account=[your_account_id]

Insert the season id into the UPDATE /seasons endpoint to update your desired season.

For example, let's update the external_id for the seasons SPRING 2022

[
  {
    "id": "33615",
    "name": "SPRING 2022",
    "year": 2022,
    "external_id":"SPRINGP22"
  }
]