Ciphertext is encrypted data whose contents should remain unreadable to consumers without the required decryption process. In API pagination, keeping ciphertext opaque protects implementation flexibility: consumers cannot depend on internal token details that may later change. section 21.3.2
Represent encrypted values according to how they travel through an API:
- Avoid numeric types: an integer cannot represent the encrypted data being stored. section 21.3.2
- Prefer a string for transport convenience, especially when values appear in URLs or JSON. section 21.3.2
- Use a Base64-encoded encrypted value serialized as UTF-8 when raw bytes are inconvenient. section 21.3.2
Opaque pagination token
A pagination API can return a string page token containing a Base64-encoded encrypted value. The consumer passes it back unchanged in a later request instead of inspecting or depending on its contents. section 21.3.2




