> ## Documentation Index
> Fetch the complete documentation index at: https://api.veda.net/llms.txt
> Use this file to discover all available pages before exploring further.

# System Status

You can check the real-time status of our services at [status.veda.net](https://status.veda.net).

## Known Issues

<AccordionGroup>
  <Accordion title="Request for multiple persons with no custom field error out">
    If you request multiple persons and there are no custom fields, or the api doesn't have permission to read any custom fields, the request will fail with a 500 error. To work around this, grant the API permission to read at least one custom field.
  </Accordion>
</AccordionGroup>

<Check>
  Resolved

  <AccordionGroup>
    <Accordion title="customFields are empty">
      `customFields` are [now returned](/help/changelog#24-march-2026) for endpoints that return multiple results. Not only if one person is queried.
    </Accordion>

    <Accordion title="Requests with modifiedSince include empty objects">
      If the data for a non-primal payroll employment changed, the person's endpoint returned an empty object. The data point [is now excluded](/help/changelog#24-march-2026).
    </Accordion>

    <Accordion title="Time bookings day unit is null">
      The `unit` field of the main time booking object was always null. The day sums are always returned in hours and minutes. This field [has been removed](/help/changelog#14-november-2025).
    </Accordion>

    <Accordion title="time-bookings endpoint is not available">
      We accidentally named the `time-booking` endpoint `timebookings`. The url [has been corrected](/help/changelog#14-november-2025).
    </Accordion>

    <Accordion title="additionalAddressInfo is null">
      `additionalAddressInfo` is [now also populated](/help/changelog#14-november-2025) for endpoints that return multiple results, not just those that return one person.
    </Accordion>
  </AccordionGroup>
</Check>