Skip to content

younify: send all_data as true and explain a 403 - #316

Merged
mfederowicz merged 1 commit into
mainfrom
younify-refresh-all-data
Oct 30, 2026
Merged

mfederowicz merged 1 commit into
mainfrom
younify-refresh-all-data

Conversation

@mfederowicz

Copy link
Copy Markdown
Owner

Fixed

  • younify -a refresh -all_data sent POST younify/users/refresh/<service_id>/all_data. The contract (trakt-api 28e57aa) wants .../<service_id>/true, so that's what we send now.

Changed

  • On 2026-10-31 Trakt answered younify -a connections with 403; on 2026-09-25 it answered 401. Both now print younify is not open to API apps yet and show which status Trakt sent.

Mock-tested only: younify answers 403 for API apps, so the -all_data path can't be checked live. Docs, API_COVERAGE findings and CHANGELOG are updated.

An AI assistant (Claude Code) triaged the contract change, wrote the fix and tests, and drafted this description.

The contract (trakt-api 28e57aa) wants POST younify/users/refresh/{service_id}/{true|false};
we sent the literal all_data segment. On 2026-10-31 Trakt answered younify with 403
instead of 401, so the not-open-to-API-apps message now covers both.
@mfederowicz
mfederowicz merged commit aa89f92 into main Oct 30, 2026
6 checks passed
@mfederowicz
mfederowicz deleted the younify-refresh-all-data 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