Authenticated API Endpoint Reference
User, dealer, listing, media, messaging, and payment routes that require identity.
Supply a short-lived access token and verify ownership-sensitive responses.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
The audit classifies 111 methods as authenticated. The effective guard comes from global identity guards and explicit Public exceptions, not only from @ApiBearerAuth decoration.
| Check | Source-backed expectation |
|---|---|
| Scope | Documented authentication does not grant a user access to another installation or owner's records. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | curl -i -H 'Authorization: Bearer [access-token]' https://api.example.invalid/api/v1/me |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
curl -i -H 'Authorization: Bearer [access-token]' https://api.example.invalid/api/v1/me
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.