@lgriffin/esi.ts - EVE Online ESI API Client - v12.3.0
    Preparing search index...
    interface EndpointDefinition {
        path: string;
        method: HttpMethod;
        requiresAuth: boolean;
        pathParams?: readonly string[];
        queryParams?: Record<string, string>;
        hasBody?: boolean;
        bodyBuilder?: (...args: any[]) => unknown;
        cursorPagination?: boolean;
        deprecated?: DeprecationInfo;
        responseSchema?: ZodType<
            unknown,
            unknown,
            $ZodTypeInternals<unknown, unknown>,
        >;
        requestSchema?: ZodType<
            unknown,
            unknown,
            $ZodTypeInternals<unknown, unknown>,
        >;
        textResponse?: TextResponse;
        emptyWhenNoContent?: boolean;
    }
    Index
    path: string

    URL template with placeholders, e.g. 'alliances/{allianceId}/'

    method: HttpMethod

    HTTP method

    requiresAuth: boolean

    Whether the endpoint requires an auth token

    pathParams?: readonly string[]

    Path parameter names in method signature order

    queryParams?: Record<string, string>

    Maps method param name to query string key, e.g. { typeId: 'type_id' }

    hasBody?: boolean

    Whether the method accepts a body parameter (for POST/PUT/DELETE)

    bodyBuilder?: (...args: any[]) => unknown

    Custom body builder for endpoints that construct body from individual params

    cursorPagination?: boolean

    Whether this endpoint uses cursor-based pagination (before/after tokens)

    deprecated?: DeprecationInfo

    Mark an endpoint as deprecated with optional migration guidance

    responseSchema?: ZodType<unknown, unknown, $ZodTypeInternals<unknown, unknown>>

    Zod schema for runtime response validation

    requestSchema?: ZodType<unknown, unknown, $ZodTypeInternals<unknown, unknown>>

    Zod schema for runtime request body validation (opt-in via validateRequest)

    textResponse?: TextResponse

    Return the body as text rather than parsed JSON, requested with this Accept header. For the few ESI routes that are not JSON, such as meta/openapi.yaml.

    emptyWhenNoContent?: boolean

    Resolve with [] when ESI answers with no content: a 204, or a 200 with Content-Length: 0. Only for routes where ESI documents no content as an ordinary answer (a public contract that expired or was accepted). Other endpoints reject an empty 200 body with JSON_PARSE_ERROR.