/v1/meta
Algorithms & limits
Essayez-le en direct
10 appels gratuits par jour — sans inscription, sans clé API. Passe par la passerelle oanor.
Ça marche. Récupérez une clé API et utilisez-la dans votre projet.
Obtenez une clé APIExtraits de code
curl "https://api.oanor.com/sri-api/v1/meta" \ -H "x-oanor-key: oanor_test_..."
await fetch("https://api.oanor.com/sri-api/v1/meta", {
headers: { "x-oanor-key": "oanor_test_..." }
});
$ch = curl_init("https://api.oanor.com/sri-api/v1/meta");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);
import requests
requests.get(
"https://api.oanor.com/sri-api/v1/meta",
headers={"x-oanor-key": "oanor_test_..."}
)
Exemple de réponse
Une réponse réelle de ce endpoint, capturée lors du dernier contrôle de santé.
{
"data": {
"note": "Generate Subresource Integrity (SRI) hashes for any web asset so browsers can verify that a CDN-hosted script or stylesheet has not been tampered with. /v1/generate?url=https://code.jquery.com/jquery-3.7.1.min.js fetches the asset and returns its sha256, sha384 and sha512 SRI hashes, the chosen integrity value (sha384 by default; pass ?algorithm=), the asset's size and content type, and a ready-to-paste <script> or <link> tag complete with the integrity and crossorigin attributes. /v1/verify?url=...&integrity=sha384-... re-fetches the asset and tells you whether it still matches a known integrity string — catching silent CDN changes or supply-chain tampering. The request is made server-side; private/internal targets are refused (SSRF-guarded). Built for securing third-party scripts, supply-chain hardening, build pipelines and CSP/SRI compliance. A Subresource Integrity generator/verifier — distinct from raw cryptographic hashing of input data (hash), the HTTP security-header grader (secheaders) and the SSL/TLS certificate check (sslcheck). No key, no cache.",
"endpoints": [
"/v1/generate",
"/v1/verify",
"/v1/meta"
],
"max_bytes": 10485760,
"algorithms": [
"sha256",
"sha384",
"sha512"
],
"default_algorithm": "sha384"
},
"meta": {
"timestamp": "2026-06-01T23:40:48.810Z",
"request_id": "3b85f858-0a8d-4452-bbb6-9ab39ed78d32"
},
"status": "ok",
"message": "Meta retrieved",
"success": true
}