Macrometa Prerender History API
The Prerender History API from Macrometa — 2 operation(s) for prerender history.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/macrometa-prerender-history-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Macrometa API Reference Activity Metrics Prerender History API
version: 0.17.17
description: API reference for the Macrometa Global Data Network.
license:
name: Macrometa License, Version 2.0
servers:
- url: https://api-play.paas.macrometa.io
description: GDN API
host: api-play.paas.macrometa.io
security:
- ApiKeyAuth: []
- BearerAuth: []
tags:
- name: Prerender History
paths:
/api/prerender/v1/history/render:
get:
summary: Get render history data
tags:
- Prerender History
description: Returns historical data for web metrics, with time-range filtering and optional response code criteria. This endpoint requires the from and to query parameters, indicating the time range as epoch seconds. Optional filters include responseCode for HTTP status, and pagination controls through limit and offset. Data can be optionally scoped to a specific origin if the origin path parameter is included. The response comprises an array of historical records, detailing bytes sent, response time, device type, and response codes. Authentication is handled via the customerId header.
parameters:
- schema:
type: number
in: query
name: from
required: true
description: Timestamp (in seconds) used as the initial time for filtering.
- schema:
type: number
in: query
name: to
required: true
description: Timestamp (in seconds) used as the final time for filtering.
- schema:
type:
- number
- string
in: query
name: responseCode
required: false
description: Response code for filtering. It can be a specific response code or a range value, e.g., 200-310.
- schema:
type: string
in: query
name: responseTime
required: false
description: Response time range in seconds for filtering, e.g., 2-10.
- schema:
type: number
minimum: 1
default: 100
maximum: 100
in: query
name: limit
required: false
description: Limit for results.
- schema:
type: number
default: 0
in: query
name: offset
required: false
description: Offset for results.
- schema:
type: string
in: header
name: x-photoniq-customerid
required: true
description: Customer unique identifier.
responses:
'200':
description: Render history fetched successfully.
content:
application/json:
schema:
type: array
description: Render history fetched successfully.
items:
type: object
properties:
timestamp:
type: number
description: The time at which the event occurred, represented as a Unix timestamp.
origin:
type: string
format: uri
description: The URL of the origin server from which the request was sent.
path:
type: string
description: The specific path on the server accessed by the request.
bytesSent:
type: number
description: The total number of bytes sent in the response.
responseTime:
type: number
description: The time taken to receive a response from the server, measured in milliseconds.
isMobile:
type: boolean
description: Indicates whether the request was made from a mobile device.
responseCode:
type: number
description: The HTTP status code returned by the server in response to the request.
example:
- timestamp: 1672543000
origin: https://www.origin.com
path: /terms
bytesSent: 362414
responseTime: 1000
isMobile: false
responseCode: 200
- timestamp: 1672542000
origin: https://www.origin.com
path: /terms
bytesSent: 362056
responseTime: 1500
isMobile: false
responseCode: 200
'400':
description: Bad request.
content:
application/json:
schema:
type: object
description: Bad request.
properties:
status:
type: string
description: Error status.
message:
type: string
description: Error message.
required:
- status
- message
example:
status: ERROR
message: Header x-photoniq-customerid is required.
'500':
description: Internal server error.
content:
application/json:
schema:
type: object
description: Internal server error.
properties:
status:
type: string
description: Error status.
message:
type: string
description: Error message.
required:
- status
- message
example:
status: ERROR
message: Internal server error.
/api/prerender/v1/history/render/{origin}:
get:
summary: Get render history data by origin
tags:
- Prerender History
description: Returns historical data for web metrics, with time-range filtering and optional response code criteria. This endpoint requires the from and to query parameters, indicating the time range as epoch seconds. Optional filters include responseCode for HTTP status, and pagination controls through limit and offset. Data can be optionally scoped to a specific origin if the origin path parameter is included. The response comprises an array of historical records, detailing bytes sent, response time, device type, and response codes. Authentication is handled via the customerId header.
parameters:
- schema:
type: number
in: query
name: from
required: true
description: Timestamp (in seconds) used as the initial time for filtering.
- schema:
type: number
in: query
name: to
required: true
description: Timestamp (in seconds) used as the final time for filtering.
- schema:
type:
- number
- string
in: query
name: responseCode
required: false
description: Response code for filtering. It can be a specific response code or a range value, e.g., 200-310.
- schema:
type: string
in: query
name: responseTime
required: false
description: Response time range in seconds for filtering, e.g., 2-10.
- schema:
type: number
minimum: 1
default: 100
maximum: 100
in: query
name: limit
required: false
description: Limit for results.
- schema:
type: number
default: 0
in: query
name: offset
required: false
description: Offset for results.
- schema:
type: string
minLength: 1
example: www.origin.com
in: path
name: origin
required: true
description: Origin hostname.
- schema:
type: string
in: header
name: x-photoniq-customerid
required: true
description: Customer unique identifier.
responses:
'200':
description: Render history fetched successfully.
content:
application/json:
schema:
type: array
description: Render history fetched successfully.
items:
type: object
properties:
timestamp:
type: number
description: The time at which the event occurred, represented as a Unix timestamp.
origin:
type: string
format: uri
description: The URL of the origin server from which the request was sent.
path:
type: string
description: The specific path on the server accessed by the request.
bytesSent:
type: number
description: The total number of bytes sent in the response.
responseTime:
type: number
description: The time taken to receive a response from the server, measured in milliseconds.
isMobile:
type: boolean
description: Indicates whether the request was made from a mobile device.
responseCode:
type: number
description: The HTTP status code returned by the server in response to the request.
example:
- timestamp: 1672543000
origin: https://www.origin.com
path: /terms
bytesSent: 362414
responseTime: 1000
isMobile: false
responseCode: 200
- timestamp: 1672542000
origin: https://www.origin.com
path: /terms
bytesSent: 362056
responseTime: 1500
isMobile: false
responseCode: 200
'400':
description: Bad request.
content:
application/json:
schema:
type: object
description: Bad request.
properties:
status:
type: string
description: Error status.
message:
type: string
description: Error message.
required:
- status
- message
example:
status: ERROR
message: Header x-photoniq-customerid is required.
'500':
description: Internal server error.
content:
application/json:
schema:
type: object
description: Internal server error.
properties:
status:
type: string
description: Error status.
message:
type: string
description: Error message.
required:
- status
- message
example:
status: ERROR
message: Internal server error.
components:
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: Authorization
description: 'Provide an API Key to the `Authorization` header, prefixed with "apikey".
Example: `Authorization: apikey <key>`'
BearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: 'Provide a JSON Web Token (JWT) to the `Authorization` header, prefixed with "bearer".
Example: `Authorization: bearer <jwt>`'