Map the caller's forwarded auth token to a userId

post/api/v2/internal/scheduledReports/identify

The scheduled-reports-service forwards the end user's auth headers verbatim; needsAuth validates them and populates req.user. This is the only identity step the scheduler cannot perform itself — token lookup, HMAC validation, and replay-protection all live in bgms.

200 Response

userId string required

400 Response

name string
Error code
context object required
Properties that apply to a specific error name
error string required
Human-readable error message
requestId string required
Client request id

401 Response

name string
Error code
context object required
Properties that apply to a specific error name
error string required
Human-readable error message
requestId string required
Client request id