/Knowledge/sources/honojs__hono/llms-full/hono-stacks-client--cc88a474e9a5.md
Hono Stacks: Client - hono-docs
Hono Stacks: Client Source evidence: /Sources/honojs hono/provenance.md Canonical citation: https://hono.dev/llms full.txt client Summary Next, The client si...
Hono Stacks: Client
Source evidence: /Sources/honojs__hono/provenance.md Canonical citation: https://hono.dev/llms-full.txt#client
Summary
Next, The client-side implementation. Create a client object by passing the AppType type to hc as generics. Then, magically, completion works and the endpoint path and request type are suggested. ```ts import ty...
Content
Next, The client-side implementation.
Create a client object by passing the AppType type to hc as generics.
Then, magically, completion works and the endpoint path and request type are suggested.
import type { AppType } from './server'
import { hc } from 'hono/client'
const client = hc<AppType>('/api')
const res = await client.hello.$get({
query: {
name: 'Hono',
},
})
The Response is compatible with the fetch API, but the data that can be retrieved with json() has a type.
const data = await res.json()
console.log(`${data.message}`)
Sharing API specifications means that you can be aware of server-side changes.
Metadata
{
"chunk_index": 0,
"citation": "https://hono.dev/llms-full.txt#client",
"coverage_role": "overview",
"qualified_title": "Hono / llms-full / Hono Stacks > Client",
"retrieved_at": "2026-07-02T05:51:01Z",
"section_index": 530,
"source_id": "/honojs/hono",
"source_type": "llms_full",
"target_label": "llms-full",
"title": "Hono Stacks: Client",
"upstream_url": "https://hono.dev/llms-full.txt",
"version": "2026"
}