Hey, @labandotheque-9185!

Could you try changing your header from Cache-Tag to Cache-Control with tags included, or use the x-vercel-cache-tags header instead:

1// Option 1: Use x-vercel-cache-tags header2setResponseHeader(event, 'x-vercel-cache-tags', `${subdomain},subdomain`)34// Option 2: Include tags in Cache-Control header5setResponseHeader(event, 'Cache-Control', `public, max-age=0, s-maxage=86400, must-revalidate, cache-tag=${subdomain},subdomain`)

Also, make sure you’re using the correct API endpoint format. The invalidation should work with:

1POST https://api.vercel.com/v1/edge-cache/purge?teamId=YOUR_TEAM_ID

With body:

1{2  "tags": ["osso"]3}

Appreciate the feedback - I'll share this with the product and docs team!

Thanks for your answer @pawlean !

I tried to add the mentioned headers (option 1, then option 2, then both), but the manual purge by tag still isn't working:

As you can see, the x-vercel-cache-tags header is correctly added, but when I try to purge using the osso tag, the cache still returns HIT. However, when I use *, the cache is correctly MISS

I also wanted to try the suggested endpoint https://api.vercel.com/v1/edge-cache/purge?teamId=YOUR_TEAM_ID, but I’m on a Hobby plan and it’s a solo project, so I don’t have a teamId.

I searched on Vercel and on Google for documentation about v1/edge-cache/purge endpoint, but couldn’t find anything! (a good example of what I meant in my previous post about the cache documentation UX)

Where can I find the documentation for this endpoint?

I tried with https://api.vercel.com/v1/edge-cache/purge?projectIdOrName=prj_SzBUtNC3uMfV8wBAFJ9QmImUY7q5, but the API returns a 404 Not Found response.

1{2  "error": {3    "code": "not_found",4    "message": "Not Found"5  }6}

Can we use the v1/edge-cache/purge endpoint on hobby plan with a projectId param instead of teamId?

Thanks again for your help!

@pawlean Just wanted to kindly check if anyone had a chance to look into this 🙂

Hello,

Following up on my previous post: I tried the suggestions from @pawlean (Vercel staff)

Method 1: Project Settings > Caches

What I tried:

Use x-vercel-cache-tags header as suggested by @pawlean (but I can't find any documentation about this header?):

1setResponseHeader(event, 'x-vercel-cache-tags', `${subdomain},subdomain`)2setResponseHeader(event, 'Cache-Control', `public, max-age=0, s-maxage=86400, must-revalidate, cache-tag=${subdomain},subdomain`)

First, I tried to manual purge from the Vercel interface but:

✅ The headers appear correctly in the response. ❌ But manual purge by tag still doesn’t work: x-vercel-cache is still HIT. ✅ Purge all (*) works as expected — the cache returns MISS.

Method 2: Api endpoint (v1/edge-cache/purge)

Then I wanted to try the suggested endpoint by @pawlean:

1POST https://api.vercel.com/v1/edge-cache/purge?teamId=YOUR_TEAM_ID2BODY { "tags": ["osso"] }

❌ But the suggested endpoint seems doesn't exists, it returns a 404 Not Found error:

--> I couldn’t find any documentation or examples for using the /v1/edge-cache/purge endpoint, can you tell us where we can find it?

Conclusion

✅ x-vercel-cache-tags and Cache-Control headers are correctly added ❌ On Project Settings > Caches, Purge CDN cache by tag doesn’t invalidate the cache ✅ But purge-all (*) works ❌ v1/edge-cache/purge suggested API endpoint seems doesn't exists, returns 404 error... ❌ No documentation about the suggested headers, and no documentation about the endpoint...

So… what am I missing here? Is this feature simply not supported on Hobby plans, or is there a specific requirement I’ve overlooked?

Thanks again for your help — I really want to understand what’s going on.

Hi @labandotheque-9185, sorry for the delayed response. Let us try to debug this together.

Have you tried waiting for a few minutes? Let's try debugging from the dashboard side,

1. Create your request, see if it's a HIT. Choose a path that no one else uses during our test.
2. Go to Dashboard and purge the cache.
3. Wait for 2 minutes. This wait is usually in milliseconds/seconds. But, for this test's sake let's wait longer.
4. Retry the request.
5. Share the result here.

Hi @anshumanb, and thanks for your answer!

I'm on a dev server so no one else use the tested url.

I tried to purge the cache from the dashboard, then waiting 2 minutes, and 5 minutes, but still serve the old cache...

Thanks for trying it out. Let me recreate it on one of my hobby projects and revert here.

Hi @labandotheque-9185, I tried purging CDN caching and I had the same behavior as you. But, when I purged the data cache. The cache was immediately purged and got a age: 0 response.

Edit: I was using Next.js

I don't think cache-tag caching is supported in Nuxt. Can you share the exact docs you followed originally? Yes, I agree the docs can be confusing because of various naming convention and the Next.js specific caching features.

Hi @labandotheque-9185, I see. The docs you share are about cache purging. I'm curious where you learned about using the Cache-Tag header you mentioned in your original post. Because, I couldn't find it in our docs.

The Cache-Control headers are respected in all responses as per web standards. But, Next.js specifically has Data Cache, which is handled differently. Hence, my experience was different.

Thanks for sharing the code snippets. There's no cache-tag header in our https://vercel.com/docs/headers/cache-control-headers docs.

The Cache tags in Next.js are driven by Framework primitives like https://nextjs.org/docs/app/api-reference/functions/cacheTag.

I'm talking to our team to figure out a solution for your use case.

Hi @anshumanb,

Thanks for this clarification. I now understand the distinction regarding Next.js and cache tags.

I do find the documentation a bit confusing, particularly because it’s not always clear what is handled by Next.js versus Vercel as a host. For example, relevant URLs exist, but they don’t make the limitation explicit:

• Programmatically purging Vercel cache — doesn’t mention that manual purging is only possible via cache tags but cache tags are only available with Next.js..
• Invalidate by tag REST API — doesn’t mention that cache tags are only available with Next.js.
• The standard Cache-Tag header is used in other CDN contexts (like Netlify and Cloudflare), so nothing in Vercel’s cache-control headers documentation suggests it wouldn’t be recognized when not using Next.js.

From the outside, these docs give the impression that manual purging could be generally available, which is why I initially tried it with Nuxt.

If that’s the case, it would have been very helpful for the documentation to make this limitation explicit upfront, to avoid spending time trying to make it work in other frameworks.

Just to confirm, is it correct that there’s currently no way to manually purge the edge cache for frameworks other than Next.js, since it relies on cache tags?

I really appreciate your time and help in clarifying this

Hi @labandotheque-9185, your feedback is understandable and duly noted. I'll work with the docs team to see how this can be improved.

Part of the reason is that this Cache tags purging came in recently and the team is still ironing out some features (which includes cross framework support). We do have a closed beta for it but don't have a timeline when this will go public/stable.

As of now, purging with tags is not possible in frameworks other than Next.js. But, this will change soon.

Sorry for all the confusion.

So is there any way to purge cache on Nuxt.js app other than pushing a new deployment?

You need to use this helper function to add cache tags:

1import { addCacheTag } from '@vercel/functions';

Then you can purge by that tag later.

See the docs here:

https://vercel.com/docs/functions/functions-api-reference/vercel-functions-package#addcachetag