Shopify's AJAX API cart token does not have a prefix of 'c1-'

Technical Q&A
1

I am currently using Dawn theme 12.0 on my store and the store’s AJAX API cart token is not updating to include the cart token prefix of c1- (as it should per https://shopify.dev/changelog/changes-to-ajax-api-cart-token-format). What could be set up incorrectly on my store to cause the missing cart token prefix?

(i.e. cart token is: Z2NwLXVzLWNlbnRyYWwxOjAxSEU5NDVDSk44VjU4UU4yV0FYWjNDNDNR and I would expect it to start with ‘c1-’ not ‘Z2’. And, every time the cart page is loaded, the cart token starts with ‘Z2,’ not ‘c1-’)

Using this [simplified for public view] code in main-cart-items Section to view the cart token:

$.ajax({
	type: 'GET',
	url: window.Shopify.routes.root + 'cart.json',
	dataType: 'jsonp',
	success: function(data) { 
          var token = data['token'];
          console.log(token);
	}
});
2

And? Is any native behaviors not working as a result?

Such formats are to be treated as random, that changelog even specifically states so.

Apps and themes should be designed to handle cart tokens in any format and of any length.> > Treat the cart token as a random identifier that will change in the future.> > Action Required: Ensure that any app and theme code is free from hard-coded assumptions (ex. Using regex to identify a cart token) on the format and structure of the cart token.

3

Understood, but I would still expect it to look like other cart tokens with or without the c1- and it looks nothing like all of my other store cart tokens, it is not even a GUID, so I still believe something is wrong with this store’s cart token. Has anyone else run into this issue?

What Shopify says exactly regarding cart tokens is:

Changes to Ajax API Cart token format

API

EFFECTIVE JULY 17, 2023

ACTION REQUIRED

Ajax API cart tokens will now be returned with a new format. The new format will include a prefix c1- however the API features and functionality remain unchanged. Apps and themes should be designed to handle cart tokens in any format and of any length. Treat the cart token as a random identifier that will change in the future.

Action Required: Ensure that any app and theme code is free from hard-coded assumptions (ex. Using regex to identify a cart token) on the format and structure of the cart token.

4

yes, I have an issue. There is an api call that I make on all my stores (corporate) that is broken only on the one store with the unusual looking token. Before I request the developer to make api modifications to accommodate the unusual looking token of 56 characters, I need to be sure that the token is valid and not an anomaly.