| CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 21:28:01 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=pg8iTeLGw_DApotpptjvgHh8NmYK_aRhevx6I61GbBE-1760131681-1.0.1.1-3w0IEXKPztVH._Xu2TbfFE1Uz.T38By_7u_Nq_q9V6_nChCRpG2RpmDChc5ffuI5sTjb5eSWE7X0I9dsv4S3aia8cdK3RoWKmqUw1O7NfZo; path=/; expires=Fri, 10-Oct-25 21:58:01 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c9347d6cb83585-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 9535 » RFC Editor
Search RFCs
RFC 9535
JSONPath: Query Expressions for JSON, February 2024
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Authors:
- S. Gössner, Ed.
G. Normington, Ed.
C. Bormann, Ed. - Stream:
- IETF
- Source:
- jsonpath (art)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9535
Discuss this RFC: Send questions or comments to the mailing list jsonpath@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9535
Abstract
JSONPath defines a string syntax for selecting and extracting JSON (RFC 8259) values from within a given JSON value.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us