const tokenSource = useMemo(() => { return TokenSource.endpoint("/api/auth/livekit"); }, []); how would i pass data to the token source endpoint ? i need to pass an id in the body

Thanks for reaching out, Aditya. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

Object literal may only specify known properties, and 'body' does not exist in type 'EndpointOptions'.ts(2353) Got this type error ?

Thanks — I’m responding to your TypeScript error about

'body' does not exist in type 'EndpointOptions'

. Short answer: that error is correct. The object form of

TokenSource

does not accept a

body

field. Use

context

(sent as query params) or provide a custom async function (if you need to POST JSON in the body). Two practical options: 1) Use

context

(object form — sends data as query parameters) • Good when GET + query params are fine. • Example:

const tokenSource = {
  endpoint: "/api/auth/livekit",
  apiKey: "your-api-key",
  context: { id: "user-123" },
};

On the server you’ll read

id

from query params (e.g.,

req.query.id

or

req.nextUrl.searchParams

). 2) Use a custom async function for full control (POST with JSON body) • Use this when you must send a JSON body or custom headers. • Example:

const tokenSource = async (roomName: string, participantName: string) => {
  const res = await fetch("/api/auth/livekit", {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({ id: "user-123", roomName, participantName }),
  });
  const data = await res.json();
  return data.token;
};

Pass this function directly where a

TokenSource

is accepted. If you’d like, tell me: • Whether GET/query params are acceptable, or you specifically need POST+body. • Where the id comes from (prop/state/route/user session). I’ll give the exact code snippet wired into your component (including correct

useMemo

dependencies) based on your choice.

so there is no way to send data ?

You're right to ask—yes, you can send data to your token endpoint, but how you do it depends on which TokenSource form you use. Brief recap of options: • Object form (endpoint + context) — You cannot send a request body. Use

context

to pass data; it will be serialized into query parameters on a GET request. ◦ Example:

const tokenSource = {
      endpoint: "/api/auth/livekit",
      apiKey: "your-api-key",
      context: { id: "user-123" },
    };

• Server: read from query params (e.g.,

req.query.id

or

req.nextUrl.searchParams

). • Function form (custom async function) — You can send whatever you need (POST, JSON body, headers). This gives you full control and avoids the TypeScript error. ◦ Example:

const tokenSource = async (roomName: string, participantName: string) => {
      const res = await fetch("/api/auth/livekit", {
        method: "POST",
        headers: { "Content-Type": "application/json" },
        body: JSON.stringify({ id: "user-123", roomName, participantName }),
      });
      const data = await res.json();
      return data.token;
    };

• Server: read JSON body as usual. Which to use? • Use context if passing data via query string is acceptable and you want the simple object form. • Use a custom function if you need to send a POST body, custom headers, or compute the payload dynamically. If you tell me whether GET/query params are acceptable or you need POST+body (and where the id comes from—prop, state, route param, or user session), I’ll give the exact code snippet wired into your component (with

useMemo

and correct typings).