Securitytrails integration

Quick start

Call Securitytrails from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Securitytrails's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "SECURITYTRAILS_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

End-users supply their own Securitytrails API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

12 actions exposed via the Securitytrails integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• SECURITYTRAILS_BULK_STATIC_ASSET_RULES
• SECURITYTRAILS_GET_COMPANY_ASSOCIATED_IPS
• SECURITYTRAILS_GET_DOMAIN
• SECURITYTRAILS_GET_DOMAIN_SSL
• SECURITYTRAILS_IP_SEARCH_STATISTICS
• SECURITYTRAILS_LIST_PROJECTS
• SECURITYTRAILS_PING
• SECURITYTRAILS_SCROLL
• SECURITYTRAILS_SEARCH_IPS
• SECURITYTRAILS_SQL_API_EXECUTE_QUERY
• SECURITYTRAILS_SQL_API_SCROLL_RESULTS
• SECURITYTRAILS_TEMP_SCRAPE_SECURITYTRAILS_USAGE