rc3 request
RC request information
**/*.request
Validate
Check your file against this schema
Opens the validator with this schema already loaded. Paste your
**/*.request and it validates in your browser — nothing is uploaded.
Reference
Fields
Generated directly from the schema, following local
$refs, to two levels of nesting.
| Field | Type | Description |
|---|---|---|
$schema | string | The JSON schema to use for validation |
comment | string | A comment to provide documentation for this request |
method | string | The HTTP method to use for this request one of: "GET", "POST", "PUT", "PATCH", "DELETE", "HEAD" … (+1) |
url | string | The URL to use for this request |
params | object | — |
params.name | string | — |
form_data | object | — |
form_data.name | string | — |
auth | any | — |
headers | object | — |
headers.name | string | — |
body | object | The body of the request |
body.text | string | — |
body.json | object | — |
save_responses | boolean | Whether to save .response files in the same dir as the .request file |
extract | object | JSON node, or Text pattern (with regex group) to extract from response |
extract.json_path | string | A JSON Path expression to extract a single field from JSON |
extract.text_pattern | string | A Python regex pattern with a single REGEX GROUP to be extracted from the response |
extract.env | string | Choose to store the extracted field in either the global env (default), or currently selected env from your collection one of: "global", "current" |
extract.var | string | The var name (default is token) in the environment to store the extracted value in |
Audit
What we found in this schema
- Declared draft: draft-07
- Validates cleanly against its own meta-schema.
- 18 properties, 78% carrying a description, max nesting depth 5.
Standards
Specification sections for the keywords in this schema
| Keyword | Document | Section |
|---|---|---|
$defs | JSON Schema Core, draft 2020-12 | §8.2.4 — Schema Re-Use With "$defs" |
$id | JSON Schema Core, draft 2020-12 | §8.2.1 — The "$id" Keyword |
$ref | JSON Schema Core, draft 2020-12 | §8.2.3.1 — Direct References with "$ref" |
$schema | JSON Schema Core, draft 2020-12 | §8.1.1 — "$schema" |
additionalProperties | JSON Schema Core, draft 2020-12 | §10.3.2.3 — "additionalProperties" |
description | JSON Schema Validation, draft 2020-12 | §9.1 — "title" and "description" |
enum | JSON Schema Validation, draft 2020-12 | §6.1.2 — "enum" |
properties | JSON Schema Core, draft 2020-12 | §10.3.2.1 — "properties" |
type | JSON Schema Validation, draft 2020-12 | §6.1.1 — "type" |
Documents
- JSON Schema Core, draft 2020-12 — JSON Schema: A Media Type for Describing JSON Documents, A. Wright, H. Andrews, B. Hutton, G. Dennis, Eds., 2022. draft-bhutton-json-schema-01. An expired Internet-Draft with no formal standing in the IETF standards process; it is nonetheless the specification of record for JSON Schema 2020-12, published by json-schema.org.
- JSON Schema Validation, draft 2020-12 — JSON Schema Validation: A Vocabulary for Structural Validation of JSON, A. Wright, H. Andrews, B. Hutton, Eds., 2022.
- RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The format a schema describes.
- RFC 6901 — JavaScript Object Notation (JSON) Pointer. Defines the pointer syntax used by $ref fragments and the ~0 / ~1 escapes.
Source
Attribution
This schema comes from SchemaStore, distributed under the Apache License 2.0. Copyright 2015–present Mads Kristensen and contributors. View the original file. The field table and audit on this page are generated by JSONTools.tools; the schema itself is unmodified.