GET /envelopes endpoint returns a cursor-paginated list of every encrypted envelope stored in your agent’s replication log. To make client-side decryption straightforward with the Web Crypto API, the server strips the initial 12-byte initialization vector (IV) from each stored binary block and returns it as a separate base64 field alongside the remaining ciphertext. You never receive plaintext — only the sealed envelopes your client originally uploaded.
Request
Query Parameters
integer
Maximum number of envelopes to return per page. Minimum
1, maximum 500, default 100.integer
Exclusive lower bound on the sequence number. Returns only envelopes with a sequence number strictly greater than this value. Use the
x-next-cursor response header value to paginate forward.integer
Exclusive upper bound on the sequence number. Returns only envelopes with a sequence number strictly less than this value.
Response Headers
The response includes the following custom headers for cursor-based pagination:Response
200 OK
Returns a JSON array. Each element represents one encrypted envelope:string
Base64-encoded ciphertext — the AES-256-GCM ciphertext and auth tag, with the IV removed (it is returned separately in
iv).string
Base64-encoded 12-byte GCM initialization vector, extracted from the stored binary block by the server.
string
SHA-256 hash of the payload as recorded at upload time.
integer
Monotonic sequence number for this envelope.
string
Client-supplied ISO-8601 timestamp from when the envelope was originally created.