Skip to content

fix: get_group_metadata called a non-existent endpoint (v0.1.2) - #12

Merged
OussemaFr merged 1 commit into
mainfrom
fix/group-metadata-endpoint
Oct 5, 2026
Merged

OussemaFr merged 1 commit into
mainfrom
fix/group-metadata-endpoint

Conversation

@OussemaFr

Copy link
Copy Markdown
Member

Bug

get_group_metadata() (sync and async) called GET /facebook/groups/metadata. The API has no such route: the live API returns 404, and endpoints.json has 50 routes, none of them groups/metadata. Every call failed.

Fix

  • Both methods now call /facebook/groups/details and return its raw JSON, so existing code keeps working instead of 404ing.
  • They emit a DeprecationWarning pointing to get_group_details() (typed GroupInfo). Removal is planned for 0.2.0.
  • README no longer advertises the method.

Release

  • Bumps to 0.1.2, with a CHANGELOG entry.
  • Releasing also refreshes the PyPI page, which still shows the 0.1.1 README (JS/Go "coming soon", PHP, endpoint count).
  • After merge, git tag v0.1.2 && git push --tags triggers release.yml (Trusted Publishing).

Tests

  • 2 new tests (sync + async): the method hits /groups/details, warns, and returns the data.
  • Locally: ruff check, ruff format --check (ruff 0.16.10, same as CI), mypy socialapis tests and pytest (35 passed) all pass.

The API has no /facebook/groups/metadata route, so get_group_metadata()
returned 404 on every call. It now calls /facebook/groups/details and
returns the raw JSON, with a DeprecationWarning pointing to
get_group_details(). Removal planned for 0.2.0.

Bumps to 0.1.2 so PyPI also picks up the README fixes merged since 0.1.1.
@OussemaFr
OussemaFr merged commit 7c971c3 into main Oct 5, 2026
6 checks passed
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