Provide daily and manual trigger JSON export for sales and stats?

[MeisterAdebar]

Hi,

Not essential, but it would be nice to have the option to get revenue and statistics data as a JSON file, on a daily schedule and via a manual trigger.
Just a helpful addition if feasible—no pressure.

[developeregrem]

Hi, all endpoints of the statistic pages provide json output already. It's used to render the charts.
E.g.:
https://<host>/statistics/utilization/monthtly?objectId=all&monthStart=1&monthEnd=1&yearStart=2026&yearEnd=2026
You can use the developer console in the browser to see the requests.
Maybe it will be helpful already?

[MeisterAdebar]

This is really cool - it enables me to implement everything I had in mind ;)

Thanks a lot for your work...

[MeisterAdebar]

However, fetching the JSON endpoints seems to require an active browser session, as simple attempts via Basic Auth are being ignored or redirected.

In Perl, I am using the HttpUtils_NonblockingGet function. My current code looks like this, where I have to rely on manually copied cookies to prevent the Symfony security layer from redirecting the request to the login page:

Perl

sub TransformUtilization {
    # My attempt with Basic Auth (fails / is ignored):
    # my $auth = encode_base64("bli:bla!");
    
    # Current unstable workaround via browser session cookies:
    my $all_cookies = 'PHPSESSID=52d80051...; REMEMBERME=App.Entity.User...';
    
    HttpUtils_NonblockingGet({ 
        url => "https://fhempi/statistics/turnover/monthly?...",
        header => "Cookie: $all_cookies",
        callback => sub {
            return if $_[1];
            Debug $_[2]; 
        }
    });
}

Since these session cookies (especially the PHPSESSID) expire regularly, this integration is very high-maintenance.

After my first few attempts, I am a bit unsure if I simply failed to implement Basic Auth correctly on my end or if the endpoint is not configured to support it.

My question: Is there a recommended method for programmatic access (e.g., a dedicated API key / Personal Access Token), or would it be possible to implement token-based authentication (e.g., via Authorization: Bearer ) for the statistics exports?

[developeregrem]

Hi,
yes default session is valid for 30 minutes I guess and basic auth is not activated. At the moment only form login and passkeys are allowed. Due to security reasons basic auth will be not implemented, but I will add the api and authorization header on the roadmap.
In the meantime you can play a bit with the rememberme cookie. Just leave the phpsess cookie and use only rememberme. In my short tests it was working by requesting a json endpoint using the rememberme cookie only. The rememberme cookie is valid for one year by default.

[MeisterAdebar]

First of all, a big thank you for implementing the many change requests over the past weeks — that’s really not something to be taken for granted and is very much appreciated!

And yes: it works with only the rememberme cookie. Thanks.