# metricool/2.0.2/app/Http/Endpoints/RealtimeEndpoint.php

Metricool – Social media and site statistics, version 2.0.2. 107 lines.

- Page: https://pluginprobe.com/plugins/metricool/2.0.2/code/app/Http/Endpoints/RealtimeEndpoint.php
- Raw: https://pluginprobe.com/plugins/metricool/2.0.2/raw/app/Http/Endpoints/RealtimeEndpoint.php
- Modified: 2026-06-11T08:45:10+00:00

Line numbers below start at 1. Link to a line or a range by appending a fragment to the
page URL, for example `https://pluginprobe.com/plugins/metricool/2.0.2/code/app/Http/Endpoints/RealtimeEndpoint.php#L10-L20`.

```php
<?php

declare(strict_types=1);

namespace Metricool\Http\Endpoints;

use Exception;
use Metricool\Http\Endpoints\Responses\RealtimeResponse;
use Metricool\Http\Metricool\MetricoolApi;
use Metricool\Interfaces\SingleEndpointInterface;
use Metricool\Services\RealtimeService;
use Metricool\Traits\HasAllowlistControl;
use Metricool\Traits\HasRestAccess;

class RealtimeEndpoint implements SingleEndpointInterface
{
    use HasRestAccess;
    use HasAllowlistControl;

    public const ROUTE = 'realtime';

    public RealtimeService $service;
    public MetricoolApi $metricoolApi;

    public function __construct(RealtimeService $service, MetricoolApi $metricoolApi)
    {
        $this->service = $service;
        $this->metricoolApi = $metricoolApi;
    }

    /**
     * @inheritDoc
     */
    public function registerRoute(): string
    {
        return self::ROUTE;
    }

    /**
     * @inheritDoc
     */
    public function enabled(): bool
    {
        return $this->adminAccessAllowed();
    }

    /**
     * @inheritDoc
     */
    public function registerArguments(): array
    {
        return [
            'methods' => \WP_REST_Server::READABLE,
            'callback' => [$this, 'callback'],
            'middleware' => ['metricool:auth', 'metricool:blog_id'],
        ];
    }

    /**
     * Build the specific Realtime response for the endpoint. This is mainly
     * used in the plugin Dashboard. Building it server side prevents client-side complexity.
     */
    public function callback(\WP_REST_Request $request): \WP_REST_Response
    {
        try {
            $response = $this->buildResponse($request);
        } catch (Exception $e) {
            return $this->sendHttpErrorResponse(__('Failed to load Realtime data', 'metricool'), $e->getMessage(), $e->getCode());
        }

        return $this->sendHttpResponse($response);
    }

    /**
     * Build the specific Analytics response for the endpoint. This is mainly
     * used in the plugin Dashboard to reflect non-realtime statistics.
     * Building it server side prevents client-side complexity.
     * @throws Exception
     */
    private function buildResponse(\WP_REST_Request $request): array
    {
        $realtimeModule = $this->metricoolApi->realtime();

        // Get our data
        $sessions = $realtimeModule->sessions()->get();
        if (!isset($sessions['timeline'])) {
            throw new Exception('Session data is missing');
        }

        $values = $realtimeModule->current()->get();
        if (!isset($values['activeVisits'])) {
            throw new Exception('Visitors data is missing');
        }

        // Add the pageViews to the timeline and totals
        $this->service->addMetric('pageViews', __('Page views', 'metricool'), $sessions['timeline']);
        // Add visitors just to the totals
        $this->service->addTotals('visitors', __('Visitors', 'metricool'), $values['activeVisits']);

        $response = new RealtimeResponse();
        $response->setTotals($this->service->getTotals());
        $response->setTimelineData($this->service->getTimelineData());

        return $response->body();
    }
}

```