Jiandu Native API
Native household document API served from the configured Jiandu origin. The safe default is loopback HTTP; supported household access uses HTTPS at a reviewed reverse proxy to a private Jiandu listener. Successful intake is asynchronous: a 202 response means the immutable original and durable work were accepted, not that extraction and indexing are complete.
Authentication
- HTTP: Bearer Auth
- API Key: captureAgentAuth
- API Key: cookieAuth
- HTTP: Bearer Auth
Opaque 256-bit session credential or scoped personal access token; both are distinct from the first-run owner token.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | 64 lowercase hexadecimal characters |
Narrow revocable outbound-agent credential using the Jiandu-Capture <credential> scheme. It cannot authorize browser, document, member, or installation APIs.
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | Authorization |
Opaque 256-bit session credential in the host-only HttpOnly SameSite=Strict cookie.
Security Scheme Type: | apiKey |
|---|---|
Cookie parameter name: | jiandu_session |
Opaque 256-bit ordinary session bearer. Credential-management operations accept this scheme but reject personal access tokens.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | 64 lowercase hexadecimal characters |