envoiReturn T. Keep transport details out.

A framework-free HTTP response layer for axios, fetch, and ofetch. Configure business codes, hooks, and adapters once; expose Promise everywhere.

Run the live demo

Install and configure

Normalize once
Move HTTP status, business codes, renamed fields, and custom errors into one typed response contract.
Keep transport portable
No transport is implicit. Axios, fetch, ofetch, and custom adapters receive the same normalized request.
Debug explicitly
Hooks expose lifecycle behavior; raw keeps status, headers, blobs, and the underlying response available.

ScenarioEnvelope successUnwrap data

Backend responseOK

HTTP 200

{
  "status": 200,
  "body": {
    "code": 200,
    "msg": "ok",
    "data": {
      "id": 42,
      "name": "Ada"
    }
  }
}

envoi outcome—

Ready to run

// Run the scenario to inspect its resolved value or BizError

One client, four explicit layers

const instance = createAxiosInstance({ withCredentials: true });
const http = createHttp({
  adapter: axiosAdapter(instance),
  defaults: { baseURL: "/api", timeout: 15_000 },
  envelope: { code: "code", msg: "msg", data: "data" },
  hooks: { onRequest: auth(getToken), onResponseError: showError },
});

01request hookslifecycle

02adaptertransport

03response policyprotocol

04Promise<T>consumer

Request hooks prepare the call, the adapter executes HTTP, and the selected response policy produces Promise<T>. Application state stays with the caller.

Production paths, not isolated snippets

01 / ExampleBuild a production client

Auth, locale, business codes, query functions, downloads, and a migration path in one example.

02 / ProtocolModel the response contract

HTTP-only defaults, explicit envelopes, renamed fields, custom errors, and expected failure bodies.

03 / TransportKeep adapters interchangeable

Use native settings without leaking baseURL, query serialization, timeout, or error rules into each adapter.

Use envoi when repetition has become behavior

A small project with two plain requests can keep native fetch or axios. envoi becomes useful when several endpoints or applications must agree on response extraction, business failures, shared headers, adapter behavior, and the value returned to callers.

End-to-end exampleBuild the client you would actually ship.

Open the example →

envoiReturn T. Keep transport details out.

Normalize once

Keep transport portable

Debug explicitly

One client, four explicit layers ​

Production paths, not isolated snippets ​

Use envoi when repetition has become behavior ​

One client, four explicit layers

Production paths, not isolated snippets

Use envoi when repetition has become behavior