111 questions, answered from the documentation and linked back to it.
GET /event/{id}/streamingEndpoints returns the streaming endpoints for an event id. preStart and postEnd are optional and given in milliseconds, and expiry is optional and given in seconds. GET /event/{id}/true gets the event itself, and POST /event and POST /event/eventIngest both take an Event Push body.
GET /mediastore gets events by filter and takes its paging as nPerPage, the number of items per page, together with pageNumber. The same call requires fromDate and toDate as epoch time in milliseconds, tags, alarmType and hierarchyLevel, which is one of serviceprovider, customer, site, device or sensor. It also carries the flags eventVerified, fullPayload and showTechnicalEvents, and declares 200, 204, 401, 403 and 404.
POST /reports adds a report, GET /reports/{reportId} reads one, PUT /reports/{reportId} updates it and DELETE /reports/{reportId} deletes it. POST /reports/execute triggers a report or gets sample data to be used in the template, GET /reports/{reportId}/preview previews a report, and POST /reports/filter gets the report list with filtering, sorting and pagination. POST /reports/sendEmail sends email and is the only operation on this resource that also declares 500 Internal Server Error.
The Analytics Scheduler tab lists every configured analytics schedule in a table, one row per scheduled job, with the entity name, access level, analytic type, schedule time, and the site and device it applies to. It sits next to the Analytics tab in the navigation bar and is governed by the same permission, so if the Analytics permission is disabled for a user at that level, neither tab appears. At Service Provider level the table covers all schedulers across the whole hierarchy; at Customer, Site or Device level it shows only the schedulers within that level. The one row-level action available is Delete.
The Analytics tab lets you subscribe cameras to analytics but does not show which schedules are already running, so duplicate schedulers can accumulate silently — the same analytics job running several times at the same level, wasting processing resources and making configurations harder to manage at scale. The Analytics Scheduler table lists every scheduler including duplicates, so an administrator can spot redundant jobs and remove them manually. Deleting a scheduler here produces the same result as unsubscribing from the Analytics tab.
Send a HealthCheck report. GCXONE has three reporting surfaces: the live dashboard for your own team, HealthCheck reports as the primary customer deliverable, and alarm and operational reports for management and trend analysis. HealthCheck reports are timestamped, independent records of camera estate health written for non-technical stakeholders such as facility managers and security directors. The dashboard does not store historical data in a shareable format, so a dashboard screenshot must never be sent as a substitute.
No. Scheduled reports deliver automatically and the customer receives them as email attachments without needing GCXONE access. Schedules are configured under Settings then Reports, and the recommended cadence is a weekly HealthCheck report delivered Monday before 08:00 and a monthly alarm summary delivered on the first business day. Set these up for every active customer rather than waiting to be asked.
Genie is the built-in assistant inside GCXONE, sitting as a floating panel on the dashboard. It opens with five topic shortcuts — Spawn, Insights, Ticket Management, VPN Requests, and Device Setup and Troubleshooting — but the tabs are shortcuts rather than a requirement: you can type a question directly and Genie pulls the relevant data or options into the panel. Typical questions cover alarm summaries, ticket status, VPN requests, camera health and device troubleshooting. If Genie does not have the answer, it says so, and anything outside the platform's operational data goes to support.
No. Every action Genie prepares requires your confirmation before it is applied. Adding a device starts with choosing the device type, after which Genie prepares the setup and asks for approval, and only then is the device created and the standard configuration form opened for connection details such as IP, credentials and ports. Ticket replies are drafted and shown with the full action details for you to approve before sending, and closing a ticket runs through guided prompts. OpenVPN requests work the same way — Genie assembles the request from details like user email, ticket title, device IP and routing model, then presents it for review, edit or rejection before submission.
Test the stream using the manufacturer's own native client or software first. If it works there but not in GCXONE, the issue is likely platform-related; if it fails in both, the problem is with the device or the network. Review the device logs and the GCXONE platform logs for specific errors, and use HealthCheck to verify camera availability and stream accessibility. Before contacting support, gather the device type and model, firmware version, network configuration, and the error messages with their timestamps.
You can submit an inquiry through the NXGEN support portal contact form, giving your name, company, email, subject and message, and the team will get back to you. If you prefer a conversation you can book a meeting with the NXGEN team at a time that suits you. The office is at Technoparkstrasse 1, CH-8005 Zurich, Switzerland, reachable on +41 44 552 8850 or +41 44 552 8851, or by email at info@nxgen.io. Product news and announcements are posted on NXGEN Technology AG's LinkedIn page.
Ask the assistant for an answer drawn from the whole documentation, or open a ticket and talk to a person.
New features, fixes and integration updates for GCXONE, delivered to your inbox as they are released.
