Developer Reference Guides

Compact, implementation-focused references for the protocol details developers look up while building and debugging APIs.

These pages are designed to answer two questions quickly: what a field, status, or encoding rule means, and what an implementation should do with it. Each reference links back to a relevant browser-based tool or troubleshooting guide so a definition can be tested against real input without uploading that input to Cryonel.

HTTP

Use the HTTP references when a request reaches the wrong handler, a response is cached unexpectedly, or browser security headers change client behavior. They distinguish protocol semantics from framework conventions and include practical request and response examples.

• HTTP Status Codes Reference
• HTTP Methods Reference
• HTTP Headers Reference
• Cache-Control Directives Reference
• CORS Headers Reference

Authentication and API Contracts

This group covers the trust and compatibility boundaries around APIs: JWT claims, OAuth flows, OpenAPI schemas, JSON Schema constraints, and webhook delivery. Treat the entries as implementation references, not substitutes for issuer-specific security policy.

• JWT Claims Reference
• OpenAPI Data Types and Formats
• JSON Schema Keywords Reference
• OpenAPI Security Schemes Reference
• OAuth Grant Types Reference
• Webhook Delivery and Retry Reference

Encoding, Formats and Scheduling

Encoding and format references focus on the small differences that cause large bugs: Base64 versus Base64URL, timestamp units, JSON value types, MIME types, URL escaping, UUID versions, and cron field order. Verify the producer's contract before applying a conversion.

• Base64 Encoding Reference
• UUID Versions Reference
• Unix Timestamp Reference
• Regular Expression Flags Reference
• JSON Value Types Reference
• JSON Lines and NDJSON Reference
• URL Encoding Reference
• MIME Types Reference
• Cron Expression Syntax Reference

Editorial method

Reference content is checked against the relevant published specification and a working example. When ecosystems differ, the page identifies that boundary instead of presenting one library's behavior as a universal rule. See About Cryonel for the maintainer, correction process, and automated quality checks.