Skip to content

users: explain a 403 on activities as limited access - #317

Merged
mfederowicz merged 1 commit into
mainfrom
users-not-open-403
Oct 30, 2026
Merged

mfederowicz merged 1 commit into
mainfrom
users-not-open-403

Conversation

@mfederowicz

Copy link
Copy Markdown
Owner

Changed

  • users -a activities: a 403 now ends with activities is limited access on Trakt and not available for this API app instead of a bare 403. On 2026-10-31 the live API answered following and friends with 403; on 2026-09-25 it answered 401. The contract (trakt-api 105e41f) now marks the route Limited Access for first-party apps only.

The 403 is handled in the activities handler only. The shared notOpenToAPIApps helper (401) stays as it was: on year_in_review_persona a 403 means VIP only, and the other routes that use the helper weren't checked for 403.

An AI assistant (Claude Code) wrote the change and test, resolved the rebase conflict with #316 and drafted this description.

Since 2026-10-31 Trakt answers users/{id}/{type}/activities with 403 (401 before); the contract
(trakt-api 105e41f) marks it limited to first-party apps. Reuse LimitedAccessMsg for it.
@mfederowicz
mfederowicz merged commit af0e0b3 into main Oct 30, 2026
6 checks passed
@mfederowicz
mfederowicz deleted the users-not-open-403 branch October 31, 2026 01:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant