@zimic/interceptor 0.19.1-canary.2 → 0.19.1-canary.3

package/src/http/interceptor/types/public.ts

@@ -3,42 +3,11 @@ import { HttpSchema } from '@zimic/http';
 import { SyncHttpInterceptorMethodHandler, AsyncHttpInterceptorMethodHandler } from './handlers';
 import { HttpInterceptorPlatform, RemoteHttpInterceptorOptions, UnhandledRequestStrategy } from './options';
 
-/**
- * Configures if the intercepted requests are saved and how they are handled.
- *
- * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#saving-requests Saving intercepted requests}
- * @see {@link https://github.com/zimicjs/zimic/wiki/guides‐testing‐interceptor Testing}
- */
+/** @see {@link https://zimic.dev/docs/interceptor/api/create-http-interceptor `createHttpInterceptor` API reference} */
 export interface HttpInterceptorRequestSaving {
-  /**
-   * Whether {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler request handlers}
-   * should save their intercepted requests in memory and make them accessible through
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerrequests `handler.requests`}.
-   *
-   * If you are using
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorchecktimes `interceptor.checkTimes()`}
-   * or
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerchecktimes `handler.checkTimes()`}
-   * during tests, consider enabling this option to get more detailed information in `TimesCheckError` errors.
-   *
-   * **Important**: If `requestSaving.enabled` is `true`, make sure to regularly clear the interceptor to avoid requests
-   * accumulating in memory. A common practice is to call
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorclear `interceptor.clear()`}
-   * after each test.
-   *
-   * @default process.env.NODE_ENV === 'test'
-   */
+  /** @see {@link https://zimic.dev/docs/interceptor/api/create-http-interceptor `createHttpInterceptor` API reference} */
   enabled: boolean;
-
-  /**
-   * The safe number of requests to save in memory before logging warnings in the console. If `requestSaving.enabled` is
-   * `true` and the interceptor is not regularly cleared with
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorclear `interceptor.clear()`},
-   * the requests may accumulate in memory and cause performance issues. This option does not limit the number of
-   * requests saved in memory, only when to log warnings.
-   *
-   * @default 1000
-   */
+  /** @see {@link https://zimic.dev/docs/interceptor/api/create-http-interceptor `createHttpInterceptor` API reference} */
   safeLimit: number;
 }
 
@@ -46,7 +15,7 @@ export interface HttpInterceptorRequestSaving {
  * An interceptor to handle HTTP requests and return mock responses. The methods, paths, status codes, parameters, and
  * responses are statically-typed based on the provided service schema.
  *
- * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httpinterceptor `HttpInterceptor` API reference}
+ * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor `HttpInterceptor` API reference}
  */
 // The schema is still a generic type for backward compatibility.
 // eslint-disable-next-line @typescript-eslint/naming-convention
