Structured hours. Explicit fields.

Keep dates, numbers and employee identities explicit. JSON gives technical teams a structured file route into and out of review.

Start using timepilot Explore JSON

Synthetic JSON input example

{
  "rows": [
    {
      "employeeName": "Jamie Example",
      "employeeCode": "0017",
      "date": "2026-10-05",
      "start": "07:00",
      "end": "15:30",
      "breakMinutes": 30,
      "custom": {}
    }
  ]
}

Example data only. This illustrates structured input, not a universal payroll export template.

For teams with a structured data workflow.

A prepared data file

Use an array of work records, or an object containing a rows array. The structured reader handles documented fields directly; a missing value or unresolved Employee still needs a decision.

Reviewed records downstream

Export eligible work as JSON for a controlled downstream process. Agree the receiving schema and validate the file before using it. A JSON file export does not establish a public API or an automatic payroll connection.

Illustrative adviser desk with separate payroll folders. — Illustrative workplace scene

Keep the schema explicit.

Use an array of records or { rows: [...] } for structured input. Other JSON envelopes need conversion to the supported shape.
Use documented field names. Dates and times are strings in YYYY-MM-DD and HH:MM form; breakMinutes and totalHours use numeric values or null where permitted.
Company-defined extra fields belong in the custom object. Values must match the configured field definitions and supported scalar types.
Preserve employeeCode alongside employeeName where available. A matching-looking name does not replace an explicit Employee identity decision.
Validate syntax and values before upload. timepilot’s import shape and the receiving system’s export requirements may differ.

The format changes. The review stays.

Bring the source
Import supported records and keep the original values available for comparison.
Resolve and approve
Match Employees, correct exceptions and record the approval your Company requires.
Export eligible work
Choose the file format and check it against the receiving system before completing the hand-off.

JSON questions, answered.

Can I send an object with a rows property?

Yes. Structured input accepts a root array or an object with a rows array. Each work record must use the documented fields and value types.

Where do extra fields go?

Use the custom object for fields defined by your Company. Unrecognised or invalid field names and values need correction rather than silent acceptance.

Does JSON mean an API integration?

No. This guide describes JSON files. API access and direct payroll connections have their own access, schema and activation requirements.

Need another integration?

Tell us what you use and how you’d like it to work with timepilot. We’ll see whether we can build a connection for you.