Hello,

Since the transition to the Censys Platform, it appears that multiple HTTP URIs can now be returned for a single IP and port.
However, the API response alone doesn’t seem to indicate which HTTP URI actually matched the query condition.

Although the "matched_services" field includes the port number that matched the query, it’s unclear which specific URI within that port satisfied the query.

Here’s an example for reference:

I’m using the following API endpoint and query with the Censys Platform API:

• API endpoint: https://api.platform.censys.io/v3/global/search/query

• Query: host.services.endpoints.http.body:"xxx" (using a specific keyword in practice)

In the API response, the "matched_services" field shows the port number that matched the query.

However, within the port listed in "matched_services", multiple HTTP URIs (for example: "/", "/login", "/robots.txt", etc.) can appear, and it seems that the API response does not indicate which specific HTTP URI actually matched the query condition.

In this case, although several HTTP URIs were returned for the same port, only the response for the root path "/" matched the query.

Is there any way to determine which HTTP URI matched the query from the API response?
If not, are there any recommended workarounds or best practices to identify the matched URI?

Thank you!