Search Reports
Answers ‘do reports already exist for these specific assets?’. Takes a batch of asset contents, normalizes each one the way ChainPatrol normalizes assets, and returns the reports covering them along with which of your assets each report matched. Use it to avoid filing a duplicate before calling POST /report/create. To browse or filter an organization’s reports instead — by status, asset type, brand, date, review state — use GET /organization/reports, which returns the full report records with pagination.
Overview
Search for existing reports within your organization by asset contents. Use this to check whether a report already exists before creating a new one with Report Create.Authorizations
Your API key. This is required by most endpoints to access our API programatically. Reach out to us at support@chainpatrol.io to get an API key for your use.
Body
Asset contents to look up — URLs, handles, addresses. Each is normalized the way ChainPatrol normalizes assets, so https://Bad.Site/ matches a report holding the canonical form.
Organization slug. Optional for organization-scoped API keys, which resolve the organization from the key itself. Required when your credentials can reach more than one organization.
Maximum number of reports to return, newest first. Defaults to 50, maximum 100. Compare with totalCount to tell whether the results were truncated.
1 <= x <= 100