Discontinued

This API no longer responds. Our last check on 2026-07-31 found no working endpoint — the service appears to have shut down or moved. The documentation, code samples and score below are kept for reference only; do not build against this API. See working Security APIs →

Spyse API

Security / API Key Intermediate HTTPS

0 F

Metadata Score Metadata estimate · not endpoint-tested

Visit Official Site Compare Alternatives

Overview

Spyse (now part of SecurityTrails) is an internet asset search engine that provides comprehensive data on domains, IPs, SSL certificates, and autonomous systems. It is designed for attack surface management and security research, letting you enumerate an organization's internet-facing infrastructure. Note: Spyse has been integrated into SecurityTrails, so check SecurityTrails for the latest API access.

Beginner Tip

If you find that Spyse API endpoints return errors, check the SecurityTrails documentation as Spyse was acquired and merged into SecurityTrails in 2022.

Available Data

The kind of data this API exposes, based on its documentation. We could not call the endpoint to confirm the exact field names.

Spyse data via REST API

Example Response

Illustrative shape only — we were not able to call this endpoint (it requires credentials or exposes no public sample URL), so the fields below show the kind of data this API returns rather than a recorded response.

JSON Response · Illustrative

{
  "status": "success",
  "data": {
    "result": "Data from Spyse",
    "description": "Access data on all Internet assets and build powerful attack surface management applications",
    "timestamp": "2025-01-15T10:00:00Z"
  }
}

Field Reference

data Top-level container for the queried entity's details.

data.items List of matching records returned for the search query.

context Pagination context including total_count and page information.

data.items[].name Domain or hostname for this result entry.

data.items[].dns_records Current DNS records associated with the domain.

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request

const url = "https://api.spyse.com/v4/data/domain/details?domain=example.com";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "X-API-Key": "YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

401 Unauthorized The Bearer token is missing or the account credentials are invalid.

✓ Obtain a valid API token from your Spyse/SecurityTrails account and include it as Authorization: Bearer YOUR_API_KEY.

Endpoint returns 404 or service unavailable Spyse was acquired by SecurityTrails in 2022 and its standalone API may no longer be active.

✓ Migrate to the SecurityTrails API (api.securitytrails.com) which offers equivalent domain and IP intelligence features.

Quota exceeded error Free and trial accounts have limited query credits.

✓ Check your remaining credits in the dashboard and use targeted queries rather than broad scans to conserve quota.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

How is this scored? →