Public Data Extractor for Meetup.com
Do you organise an event on meetup.com? Would you like basic details of the event to be available as Open Data for reuse elsewhere?
(Public details only - this does NOT extract any information about the people attending your events.)
This is an unofficial tool not endorsed by Meetup.com - use at your own risk!
Install
pip install public-data-extractor-for-meetup-com
Configure
Log into https://www.meetup.com/ and go to "View Profile".
You'll be at a URL like: https://www.meetup.com/members/123456789/
That number is your member ID.
Set it as the environmental Variable MEETUP_COM_AUTHORIZED_MEMBER_ID
Go to https://www.meetup.com/graphql/oauth/list/ and create a new API client.
Set the Client Key as the environmental Variable MEETUP_COM_YOUR_CLIENT_KEY
Create a new signing key for the client (Make sure you save the private certificate as you won't see it again!)
Set it as the environmental Variable MEETUP_COM_PRIVATE_SIGNING_KEY
Run
Run:
python -m publicdataextractorformeetupcom extractgroup your_group_slug output_directory
The output directory will then hold files with public information that you can publish.
Run & Host on GitHub
You can run this automatically and host it on GitHub.
Make a new public GitHub repository, selecting the "Add Readme" option.
In settings, Secrets and Variables, Actions, add the following repository secrets:
- MEETUP_COM_AUTHORIZED_MEMBER_ID
- MEETUP_COM_YOUR_CLIENT_KEY
- MEETUP_COM_PRIVATE_SIGNING_KEY
The values should be as described in the "Configure" section above.
In settings, Secrets and Variables, Actions, add the following repository variables:
- MEETUP_COM_GROUP_URL_NAME - The group you want to import, from the https://www.meetup.com/group_name/ URL. Just the
group_namepart.
Go to Settings, GitHub pages and change the source to "GitHub Actions".
Create a file .github/workflows/build.yml and copy the contents of the github_workflow.yml file into it. Commit this file and push it to GitHub.
Go to Actions in the repository, and make sure the first run finishes successfully. It can take a few minutes for it to actually start.
You should now be able to view out.json on your GitHub pages URL. (Go back to Settings, GitHub pages to find the URL.)
For Developers
The GraphQL Playground at https://www.meetup.com/graphql/playground/#graphQl-playground is very handy to explore.
Metadata
Release files for public-data-extractor-for-meetup-com 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| public_data_extractor_for_meetup_com-0.2.1.tar.gz | 6.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| public_data_extractor_for_meetup_com-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.0 kB
Release files / public_data_extractor_for_meetup_com-0.2.1.tar.gz
| Download URL | public_data_extractor_for_meetup_com-0.2.1.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2aa817e0b0822d949a8b2ffdc7fa4a7da1ea43222e0241568cba2c1e4206162
|
|
BLAKE2b-256 checksum How to use checksums |
0e15f972ce5c857be182f31e68a658a6f15ab7e61fbc9851ea76ebb46ca83ddf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 7, 2026.
Transparency logRelease files / public_data_extractor_for_meetup_com-0.2.1-py3-none-any.whl
| Download URL | public_data_extractor_for_meetup_com-0.2.1-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2f2a728f658253cf5867fb2b63c0715d7ced87a4bfe024e29c09816a2cddf08
|
|
BLAKE2b-256 checksum How to use checksums |
cc9f2432468597727a4364a30d1e8245f1c3ccc2fdc72e0aeb54cec9bdd6a2ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 7, 2026.
Transparency log