CEcensys
Global Data

Get web property event history

Changed on

Retrieve event history for a web property. Web properties are identified using a combination of a hostname and port joined with a colon, such as platform.censys.io:80. URL-encode the colon when used in the path (e.g. platform.censys.io%3A80).

get/v3/global/asset/webproperty/{webproperty_id}/timeline

Request

  • Base URL
    https://api.platform.censys.io
  • URL
    https://api.platform.censys.io/v3/global/asset/webproperty/{webproperty_id}/timeline
  • Auth
    HTTP bearer

Path parameters

webproperty_idstring required

A web property identifier, such as platform.censys.io:80. URL-encode the colon when used in the path (e.g. platform.censys.io%3A80).

Example:platform.censys.io:80

Query parameters

organization_idstring uuid

The ID of a Censys organization to associate the request with. If omitted, the request will be processed using the authenticated user's free wallet where applicable. See the Getting Started docs for more information.

Example:11111111-2222-3333-4444-555555555555
start_timestring date-time required

Start time of the web property timeline. Equivalent to the To field in the event history UI. This must be the timestamp closest to the current time. For example, if you want events from January 1, 2025 to the start of January 2, 2025, input the January 2 timestamp here. Must be a valid RFC3339 string. Ensure that you suffix the date with T00:00:00Z or a specific time.

Example:2025-01-02T00:00:00Z
end_timestring date-time required

End time of the web property timeline. Equivalent to the From field in the event history UI. This must be the timestamp furthest from the current time. For example, if you want events from January 1, 2025 to the start of January 2, 2025, input the January 1 timestamp here. Must be a valid RFC3339 string. Ensure that you suffix the date with T00:00:00Z or a specific time.

Example:2025-01-01T00:00:00Z

Headers

X-Organization-IDstring uuid

The ID of a Censys organization to associate the request with. If omitted, the request will be processed using the authenticated user's free wallet where applicable. See the Getting Started docs for more information. Note: The header parameter is supported for atypical use cases; we recommend always providing this field via the query parameter.

Example:11111111-2222-3333-4444-555555555555

Response

OK

Changes