Lookup SHA-1 in hashlookup CIRCL
A documented hashlookup CIRCL operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Lookup SHA-1.
- GETReads data · default
/lookup/sha1/{sha1}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which hashlookup CIRCL operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other hashlookup CIRCL operations
- Bulk search of MD5 hashes in a JSON array with the key 'hashes'POST · changes data
- Bulk search of SHA1 hashes in a JSON array with the 'hashes'POST · changes data
- Create a session key to keep search contextGET · reads data
- Info about the hashlookup databaseGET · reads data
- Return the top 100 of most queried valuesGET · reads data
- Return set of matching and non-matching hashes from a sessionGET · reads data
- Lookup SHA-256GET · reads data
- Return parents from a given SHA1GET · reads data
Questions
- Can HumDay lookup sha-1 in hashlookup CIRCL?
- Yes. This operation is published in hashlookup CIRCL's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my hashlookup CIRCL account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in hashlookup CIRCL.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your hashlookup CIRCL account.
Where this came from
Read from a published API description for hashlookup CIRCL at hashlookup.circl.lu/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.