8000 Next.js 14.2.28 Unable to access request Body in api route · Issue #79763 · vercel/next.js · GitHub
[go: up one dir, main page]
Skip to content

Next.js 14.2.28 Unable to access request Body in api route #79763

New issue

Have a question about this project? Sign up for a free GitHub account to open an is 8000 sue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
sptungG opened this issue May 28, 2025 · 1 comment
Closed

Next.js 14.2.28 Unable to access request Body in api route #79763

sptungG opened this issue May 28, 2025 · 1 comment
Labels
Connection Related to the connection() function. invalid link The issue was auto-closed due to a missing/invalid reproduction link. A new issue should be opened.

Comments

@sptungG
Copy link
sptungG commented May 28, 2025

Link to the code that reproduces this issue

/

To Reproduce

Summary
I am using NextJs with app directory and I am trying to access request's body in one api route but it is giving empty object. Here's the code:

export const config = {
  api: { bodyParser: false }
}

const HttpRes = (data: any, status = 200) => NextResponse.json(data || {}, { status });

export async function POST(request: NextRequest, { params }: TParams) {
  try {
    const body = await request.json(); // ---- still have body data
    return HttpRes(await httpReq.post(`/public/clients/`, body));
  } catch (error) {
    const mappedError = getErrorMessage(error);
    return HttpRes(mappedError, mappedError.status);
  }
}
import axios from "axios";
import queryString from "query-string";

const instance = axios.create({
  baseURL: process.env.NEXT_PUBLIC_API_URL as string,
  paramsSerializer: {
    serialize: (params) => queryString.stringify(params, { skipNull: true, skipEmptyString: true }),
  },
  maxRedirects: 0,
  adapter: ["fetch", "xhr", "http"],
});

const interceptorReq = instance.interceptors.request.use(
  async (config) => {
    if (config.method && ["post", "put", "patch"].includes(config.method.toLowerCase())) {
      console.log("Request Body:", config.data); // ---- still have body data
    }
    config.headers["Content-Type"] = "application/json";
    return config;
  },
  (error) => Promise.reject(error),
);

instance.interceptors.response.use(
  (response) => {
    return response.data;
  },
  (error) => {
    return Promise.reject(error);
  },
);

export const httpReq = instance;

Current vs. Expected behavior

Below is the image of the request I am sending via postman

Image

here my BE log when use post nextjs api route

Bad Request: /public/appointments/
Creating client with payload: {}
Bad Request: /public/clients/

When I tried accessing request body direct the api in api route there and in that routes they are working perfectly.

Creating client with payload: {'name': 'abcnanccccccc', 'email': '', 'phone_number': '', 'phone_country': 'US', 'business': 'e70ec71a-3baa-4345-b3b9-e23b07476688'}
Client created successfully: {'id': '271a8311-f652-427d-a1d8-39707fcc5e8e', 'name': 'abcnanccccccc', 'phone_number': '', 'phone_country': 'US', 'email': '', 'business': UUID('e70ec71a-3baa-4345-b3b9-e23b07476688')}

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.4.0: Fri Apr 11 18:33:47 PDT 2025; root:xnu-11417.101.15~117/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 20.19.2
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: 10.11.0
Relevant Packages:
  next: 14.2.28 // An outdated version detected (latest is 15.3.2), upgrade is highly recommended!
  eslint-config-next: 14.2.28
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.8.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Connection

Which stage(s) are affected? (Select all that apply)

Other (Deployed), next dev (local)

Additional context

No response
@github-actions github-actions bot added the Connection Related to the connection() function. label May 28, 2025
@github-actions github-actions bot added the invalid link The issue was auto-closed due to a missing/invalid reproduction link. A new issue should be opened. label May 28, 2025
@github-actions GitHub Actions
Copy link
Contributor

We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.

Why was this issue closed?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.

The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.

  • If you did not provide a link or the link you provided is not valid, we will close the issue.
  • If you provide a link to a private repository, we will close the issue.
  • If you provide a link to a repository but not in the correct section, we will close the issue.

What should I do?

Depending on the reason the issue was closed, you can do the following:

  • If you did not provide a link, please open a new issue with a link to a reproduction.
  • If you provided a link to a private repository, please open a new issue with a link to a public repository.
  • If you provided a link to a repository but not in the correct section, please open a new issue with a link to a reproduction in the correct section.

In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.

My repository is private and cannot make it public

In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:

  • Remove any code that is not related to the issue. (pages, API routes, components, etc.)
  • Remove any dependencies that are not related to the issue.
  • Remove any third-party service that would require us to sign up for an account to reproduce the issue.
  • Remove any environment variables that are not related to the issue.
  • Remove private packages that we do not have access to.
  • If the issue is not related to a monorepo specifically, try to reproduce the issue without a complex monorepo setup

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.

I think my reproduction is good enough, why aren't you looking into it quickly?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

@github-actions github-actions bot locked and limited conversation to collaborators May 28, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Connection Related to the connection() function. invalid link The issue was auto-closed due to a missing/invalid reproduction link. A new issue should be opened.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sptungG
0