Buyer_facing_name is not available in Catalog API - 2026-01-22 version

Questions
1

I had made the query to the support team through Web about the buyer-facing name which was added in the last update.

Support team replied as the follows;

“Regarding this inquiry, there was a new buyer_facing_name field introduced in version 2026-01-22 which maps to “customer-facing name”. You’ll need to update to that version of the API or later to use this field.”

I checked “Listing Catalog” and “Batch Relieve Object” using API v2026-01-22,

however, I could not find the buyer_facing_name field in the return values.Could you help us?

Bests, Shoji

2

Hey! @ShojiPaxtech Do you mind sharing your application ID (beginning sq0idp-…) as well as an example of a catalog object you’re attempting to retrieve?

3

Hi,
I’m a bit hesitant to share my App ID publicly on the forum. Would it be possible to share it via a private channel?

Instead, I attached the sample of objects.

5

“items”: [
{
“type”: “ITEM”,
“id”: “6RDBKXF7DDTWBK5LBKK22TJV”,
“updated_at”: “2026-04-11T00:09:23.963Z”,
“created_at”: “2026-01-10T01:47:46.256Z”,
“version”: 1775866163963,
“is_deleted”: false,
“present_at_all_locations”: false,
“present_at_location_ids”: [
“LFC6APJJDGHMV”
],
“item_data”: {
“name”: “sampletext”,
“description”: “sampletext”,
“is_taxable”: true,
“tax_ids”: [
“G2TW7TMHUCKZXSG4VT7QRVNV”
],
“variations”: [
{
“type”: “ITEM_VARIATION”,
“id”: “OVUGOQB46ERVT5NM7KCIPQ23”,
“updated_at”: “2026-01-10T01:48:08.542Z”,
“created_at”: “2026-01-10T01:47:46.256Z”,
“version”: 1768009688542,
“is_deleted”: false,
“present_at_all_locations”: false,
“present_at_location_ids”: [
“LFC6APJJDGHMV”
],
“item_variation_data”: {
“item_id”: “6RDBKXF7DDTWBK5LBKK22TJV”,
“name”: “”,
“sku”: “12H0401184008”,
“ordinal”: 1,
“pricing_type”: “FIXED_PRICING”,
“price_money”: {
“amount”: 5830,
“currency”: “JPY”
},
“location_overrides”: [
{
“location_id”: “LFC6APJJDGHMV”,
“track_inventory”: true
}
],
“track_inventory”: true,
“sellable”: true,
“stockable”: true,
“channels”: [
“CH_iLHFlw7Btqa9ULsdvgZz3xvlEOkWg1OVWSsfYRlQuYC”,
“CH_HNGLUbpyBdkzYlRCKxuhi7TWIlpcHKRH7RogtUR29945o”
]
}
}
],
“product_type”: “REGULAR”,
“ecom_visibility”: “VISIBLE”,
“image_ids”: [
“NF4VRMGBSYEINXIIFROLO5UZ”,
“HA2QBPU653DAQXPKXGBMAVQR”,
“MAH6EPJULROJEGE64C4CI7G2”
],
“sort_name”: “Miel”,
“categories”: [
{
“id”: “CE4IWXYHRIBOLWBEEZMQ2J3F”,
“ordinal”: 2965532361883838
},
{
“id”: “EXULSVUIHKOLNIXWCV7OV3QL”,
“ordinal”: -2251799461363712
}
],
“description_html”: “sample”,
“channels”: [
“CH_iLHFlw7Btqa9ULsdvgZz3xvlEOkWg1OVWSsfYRlQuYC”,
“CH_HNGLUbpyBdkzYlRCKxuhi7TWIlpcHKRH7RogtUR29945o”
],
“is_archived”: false,
“reporting_category”: {
“id”: “CE4IWXYHRIBOLWBEEZMQ2J3F”,
“ordinal”: 2965532361883838
}
}
},

6

@ShojiPaxtech No worries, I was able to find your application from that! It’s safe to share your application ID publicly (just not your Access Token, of course!), but if you’d rather not do so that’s totally okay.

I’m coordinating with the team internally to confirm what the expected behavior here is.