Jeff the Giraffe
Jeff fetches his daily messages from a JSON file that contains:
number(int) The ID of Jeff's message. This number will go up by 1 each time it changes.
use_image(boolean) True if a Jeff image is present, false if not.
image(string) The file name of Jeff's image. (Ex: "jeffhearts.gif" would direct to empanadas.io/Content/Images/Jeff/jeffhearts.gif)
message(string) The message Jeff will use! (Note, this will sometimes contain Unicode/HTML tags)
button(boolean) True if there is a clickable button under Jeff, false if not.
button_text(string) The text displayed on the button if above is true.
button_href(string) The link that the button points to.
button_target(string) Usually set to
_blankto open in a new tab. Tells browser how to open link.
time(string) The time as a string from the initial post.
timestamp(long) The time from the initial post as a long.
Current Message Endpoint:https://empanadas.io/api/v1/jeff
All Messages Endpoint:
Need all of jeffs messages?https://empanadas.io/api/v1/jeff_history
The JSON formatting for the
jeff_history endpoint works by using the message ID's at the start of each path. The
timestamp argument kept outside of the ID scope.
Empanadas.io can return a JSON file that sums up all data from all accounts.
result(boolean) A true/false if the database/request went successful.
- Data The data from all member accounts combined
Total_PeppersAll users current peppers + spent peppers.
Total_SpinsTotal manual (clicked) spins in the Spin Game.
Total_FlappyTotal number of Flappy Empanada games played.
time(long) The time the query started (in miliseconds).
query_ms(int) How long the database lookup took to complete.
System Status API
To prevent our status page from going offline when our origin server does, we use a 3rd party service to monitor and report incidents and outages. We can not see or monitor any API requests made to these endpoints. Seperate privacy policies, usage limits, and terms do apply.
You may view the seperate API for our status page here.
We give NO GUARANTEE that these methods won't have breaking changes. Basically, we want you to know that we may abruptly update our APIs, change their paths, change what they return, change how much they return, or some other form of change that could result in whatever calls you make to our services to break your application. By using our API, you understand this side-effect. We will try our best to bump the v number when breaking changes are made. At the moment v1 is the latest version. Directory listing is enabled on all
/api/ subfolders, so feel free to use this in finding what you're looking for!
Since all of our APIs are cached on a CDN for 2 hours: All of our public API requests have no request limits. Should you suspect your applications traffic will exceeding normal expectations, we encourage you to implement caching techniques accordingly. Should you abuse our services, your access to our website and API will be revoked accordingly.
Questions About Our APIs?
Need help? Have a question? Join our discord and our lovely Empanada team would be more than happy to answer any of your questions.