scratchattach is a Scratch API wrapper with support for almost all site features. Created by TimMcCool.
The library allows setting cloud variables, following users, updating your profile, and so much more! Additionally, it provides frameworks that simplify sending data through cloud variables.
Documentation
Helpful resources
Report bugs by opening an issue on this repository. If you need help or guideance, leave a comment in the official forum topic. Projects made using scratchattach can be added to this Scratch studio.
Helpful for contributors
Contribute code by opening a pull request on this repository.
️Example usage
Set a cloud variable:
import scratchattach as sa
session = sa.login("username", "password")
cloud = session.connect_cloud("project_id")
cloud.set_var("variable", value)
Getting started
Installation:
Run the following command in your command prompt / shell:
pip install -U scratchattach
If this doesn't work, try running:
python -m pip install -U scratchattach
Logging in with username / password:
import scratchattach as sa
session = sa.login("username", "password")
login() returns a Session object that saves your login and can be used to connect objects like users, projects, clouds etc.
Logging in with a sessionId: You can get your session id from your browser's cookies. More information
import scratchattach as sa
session = sa.login_by_id("sessionId", username="username") #The username field is case sensitive
Cloud variables:
cloud = session.connect_cloud("project_id") # connect to the cloud
value = cloud.get_var("variable")
cloud.set_var("variable", "value") # the variable name is specified without the cloud emoji
Cloud events:
cloud = session.connect_cloud('project_id')
events = cloud.events()
@events.event
def on_set(activity):
print("variable", activity.var, "was set to", activity.value)
events.start()
Follow users, love their projects and comment:
user = session.connect_user('username')
user.follow()
project = user.projects()[0]
project.love()
project.post_comment('Great project!')
All scratchattach features are documented in the documentation.
1 maintainer
Release files for scratchattach 2.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| scratchattach-2.2.3.tar.gz | 127.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scratchattach-2.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 275.9 kB
Release files / scratchattach-2.2.3.tar.gz
| Download URL | scratchattach-2.2.3.tar.gz |
|---|---|
| Size | 127.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
125704462b5d9705117d36ba140058f6079e99dc904b8203c9b3286f8a0a40ca
|
|
BLAKE2b-256 checksum How to use checksums |
4a9e52e5c82546f918e77352093d1133e8dd5b13677d39614ad314b5dbd7201d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 28, 2026.
Transparency logRelease files / scratchattach-2.2.3-py3-none-any.whl
| Download URL | scratchattach-2.2.3-py3-none-any.whl |
|---|---|
| Size | 148.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4fd0986f6efed8b1f3eea738db907dbc9e66535fe6896f53ccb30fe479991e47
|
|
BLAKE2b-256 checksum How to use checksums |
8028e24fc51d232a5448c8edc88ee32579d11cd9e1fd5e5e25a1d2e5e1828464
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 28, 2026.
Transparency log
