A small JSON example you can adapt

JSON represents data using objects, arrays, strings, numbers, booleans and null. Object keys and string values use double quotes. A comma separates members, but the final member must not have a trailing comma in strict JSON. Comments are not part of the standard JSON syntax, even though some configuration formats accept them. The example below describes an invented task with a nested owner and a list of labels. Replace the sample values with non-sensitive test data. Keep values such as postal codes and identifiers as strings when leading zeros matter. A number is appropriate for a quantity, but it is not automatically the right representation for every sequence of digits. Use the JSON formatter to check syntax and make nesting easier to inspect. Formatting changes whitespace, not the meaning of a field. It does not prove that a document satisfies an API schema or that the values are acceptable to a particular service. Validate those requirements against the API documentation separately. When reporting an integration problem, reduce the document to the fields needed to reproduce the issue. Remove tokens, secrets and customer details before sharing it. Preserve the distinction between a missing property, an empty string and null if the receiving service treats them differently. Large integers deserve special care because some language runtimes cannot represent every integer exactly. Do not casually convert identifiers into numbers. Pastzo formatting preserves numeric text rather than passing it through a floating-point round trip.

{
  "task": "Prepare a handover",
  "completed": false,
  "owner": {"name": "Example user", "reference": "00042"},
  "labels": ["documentation", "team"],
  "estimateMinutes": 30,
  "dueAt": null
}