VRChat User-Agent compliance? #1130

Closed
opened 2026-04-05 16:53:03 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @cyberkitsune on 2/19/2023

Forgive me if this is the wrong place or if this is already done.

It appears that VRChat now prefers that any application that interfaces with their API identify themselves in a somewhat standardized way using the User-Agent header:

applicationName/Version contactInfo

(VRChat API Community)
Post from Foorack

(VRChat FAQ)
Post from VRChat FAQ

Does VRCX already follow this format? If not I assume this is in the pipeline? :)

*Originally created by @cyberkitsune on 2/19/2023* Forgive me if this is the wrong place or if this is already done. It appears that VRChat now prefers that any application that interfaces with their API identify themselves in a somewhat standardized way using the `User-Agent` header: ``` applicationName/Version contactInfo ``` (VRChat API Community) ![Post from Foorack](https://cyberk.it/YhYDwBvE) (VRChat FAQ) ![Post from VRChat FAQ](https://cyberk.it/IeqzdjvB) Does VRCX already follow this format? If not I assume this is in the pipeline? :)
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/VRCX#1130