edge mode; passthrough is for compliance constraints requiring TLS to terminate inside your network, or for client-side cert pinning.
Passthrough flow
- Create the identity with a passthrough tunnel by passing
tunnel: { tls_mode: "passthrough" }toPOST /identities. The tunnel is provisioned inawaiting_cert— DNS is provisioned but inbound TLS handshakes will fail until you complete step 3. - Generate a CSR locally. The Common Name (CN) must equal your tunnel hostname
my-agent.inkboxwire.com. Keep the private key on the machine running your agent. - POST the CSR to
/sign-csr. Inkbox validates the CN, signs it, and returns the certificate plus chain. Status flips toactive. - Renew before expiry. Certificates are valid for 90 days. Call
/sign-csragain with a fresh CSR beforecert_expires_at.
Generate a CSR with OpenSSL
bash
tunnel.key (your private key — keep secret) and tunnel.csr (the CSR you’ll submit below).
Sign CSR
tls_mode: "passthrough" in awaiting_cert or active state.
The first successful signing transitions the tunnel from awaiting_cert to active. Subsequent signings (renewals) are allowed while active.
Certificate issuance has a per-tunnel limit of 4 attempts per 7-day period. After a 429, wait for the Retry-After interval before retrying.
Path parameters
Request body
Request example
JSON
Response (200)
JSON
cert_pem + chain_pem to produce the full chain your agent should present during the TLS handshake.

