Undocumented endpoint (/pigAscii)

[Usman Shafiq]

I have no clue what the use is, but https://vrchat.com/api/1/pigAscii exists.

Response at time of writing:

{"pig":"\n             __,---.__\n        __,-'         `-.\n       /_ /_,'           \\&\n       _,''               \\\n      (\")            .    |\n pig   ``--|__|--..-'`.__|\n"}

formatted 'pig' object:

             __,---.__
        __,-'         `-.
       /_ /_,'           \\&
       _,''               \\
      (\")            .    |
 pig   ``--|__|--..-'`.__|

[Bluscream]

how do people find these

[waterflame]

The page can also be reached from https://api.vrchat.cloud/api/1/pigAscii

[Myrkur]

amazing contribution.

[Eirik Bøe]

absolute madlad 👀

[Aries]

Can you confirm where this endpoint was found from?

[Usman Shafiq]

Can you confirm where this endpoint was found from?

no

[nyan]

HOW

[Foorack / Max Faxälv]

@DubyaDude Thank you very much for this report. While this specific endpoint is a meme, we rely majorly on community contributions, so still very appreciated. Also for the laugh 😊

@wfscans api.vrchat.cloud and vrchat.com are mostly interchangeable, except for some minor Cloudflare bot detection differences. But they will always respond with the same result on both domains.

---

And to everyone else, YES, we are all surely very curious of the origins of this endpoint, but they have reported something which we have already been able to independently verify.

Asking them to reveal their source on how they got hold of this information should not be necessary. In fact, it might even discourage them from reporting further findings in the future. Thanks for the understanding! 💜

---

Now... Wth to do with this one.....

1. As an undocumented endpoint, this Issue should be moved to the Specification project.

2. Do... we want this in the SDK?.. We could make it website-only, or maybe a Markdown page rather than as part of the spec?
   Alternatively, do we not include it at all, and instead keep it to here and on the Discords only? But what if more endpoints like this appear in the future, etc?

[Myrkur]

put it in the sdk its existence is more then enough to warrant it be added 👍

[Usman Shafiq]

1. I'll go ahead and move it to the Specification project.
2. Since there's no real dependency of any user functionality on the endpoint (that I'm aware of), it could disappear at any moment now that this issue shed light on it. Would be a fun easter egg in the SDK though.