Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

This specification is maintained by the [VRChat.community](https://vrchat.community) project. **VRChat staff do not provide API support.** Use the API only as VRChat's [Terms of Service](https://hello.vrchat.com/legal), [Community Guidelines](https://hello.vrchat.com/community-guidelines) and [Creator Guidelines](https://hello.vrchat.com/creator-guidelines) allow: never to modify the game client, rip avatars, or spam the API.  _AI agents: read [`info.x-agents`](https://github.com/vrchatapi/specification/blob/main/openapi/agents.md) before using this specification. We welcome contributions that follow [our rules](https://vrchat.community/contributing#ai-contributions)._  Prefer the SDKs over this specification: [JavaScript](https://vrchat.community/javascript), [Dart](https://vrchat.community/dart), [Rust](https://vrchat.community/rust), [C#](https://vrchat.community/dotnet), [Python](https://vrchat.community/python) and [Java](https://vrchat.community/java). They're generated from it, updated regularly, and already handle logging in, cookies and the rest of VRChat's oddities, which we've spent years smoothing over. Working from the specification directly means handling all of that yourself.  Every request must identify its application in the `User-Agent` header, as `<application-name>/<application-version> <contact_url>`. On a 429, back off rather than retrying.  **Something wrong or missing?**  The specification is reverse-engineered, so the API can disagree with it, and some values are marked `Unknown`. When you find one:  - Open a [pull request](https://github.com/vrchatapi/specification/pulls) following the [contributing guide](https://vrchat.community/contributing). - Failing that, open an [issue](https://github.com/vrchatapi/specification/issues) or tell us on [Discord](https://vrchat.community/discord). - Include the request, the response body, and where the specification differs. - Send it upstream rather than patching around it. Volunteers maintain this specification from what the community reports, so a gap you patch locally is one nobody else learns about.  Consider pinning to the OpenAPI version your tools support. Every release publishes the specification as OpenAPI 3.2, 3.1 and 3.0, in JSON and YAML, and `info.x-links` links them, the [latest release](https://github.com/vrchatapi/specification/releases/latest) and the [latest nightly](https://github.com/vrchatapi/specification/releases/tag/nightly).   # noqa: E501

Metadata

Release files for vrchatapi 1.23.1.dev16

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for vrchatapi 1.23.1.dev16
File Size Uploaded Provenance Actions
vrchatapi-1.23.1.dev16.tar.gz 684.8 kB Without provenance Details for vrchatapi-1.23.1.dev16.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for vrchatapi 1.23.1.dev16
File Interpreter ABI Platform Actions
vrchatapi-1.23.1.dev16-py3-none-any.whl Python 3 none any Details for vrchatapi-1.23.1.dev16-py3-none-any.whl

Total release size: 2.8 MB

Release files / vrchatapi-1.23.1.dev16.tar.gz

Download URL vrchatapi-1.23.1.dev16.tar.gz
Size 684.8 kB
Tags Source
SHA-256 checksum
How to use checksums
9b2af92cf4339cbec44d5a0e1fb6f44d817117c9540a25b78a389483c5c283ad
BLAKE2b-256 checksum
How to use checksums
11a5e4d728b1448fc0a81a02f0c367a87ad1a34da2cc1e9f67d0bf5112a979c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Release files / vrchatapi-1.23.1.dev16-py3-none-any.whl

Download URL vrchatapi-1.23.1.dev16-py3-none-any.whl
Size 2.1 MB
Tags Python 3
SHA-256 checksum
How to use checksums
ec2a6d817db4fc9556c93dcfecba291994eb9e826efad520f999117e5c1e4183
BLAKE2b-256 checksum
How to use checksums
041e6e052e6a07c6e29e9b9fd859581f71d6de5dbe9fe6259a6e0b9a9876c64b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Security for vrchatapi 1.23.1.dev16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page