@@ -54,15 +23,15 @@ export interface HttpInterceptor<_Schema extends HttpSchema> {
   /**
    * The base URL used by the interceptor.
    *
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorbaseurl `interceptor.baseURL` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#interceptorbaseurl `interceptor.baseURL` API reference}
    */
   baseURL: string;
 
   /**
    * Configures if the intercepted requests are saved and how they are handled.
    *
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#saving-requests Saving intercepted requests}
-   * @see {@link https://github.com/zimicjs/zimic/wiki/guides‐testing‐interceptor Testing}
+   * @see {@link https://zimic.dev/docs/interceptor/api/create-http-interceptor `createHttpInterceptor` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/guides/http/testing Testing}
    */
   requestSaving: HttpInterceptorRequestSaving;
 
@@ -70,7 +39,7 @@ export interface HttpInterceptor<_Schema extends HttpSchema> {
    * The platform the interceptor is running on.
    *
    * @readonly
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorplatform `interceptor.platform` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#interceptorplatform `interceptor.platform` API reference}
    */
   get platform(): HttpInterceptorPlatform | null;
 
@@ -78,7 +47,7 @@ export interface HttpInterceptor<_Schema extends HttpSchema> {
    * Whether the interceptor is currently running and ready to use.
    *
    * @readonly
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorisrunning `interceptor.isRunning` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#interceptorisrunning `interceptor.isRunning` API reference}
    */
   get isRunning(): boolean;
 
@@ -90,55 +59,53 @@ export interface HttpInterceptor<_Schema extends HttpSchema> {
    *
    * @throws {UnregisteredServiceWorkerError} When the worker is targeting a browser environment and the mock service
    *   worker is not registered.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorstart `interceptor.start()` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#interceptorstart `interceptor.start()` API reference}
    */
   start: () => Promise<void>;
 
   /**
    * Stops the interceptor, preventing it from intercepting HTTP requests. Stopped interceptors are automatically
    * cleared, exactly as if
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorclear `interceptor.clear()`}
-   * had been called.
+   * {@link https://zimic.dev/docs/interceptor/api/http-interceptor#interceptorclear `interceptor.clear()`} had been
+   * called.
    *
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorstop `interceptor.stop()` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#interceptorstop `interceptor.stop()` API reference}
    */
   stop: () => Promise<void>;
 
   /**
    * Checks if all handlers created by this interceptor have matched the number of requests declared with
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes `handler.times()`}.
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes `handler.times()`}.
    *
    * If some handler has matched fewer or more requests than expected, this method will throw a `TimesCheckError` error,
    * including a stack trace to the
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes `handler.times()`} that
-   * was not satisfied.
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes `handler.times()`} that was not
+   * satisfied.
    *
    * This is useful in an `afterEach` hook (or equivalent) to make sure that all expected requests were made at the end
    * of each test.
    *
-   * When
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#saving-requests
-   * `requestSaving.enabled`} is
-   * `true` in your interceptor, the `TimesCheckError` errors will also list each unmatched request with diff of the
-   * expected and received data. This is useful for debugging requests that did not match a handler with
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions}.
+   * When {@link https://zimic.dev/docs/interceptor/api/create-http-interceptor `requestSaving.enabled`} is `true` in
+   * your interceptor, the `TimesCheckError` errors will also list each unmatched request with diff of the expected and
+   * received data. This is useful for debugging requests that did not match a handler with
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}.
    *
    * @throws {TimesCheckError} If some handler has matched less or more requests than the expected number of requests.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorchecktimes `interceptor.checkTimes()` API reference}
-   * @see {@link https://github.com/zimicjs/zimic/wiki/guides‐teting Testing guide}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#interceptorchecktimes `interceptor.checkTimes()` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/guides/http/testing Testing guide}
    */
   checkTimes: (() => void) | (() => Promise<void>);
 
   /**
    * Clears the interceptor and all of its
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   * instances, including their registered responses and intercepted requests. After calling this method, the
-   * interceptor will no longer intercept any requests until new mock responses are registered.
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} instances, including their
+   * registered responses and intercepted requests. After calling this method, the interceptor will no longer intercept
+   * any requests until new mock responses are registered.
    *
    * This method is useful to reset the interceptor mocks between tests.
    *
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorclear `interceptor.clear()` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#interceptorclear `interceptor.clear()` API reference}
    */
   clear: (() => void) | (() => Promise<void>);
 }
@@ -148,9 +115,9 @@ export interface HttpInterceptor<_Schema extends HttpSchema> {
  * and responses are statically-typed based on the provided service schema.
  *
  * To intercept HTTP requests, the interceptor must have been started with
- * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorstart `interceptor.start()`}.
+ * {@link https://zimic.dev/docs/interceptor/api/http-interceptor#interceptorstart `interceptor.start()`}.
  *
- * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httpinterceptor `HttpInterceptor` API reference}
+ * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor `HttpInterceptor` API reference}
  */
 export interface LocalHttpInterceptor<Schema extends HttpSchema> extends HttpInterceptor<Schema> {
   /** @readonly */
@@ -161,21 +128,19 @@ export interface LocalHttpInterceptor<Schema extends HttpSchema> extends HttpInt
    * matching handler exists, this strategy will be used. If a function is provided, it will be called with the
    * unhandled request.
    *
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#unhandled-requests Unhandled requests}
+   * @see {@link https://zimic.dev/docs/interceptor/guides/http/unhandled-requests Unhandled requests}
    */
   onUnhandledRequest?: UnhandledRequestStrategy.Local;
 
   /**
-   * Creates a GET
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates a GET {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a path.
+   * The path and method must be declared in the interceptor schema.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -183,25 +148,22 @@ export interface LocalHttpInterceptor<Schema extends HttpSchema> extends HttpInt
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns A GET
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns A GET {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   get: SyncHttpInterceptorMethodHandler<Schema, 'GET'>;
 
   /**
-   * Creates a POST
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates a POST {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a path.
+   * The path and method must be declared in the interceptor schema.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -209,25 +171,22 @@ export interface LocalHttpInterceptor<Schema extends HttpSchema> extends HttpInt
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns A POST
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns A POST {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   post: SyncHttpInterceptorMethodHandler<Schema, 'POST'>;
 
   /**
-   * Creates a PATCH
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates a PATCH {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a path.
+   * The path and method must be declared in the interceptor schema.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -235,25 +194,22 @@ export interface LocalHttpInterceptor<Schema extends HttpSchema> extends HttpInt
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns A PATCH
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns A PATCH {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   patch: SyncHttpInterceptorMethodHandler<Schema, 'PATCH'>;
 
   /**
-   * Creates a PUT
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates a PUT {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a path.
+   * The path and method must be declared in the interceptor schema.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -261,25 +217,22 @@ export interface LocalHttpInterceptor<Schema extends HttpSchema> extends HttpInt
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns A PUT
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns A PUT {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   put: SyncHttpInterceptorMethodHandler<Schema, 'PUT'>;
 
   /**
-   * Creates a DELETE
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates a DELETE {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a
+   * path. The path and method must be declared in the interceptor schema.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -287,25 +240,22 @@ export interface LocalHttpInterceptor<Schema extends HttpSchema> extends HttpInt
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns A DELETE
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns A DELETE {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   delete: SyncHttpInterceptorMethodHandler<Schema, 'DELETE'>;
 
   /**
-   * Creates a HEAD
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates a HEAD {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a path.
+   * The path and method must be declared in the interceptor schema.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -313,25 +263,22 @@ export interface LocalHttpInterceptor<Schema extends HttpSchema> extends HttpInt
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns A HEAD
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns A HEAD {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   head: SyncHttpInterceptorMethodHandler<Schema, 'HEAD'>;
 
   /**
-   * Creates an OPTIONS
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates an OPTIONS {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a
+   * path. The path and method must be declared in the interceptor schema.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -339,11 +286,10 @@ export interface LocalHttpInterceptor<Schema extends HttpSchema> extends HttpInt
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns An OPTIONS
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns An OPTIONS {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   options: SyncHttpInterceptorMethodHandler<Schema, 'OPTIONS'>;
 
@@ -357,11 +303,10 @@ export interface LocalHttpInterceptor<Schema extends HttpSchema> extends HttpInt
  * and responses are statically-typed based on the provided service schema.
  *
  * To intercept HTTP requests, the interceptor must have been started with
- * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptorstart `interceptor.start()`}
- * and an {@link https://github.com/zimicjs/zimic/wiki/cli‐zimic‐server#zimic-server interceptor server} should be
- * running.
+ * {@link https://zimic.dev/docs/interceptor/api/http-interceptor#interceptorstart `interceptor.start()`} and an
+ * {@link https://zimic.dev/docs/interceptor/cli/server interceptor server} should be running.
  *
- * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httpinterceptor `HttpInterceptor` API reference}
+ * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor `HttpInterceptor` API reference}
  */
 export interface RemoteHttpInterceptor<Schema extends HttpSchema> extends HttpInterceptor<Schema> {
   /** @readonly */
@@ -371,7 +316,7 @@ export interface RemoteHttpInterceptor<Schema extends HttpSchema> extends HttpIn
    * Options to authenticate the interceptor when connecting to an interceptor server. This is required if the
    * interceptor server was started with the `--tokens-dir` option.
    *
-   * @see {@link https://github.com/zimicjs/zimic/wiki/cli‐zimic‐server#authentication Interceptor server authentication}
+   * @see {@link https://zimic.dev/docs/interceptor/guides/http/remote-interceptors#interceptor-server-authentication Interceptor server authentication}
    */
   auth?: RemoteHttpInterceptorOptions['auth'];
 
@@ -380,26 +325,23 @@ export interface RemoteHttpInterceptor<Schema extends HttpSchema> extends HttpIn
    * matching handler exists, this strategy will be used. If a function is provided, it will be called with the
    * unhandled request.
    *
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#unhandled-requests Unhandled requests}
+   * @see {@link https://zimic.dev/docs/interceptor/guides/http/unhandled-requests Unhandled requests}
    */
   onUnhandledRequest?: UnhandledRequestStrategy.Remote;
 
   /**
-   * Creates a GET
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates a GET {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a path.
+   * The path and method must be declared in the interceptor schema.
    *
-   * When using a
-   * {@link https://github.com/zimicjs/zimic/wiki/getting‐started#remote-http-interceptors remote interceptor}, creating
+   * When using a {@link https://zimic.dev/docs/interceptor/guides/http/remote-interceptors remote interceptor}, creating
    * a handler is an asynchronous operation, so you need to `await` it. You can also chain any number of operations and
    * apply them by awaiting the handler.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -407,30 +349,26 @@ export interface RemoteHttpInterceptor<Schema extends HttpSchema> extends HttpIn
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns A GET
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns A GET {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   get: AsyncHttpInterceptorMethodHandler<Schema, 'GET'>;
 
   /**
-   * Creates a POST
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates a POST {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a path.
+   * The path and method must be declared in the interceptor schema.
    *
-   * When using a
-   * {@link https://github.com/zimicjs/zimic/wiki/getting‐started#remote-http-interceptors remote interceptor}, creating
+   * When using a {@link https://zimic.dev/docs/interceptor/guides/http/remote-interceptors remote interceptor}, creating
    * a handler is an asynchronous operation, so you need to `await` it. You can also chain any number of operations and
    * apply them by awaiting the handler.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -438,30 +376,26 @@ export interface RemoteHttpInterceptor<Schema extends HttpSchema> extends HttpIn
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns A POST
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns A POST {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   post: AsyncHttpInterceptorMethodHandler<Schema, 'POST'>;
 
   /**
-   * Creates a PATCH
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates a PATCH {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a path.
+   * The path and method must be declared in the interceptor schema.
    *
-   * When using a
-   * {@link https://github.com/zimicjs/zimic/wiki/getting‐started#remote-http-interceptors remote interceptor}, creating
+   * When using a {@link https://zimic.dev/docs/interceptor/guides/http/remote-interceptors remote interceptor}, creating
    * a handler is an asynchronous operation, so you need to `await` it. You can also chain any number of operations and
    * apply them by awaiting the handler.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -469,30 +403,26 @@ export interface RemoteHttpInterceptor<Schema extends HttpSchema> extends HttpIn
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns A PATCH
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns A PATCH {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   patch: AsyncHttpInterceptorMethodHandler<Schema, 'PATCH'>;
 
   /**
-   * Creates a PUT
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates a PUT {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a path.
+   * The path and method must be declared in the interceptor schema.
    *
-   * When using a
-   * {@link https://github.com/zimicjs/zimic/wiki/getting‐started#remote-http-interceptors remote interceptor}, creating
+   * When using a {@link https://zimic.dev/docs/interceptor/guides/http/remote-interceptors remote interceptor}, creating
    * a handler is an asynchronous operation, so you need to `await` it. You can also chain any number of operations and
    * apply them by awaiting the handler.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -500,30 +430,26 @@ export interface RemoteHttpInterceptor<Schema extends HttpSchema> extends HttpIn
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns A PUT
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns A PUT {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   put: AsyncHttpInterceptorMethodHandler<Schema, 'PUT'>;
 
   /**
-   * Creates a DELETE
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates a DELETE {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a
+   * path. The path and method must be declared in the interceptor schema.
    *
-   * When using a
-   * {@link https://github.com/zimicjs/zimic/wiki/getting‐started#remote-http-interceptors remote interceptor}, creating
+   * When using a {@link https://zimic.dev/docs/interceptor/guides/http/remote-interceptors remote interceptor}, creating
    * a handler is an asynchronous operation, so you need to `await` it. You can also chain any number of operations and
    * apply them by awaiting the handler.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -531,30 +457,26 @@ export interface RemoteHttpInterceptor<Schema extends HttpSchema> extends HttpIn
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns A DELETE
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns A DELETE {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   delete: AsyncHttpInterceptorMethodHandler<Schema, 'DELETE'>;
 
   /**
-   * Creates a HEAD
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates a HEAD {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a path.
+   * The path and method must be declared in the interceptor schema.
    *
-   * When using a
-   * {@link https://github.com/zimicjs/zimic/wiki/getting‐started#remote-http-interceptors remote interceptor}, creating
+   * When using a {@link https://zimic.dev/docs/interceptor/guides/http/remote-interceptors remote interceptor}, creating
    * a handler is an asynchronous operation, so you need to `await` it. You can also chain any number of operations and
    * apply them by awaiting the handler.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -562,30 +484,26 @@ export interface RemoteHttpInterceptor<Schema extends HttpSchema> extends HttpIn
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns A HEAD
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns A HEAD {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   head: AsyncHttpInterceptorMethodHandler<Schema, 'HEAD'>;
 
   /**
-   * Creates an OPTIONS
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`} for
-   * a path. The path and method must be declared in the interceptor schema.
+   * Creates an OPTIONS {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for a
+   * path. The path and method must be declared in the interceptor schema.
    *
-   * When using a
-   * {@link https://github.com/zimicjs/zimic/wiki/getting‐started#remote-http-interceptors remote interceptor}, creating
+   * When using a {@link https://zimic.dev/docs/interceptor/guides/http/remote-interceptors remote interceptor}, creating
    * a handler is an asynchronous operation, so you need to `await` it. You can also chain any number of operations and
    * apply them by awaiting the handler.
    *
    * After a request is intercepted, Zimic tries to find a handler that matches it, considering the base URL of the
    * interceptor, and the method, path,
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlerwithrestriction restrictions},
-   * and
-   * {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-handlertimes limits on the number of requests}
-   * of the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlerwithrestriction restrictions}, and
+   * {@link https://zimic.dev/docs/interceptor/api/http-request-handler#handlertimes limits on the number of requests} of
+   * the handler. The handlers are checked from the **last** one created to the first one, so new handlers have
    * preference over older ones. This allows you to declare generic and specific handlers based on their order of
    * creation. For example, a generic handler for `GET /users` can return an empty list, while a specific handler in a
    * test case can return a list with some users. In this case, the specific handler will be considered first as long as
@@ -593,11 +511,10 @@ export interface RemoteHttpInterceptor<Schema extends HttpSchema> extends HttpIn
    *
    * @param path The path to intercept. Paths with dynamic parameters, such as `/users/:id`, are supported, but you need
    *   to specify the original path as a type parameter to get type-inference and type-validation.
-   * @returns An OPTIONS
-   *   {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#httprequesthandler `HttpRequestHandler`}
-   *   for the provided path. The path and method must be declared in the interceptor schema.
+   * @returns An OPTIONS {@link https://zimic.dev/docs/interceptor/api/http-request-handler `HttpRequestHandler`} for the
+   *   provided path. The path and method must be declared in the interceptor schema.
    * @throws {NotRunningHttpInterceptorError} If the interceptor is not running.
-   * @see {@link https://github.com/zimicjs/zimic/wiki/api‐zimic‐interceptor‐http#http-interceptormethodpath `interceptor.<method>(path)` API reference}
+   * @see {@link https://zimic.dev/docs/interceptor/api/http-interceptor#declaring-request-handlers Declaring request handlers}
    */
   options: AsyncHttpInterceptorMethodHandler<Schema, 'OPTIONS'>;