Fetch a log by its ID in elmah.io
A documented elmah.io 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
Fetch a log by its ID.
- GETReads data · Logs
/v3/logs/{id}
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 elmah.io 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 elmah.io operations
- Create a new messagePOST · changes data
- Deletes a list of messages by logid and queryDELETE · changes data
- Create a new logPOST · changes data
- Create a new deploymentPOST · changes data
- Mark a list of messages as fixed by logid and queryPOST · changes data
- Create one or more new messagesPOST · changes data
- Create or update a translation between a minified JavaScript pathPOST · changes data
- Delete a message by its IDDELETE · changes data
Questions
- Can HumDay fetch a log by its id in elmah.io?
- Yes. This operation is published in elmah.io'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 elmah.io account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in elmah.io.
- 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 elmah.io account.
Where this came from
Read from a published API description for elmah.io at api.elmah.io/swagger/docs/v3. The description above is the provider’s own wording, not ours. Last published 2023-03-06.