payload-v3-endpoints

To access request body data in Payload v3 endpoints, you must parse it asynchronously using `await req.json()`. This replaces the Payload v2 `req.data` property, resolving undefined body access and TypeScript type errors during migration.

The `req.data` property returns undefined in Payload v3 custom handlers because it was removed in the migration from v2. You must refactor your handlers to use `await req.json()` to parse the incoming REST API request body correctly.

The correct handler signature for Payload v3 API endpoints uses an asynchronous function taking a single request argument: `async (req) => ...`. This signature enables proper body parsing and compatibility with Payload v3 runtime patterns.

You return JSON responses from Payload v3 custom endpoints by using the standard web API `Response.json()` method. This standardizes your API endpoint responses and ensures proper error handling patterns within your TypeScript types.

You use the logger in Payload v3 endpoint handlers by accessing `req.payload.logger`. This approach ensures secure and predictable logger usage, avoiding common runtime issues caused by misapplied v2 patterns during migration.

Yes, you need to change `req.cookies` handling when migrating endpoints to Payload v3, as direct v2 patterns cause runtime issues. Refactoring to the v3 endpoint patterns using the `async (req)` signature ensures proper compatibility and resolves TypeScript type errors.