Skip to content
Discussion options

You must be logged in to vote

Thank you very much for your question, @ricardocuritiba — I truly appreciate your interest in the project!

You're absolutely right to bring this up — I realize now that I missed including a clear instruction on how to obtain the required session token (connect.sid). Since Substack doesn’t offer an official API or SDK for authentication, the only current method is to manually extract this token from your browser after logging into your account.

This token is stored in your browser cookies and acts as a session identifier that Substack uses to confirm you’re authenticated. Because of its sensitive nature, it’s very important to treat this value like a password: do not share it with anyone, …

Replies: 6 comments 5 replies

Comment options

You must be logged in to vote
1 reply
@ricardocuritiba
Comment options

Answer selected by jakub-k-slys
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@jakub-k-slys
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
3 replies
@sabarinathan1611
Comment options

@jakub-k-slys
Comment options

@sabarinathan1611
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants