Reference

Numeric types

There are two numeric types in JSON Schema: integer and number. They share the same validation keywords.

JSON has no standard way to represent complex numbers, so there is no way to test for them in JSON Schema.

integer

The integer type is used for integral numbers. JSON does not have distinct types for integers and floating-point values. Therefore, the presence or absence of a decimal point is not enough to distinguish between integers and non-integers. For example, 1 and 1.0 are two ways to represent the same value in JSON. JSON Schema considers that value an integer no matter which representation was used.

Language-specific info:

Python

Ruby

Objective-C

Swift

In Python, "integer" is analogous to the int type.

schema

{ "type": "integer" }

data

42

compliant to schema

data

-1

compliant to schema

Numbers with a zero fractional part are considered integers:

data

1.0

compliant to schema

Floating point numbers are rejected:

data

3.1415926

not compliant to schema

Numbers as strings are rejected:

data

"42"

not compliant to schema

number

The number type is used for any numeric type, either integers or floating point numbers.

Language-specific info:

Python

Ruby

Objective-C

Swift

In Python, "number" is analogous to the float type.

schema

{ "type": "number" }

data

42

compliant to schema

data

-1

compliant to schema

Simple floating point number:

data

5.0

compliant to schema

Exponential notation also works:

data

2.99792458e8

compliant to schema

Numbers as strings are rejected:

data

"42"

not compliant to schema

Multiples

Numbers can be restricted to a multiple of a given number, using the multipleOf keyword. It may be set to any positive number.

schema

{  "type": "number",  "multipleOf" : 10}

data

0

compliant to schema

data

10

compliant to schema

data

20

compliant to schema

data

23

not compliant to schema

The multiple can be a floating point number:

schema

{  "type": "number",  "multipleOf" : 0.01}

data

4.02

compliant to schema

data

4.021

not compliant to schema

Range

Ranges of numbers are specified using a combination of the minimum and maximum keywords, (or exclusiveMinimum and exclusiveMaximum for expressing exclusive range).

If x is the value being validated, the following must hold true:

x ≥ minimum
x > exclusiveMinimum
x ≤ maximum
x < exclusiveMaximum

While you can specify both of minimum and exclusiveMinimum or both of maximum and exclusiveMaximum, it doesn't really make sense to do so.

schema

{  "type": "number",  "minimum": 0,  "exclusiveMaximum": 100}

Less than minimum:

data

-1

not compliant to schema

minimum is inclusive, so 0 is valid:

data

0

compliant to schema

data

10

compliant to schema

data

99

compliant to schema

exclusiveMaximum is exclusive, so 100 is not valid:

data

100

not compliant to schema

Greater than maximum:

data

101

not compliant to schema

Draft-specific info:

Draft 4

In JSON Schema Draft 4, exclusiveMinimum and exclusiveMaximum work differently. There they are boolean values, that indicate whether minimum and maximum are exclusive of the value. For example:

if exclusiveMinimum is false, x ≥ minimum
if exclusiveMinimum is true, x > minimum.

This was changed to have better keyword independence.

Here is an example using the older Draft 4 convention:

schema

{  "type": "number",  "minimum": 0,  "maximum": 100,  "exclusiveMaximum": true}

Less than minimum: json // props { "indent": true, "valid": false } -1 exclusiveMinimum was not specified, so 0 is included:

data

0

compliant to schema

data

10

compliant to schema

data

99

compliant to schema

exclusiveMaximum is true, so 100 is not included:

data

100

not compliant to schema

Greater than maximum:

data

101

not compliant to schema

Need Help?

Did you find these docs helpful?

Help us make our docs great!

At JSON Schema, we value docs contributions as much as every other type of contribution!

Edit this page on Github

Learn how to contribute

Still Need Help?

Learning JSON Schema is often confusing, but don't worry, we are here to help!.

Ask the community on GitHub

Ask the community on Slack