KWkwx·Dec 19, 2013
Already done months ago.. ?
https://github.com/tlack/snaphax
In Reverse engineering Snapchat to store filestlack
snaphax
PHP2012–2013
tlack / snaphax
snaphax
A PHP library to use the Snapchat API
6Distinct people
7Mentions
0Explicit recommenders
268GitHub stars
What to know before exploring
What it is
A PHP library to use the Snapchat API
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month7 dated mentions
Observed mentions: 2012-12-31 21:18:12 UTC to 2013-12-19 05:35:05 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Dec 2012 | 2012-12-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 1 | 1 | 0 |
| Jan 2013 | 2013-01-01 00:00:00 UTC | 2013-02-01 00:00:00 UTC | 1 | 0 | 1 |
| Feb 2013 | 2013-02-01 00:00:00 UTC | 2013-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2013 | 2013-03-01 00:00:00 UTC | 2013-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2013 | 2013-04-01 00:00:00 UTC | 2013-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2013 | 2013-05-01 00:00:00 UTC | 2013-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2013 | 2013-06-01 00:00:00 UTC | 2013-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2013 | 2013-07-01 00:00:00 UTC | 2013-08-01 00:00:00 UTC | 2 | 1 | 1 |
| Aug 2013 | 2013-08-01 00:00:00 UTC | 2013-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2013 | 2013-09-01 00:00:00 UTC | 2013-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2013 | 2013-10-01 00:00:00 UTC | 2013-11-01 00:00:00 UTC | 1 | 0 | 1 |
| Nov 2013 | 2013-11-01 00:00:00 UTC | 2013-12-01 00:00:00 UTC | 1 | 0 | 1 |
| Dec 2013 | 2013-12-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
7 sourcesSnaphax, simple PHP class that connects and uses the Snapchat API - https://github.com/tlack/snaphax
Would assume snpcht.com uses it.
In Show HN: SnpCht.com, a site that lets you secretly save your unread snapchatsUses https://github.com/tlack/snaphax, I assume?
In Show HN: Snapchan - the Snapchat-only image boardThis is completely off-topic, but I'm curious. How does one go about "reverse engineering" a protocol like what Snapchat uses? Do you just listen in on the bits that the phone sends (say, with Wireshark) and kind of guess and poke at it to see what each part does?
Edit: after some research (like reading TFRepo), I found some links mentioned that give some info in case anyone else is curious too.
http://adamcaudill.com/2012/06/16/snapchat-api-and-security/
https://github.com/tlack/snaphax#motivation-and-development-...
In Ask HN: Take down my reverse-engineered Snapchat lib because they asked?Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
A few months ago, I spent a couple days reverse engineering the Snapchat protocol and wrote a quick and dirty library to use it in your own PHP apps:
https://github.com/tlack/snaphax
Today Snapchat has written me requesting that I take it offline:
Hi Thomas,
I'm writing to ask that you remove Snaphax from github
and no longer publish or distribute it. Snapchat does
not permit third party software to access our API and
we consider Snaphax to be an unlawful circumvention
device under 17 U.S.C. § 1201(a)(1).
Please confirm that it has been removed by end of day
Monday, July 22nd.
Thank you,
Micah Schaffer
Snapchat, Inc.
I haven't had much time to really finish Snaphax (and I doubt I ever will) but I strongly support the idea that third party software should be able to interact with the service
Read the rest
s I use every day.
I am under the impression that reverse engineering is still protected under fair use doctrines. Is this the case? How should I respond, if at all?
api.snapchat.com is currently a CNAME to feelinsonice-hrd.appspot.com .
Apparently the current API has been reverse-engineered very recently [1], with an alternate implementation publicly available [2].
Not good considering the nature of the app, perhaps there are some backwards-incompatible changes in the works?
[1] http://adamcaudill.com/2012/12/31/revisiting-snapchat-api-an...
[2] https://github.com/tlack/snaphax
In Api.snapchat.com redirects to Google.comSnaphax: connect to the undocumented Snapchat API (PHP)
1 points · Open discussion