---
title: >-
  Errors returned in REST now include the attribute name - Shopify developer
  changelog
description: >-
  Shopify’s developer changelog documents all changes to Shopify’s platform.
  Find the latest news and learn about new platform opportunities.
source_url:
  html: >-
    https://shopify.dev/changelog/errors-returned-in-rest-now-include-the-attribute-name
  md: >-
    https://shopify.dev/changelog/errors-returned-in-rest-now-include-the-attribute-name.md
metadata:
  effectiveApiVersion: ''
  affectedApi: []
  primaryTag:
    displayName: API
    handle: api
  secondaryTag:
    displayName: Update
    handle: update
  indicatesActionRequired: false
  createdAt: '2018-11-23T14:12:54-05:00'
  postedAt: '2018-06-05T14:08:00-04:00'
  updatedAt: '2024-02-02T10:04:52-05:00'
  effectiveAt: '2018-06-05T14:08:00-04:00'
---

June 5, 2018

Tags:

* API

# Errors returned in REST now include the attribute name

We've changed the error messages returned in REST responses to include the attribute name, which matches what we currently return in GraphQL.

***

For example:

```
Before:
errors['title'] = ["can't be blank"]
After: 
errors['title'] = ["Title can't be blank"]
```

If you have any apps that display the errors messages to merchants or customers, then you should make sure that the new text is rendered correctly and the attribute name doesn't appear twice.

Although we don't recommend parsing the error message itself for any code logic in your apps (use http status codes instead), if your app currently implements this behavior, then you need to make sure that it handles the new text appropriately.