How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Matomo Tracking API (matomo.php entrypoint)

The Matomo Tracking API — the server-side ingest entrypoint at /matomo.php that records pageviews, events, goals, ecommerce orders, site searches and content interactions. It is the counterpart to the JavaScript tracking client and the target of every first-party tracking SDK. On Matomo Cloud the tracking endpoints are explicitly exempt from the API rate limits that apply to reporting. There is no MCP tool for tracking: agents can read Matomo analytics but cannot write tracking events.

Matomo Tracking API (matomo.php entrypoint) is one of 61 APIs that Matomo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Analytics, Tracking, Event, Ingest, and Server-Side. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 2 operations across 1 path, and defines 1 schema. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against a single base URL, https://{matomo_host}.

2 operations 1 paths 1 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://{matomo_host}/matomo.php
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Matomo Tracking API (matomo.php entrypoint) declares 1 security scheme for authenticating requests. An API key is passed in the query as token_auth (TokenAuth). By default, every request must be authenticated.

  • TokenAuth — Matomo auth token created in Administration Personal Security Auth tokens. May be passed as a query parameter or, preferably, in the POST body.

Paths & Operations 2

Across 1 path, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Matomo.php 2
GET
/matomo.php
Submit a single tracking request (querystring)
trackEventGet 51 params → 200
POST
/matomo.php
Submit a single tracking request or a bulk batch
trackEventPost body → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is BulkRequest (2 properties). Each schema is shown below with its type and property counts.

BulkRequest
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

matomo-matomo-php-api-openapi.yml Raw ↑

Other APIs Matomo publishes across the network.

Matomo Live API
Matomo Goals API
Matomo Segments API
Matomo Reporting API (index.php entrypoint)
Matomo SitesManager API
Matomo TagManager API
Matomo UsersManager API
Matomo CrashAnalytics API
Matomo HeatmapSessionRecording API
Matomo FormAnalytics API
Matomo Referrers API
Matomo Funnels API
Where this information came from

This is an independent, third-party profile of Matomo Tracking API (matomo.php entrypoint), published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.