Skip to content


You can cache your API responses to improve performance between multiple calls like for page navigation.


Responses from the useFetch-like composable are cached by default. On the other hand, you have to enable caching for $fetch composable manually.

Caching Strategy

Both generated composables will calculate a cache key (if no custom one is provided) based on the following properties:

If the cache key is already present in the cache, the cached response will be returned instead of making a new API call.


The cache key is reactive when using the useFetch-like composable. This means that the cache key will be recalculated when any of the properties change.

Custom Cache Key

For more control over when the cache should be invalidated, you can provide a custom cache key to de-duplicate requests. Please head to the API references for more information:

Cache Options

You can disable the cache for each request by setting the cache option to false. This is necessary for the useFetch-like composable:

// Disable caching for a single request
const { data } = await useJsonPlaceholderData('posts/1', {
  cache: false


These examples assume that you have set up an API endpoint called jsonPlaceholder:

// `nuxt.config.ts`
export default defineNuxtConfig({
  modules: ['nuxt-api-party'],

  apiParty: {
    endpoints: {
      jsonPlaceholder: {
        url: ''

Although the $myApi composables are intended for one-time API calls, like submitting form data, you can also cache their responses when needed:

// Enable cache for a single request
const response = $jsonPlaceholder('posts/1', {
  method: 'POST',
  body: {
    foo: 'bar'
  cache: true

Invalidate Cache On Error

If a request fails, the cache will be invalidated by default. This means that the next request will not return the cached response, but make a new API call instead.

Released under the MIT License.