v1.5.5WebsiteLatest
1 min read

Log Status Code Filtering & Lookup by Log ID

The logs endpoint now honours explicit HTTP status codes, can find a single entry by its ID, and rejects an unrecognized status filter instead of quietly returning everything.

#What's Changed

  • [Fix] The logs endpoint now filters by explicit HTTP status codes (for example status=200 or status=404, and several at once). Only the keywords success and error were implemented, so a request for a specific code was silently dropped and the response came back unfiltered — which reads as “nothing was excluded” rather than as a broken filter.
  • [Fix] Log search now matches an entry's own ID, including by prefix. Without it there was no way to look up a single log entry, so the CLI's apivault logs get <id> could never resolve one.
  • [Improvement] An unrecognized status filter is rejected with 400 and a message naming the accepted values, rather than being ignored. Multiple status values are combined as a match-any set, so success and error together still return everything.
  • [Improvement] The project logs and log-filters endpoints resolve their path segment as a project ID or slug, matching the X-Project-Id contract, and select only the membership fields they use.