Rate this page Β
- ββ
- ββ
- ββ
- ββ
- ββ
Can we improve this page? Send us feedbackRate this page
- ββ
- ββ
- ββ
- ββ
- ββ
JavaScript Object Notation, or JSON, is a lightweight format for storing and transporting data of most any kind. It contains "fields" of your own choosing to convey strings, numbers, boolean values, other JSON objects, and arrays of values:
{
"temp": 34.5,
"skies": "cloudy",
"windy": true
}
You can learn more about using JSON and its syntax in this online tutorial from Codewall .
As you work with the Notecard API, there are a few behaviors and caveats to keep in mind:
If a structure field is ""
(string), 0
(int), or 0.0
(float),
then that field may be omitted from all JSON Requests and will be omitted
from JSON Responses. In the case of responses, the absence of an expected
field should be interpreted as 0
or empty.
Representation of whole numbers will appear in JSON without a decimal point.
Integers greater than 2^31
and less than -2^31
, while generally supported,
are technically Undefined Behavior by the JSON specification and thus may be
converted into floating point numbers by some implementations.
Sending JSON from one part of the software or service to another, and getting that JSON back from the software or service, does not guarantee the order of fields or the presence of any whitespace.
Although tabs, CR
, and LF
characters are technically allowable whitespace
in JSON, they are not allowed in Notecard Requests or Bodies and will never be
placed within Notecard Responses. The Notecard uses the
ndjson technique of new line-delimited json.
The Notecard JSON libraries do support UTF-8, but there may be language representation limitations due to the constraints of JSON within embedded systems.