Get help on Discord

Sanity HTTP 404 Error: Missing API version in client config

16 replies
Last updated: Nov 29, 2025
I've started a project with nextJS + sanity. I'm facing some problems. What's wrong in my code? When I open the console it shows me :
Server error:
*Error: HTTP 404 Not Found: https://*******.
api.sanity.io/v1/data/query/production?query=*%5B%20_type%20%3D%3D%20%22post%22%5D *
I attached screenshots and code below, please someone help.

sanity.js file:
import { createClient, createImageUrlBuilder } from "next-sanity";

const config = {
  
  dataset: "production",
  projectId: "****************",
  useCdn: process.env.NODE_ENV === "production",
  
};

export const urlFor = (source) => createImageUrlBuilder(config).image(source);
export const sanityClient = createClient(config);

homepage.js file:
import React from "react";
import { sanityClient } from "../sanity";

const Homepage = ({ properties }) => {
  console.log(properties);
  return (
    <div>
      <h1>hello</h1>
    </div>
  );
};

export const getServerSideProps = async () => {
  const query = '*[ _type == "post"]';
  const properties = await sanityClient.fetch(query);

  if (!properties.length) {
    return {
      props: {
        properties: [],
      },
    };
  } else {
    return {
      props: {
        properties,
      },
    };
  }
};

export default Homepage;

post.js Schema:
export default {
  name: "post",
  title: "Post",
  type: "document",
  fields: [
    {
      name: "name",
      title: "Name",
      type: "string",
      description: "please use 'Firstname Lastname' format",
    },
    {
      name: "slug",
      title: "Slug",
      type: "slug",
      options: {
        source: "name",
        maxLength: 100,
      },
    },
    {
      name: "image",
      title: "Image",
      type: "image",
    },
  ],
};

AI Update

The HTTP 404 error you're seeing is happening because your Sanity client configuration is missing the required apiVersion property. This is a mandatory field that tells Sanity which version of the API you want to use.

Here's the fix for your sanity.js file:

import { createClient, createImageUrlBuilder } from "next-sanity";

const config = {
  dataset: "production",
  projectId: "****************",
  apiVersion: "2024-01-01", // ADD THIS LINE
  useCdn: process.env.NODE_ENV === "production",
};

export const urlFor = (source) => createImageUrlBuilder(config).image(source);
export const sanityClient = createClient(config);

The apiVersion should be set to today's date or the date you're developing your project (in YYYY-MM-DD format). This ensures your queries work consistently as Sanity's API evolves.

Additional recommendations:

  1. Use environment variables instead of hardcoding your projectId. Create a .env.local file:
NEXT_PUBLIC_SANITY_PROJECT_ID=your-project-id
NEXT_PUBLIC_SANITY_DATASET=production

Then update your config:

const config = {
  dataset: process.env.NEXT_PUBLIC_SANITY_DATASET || "production",
  projectId: process.env.NEXT_PUBLIC_SANITY_PROJECT_ID,
  apiVersion: "2024-01-01",
  useCdn: process.env.NODE_ENV === "production",
};

  1. Verify your dataset exists: Double-check that you actually have a "production" dataset in your Sanity project. You can verify this in your Sanity management console or by running sanity dataset list in your terminal.

  2. Make sure your schema is deployed: Ensure you've started your Sanity Studio (sanity dev) so your "post" schema is available, or if you're using a separate Studio, make sure it's been deployed.

Once you add the apiVersion, your 404 error should be resolved and your queries will work properly!

Show original thread
16 replies

Sanity – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Get started for freeExplore the demo

Was this answer helpful?