canonical: https://jentic.com/apis/vrchat.com/vrchat

# VRChat API Documentation

![VRChat API Banner](https://vrchatapi.github.io/assets/img/api_banner_1500x400.png) Welcome to the VRChat API Before we begin, we would like to state this is a **COMMUNITY DRIVEN PROJECT**. This means that everything you read on here was written by the community itself and is **not** officially supported by VRChat. The documentation is provided "AS IS", and any action you take towards VRChat is c. The API exposes 271 endpoints secured with apiKey, basic authentication.

## For AI agents

Programmatically list steam transactions, get steam transaction. Covers 271 operations with apiKey, basic authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- List Steam Transactions
- Get Steam Transaction
- Submit Content Agreement
- Query and filter VRChat API Documentation records by parameters
- Monitor VRChat API Documentation operational status and events

## Use cases

### CRM Operations

Use the VRChat API Documentation to perform crm operations programmatically. The API provides 271 endpoints covering core functionality including list steam transactions, get steam transaction, get adminassetbundle.

Example prompt: Call GET `/Steam/transactions` to list steam transactions

### Automated authentication Management

Automate authentication operations by combining multiple VRChat API Documentation endpoints. Agents can get steam transaction and then get adminassetbundle in a single workflow.

Example prompt: Call GET `/Steam/transactions/{transactionId}` to get steam transaction, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call VRChat API Documentation endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, basic tokens manually.

Example prompt: Search Jentic for 'list steam transactions', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/Steam/transactions` | List Steam Transactions |
| GET | `/Steam/transactions/{transactionId}` | Get Steam Transaction |
| GET | `/adminassetbundles/{adminAssetBundleId}` | Get AdminAssetBundle |
| POST | `/agreement` | Submit Content Agreement |
| GET | `/agreement` | Get Content Agreement Status |
| GET | `/analysis/{fileId}/{versionId}` | Get File Version Analysis |
| GET | `/analysis/{fileId}/{versionId}/security` | Get File Version Analysis Security |
| GET | `/analysis/{fileId}/{versionId}/standard` | Get File Version Analysis Standard |

## Key resources

- **authentication** — Authentication Docs Here
- **avatars** — Avatars Docs Here
- **calendar** — Calendar docs here
- **economy** — Economy Docs Here
- **favorites** — Favorites Docs Here

## Why Jentic

- **Setup:** Wiring VRChat by hand means running its basic-auth login, carrying the auth cookie and any two-factor cookie against api.vrchat.cloud, and managing the calls yourself. Through Jentic you install once, import VRChat from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** VRChat puts the file and version ids in the URL path (`/analysis/{fileId}/{versionId}`), so a rule can pin your agent to reading analysis for one file version. You choose the operations it may call, so others such as posting an agreement are not included unless you add them.
- **Credential handling:** Your VRChat credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list Steam transactions' or 'read file analysis', and Jentic returns the matching VRChat operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the VRChat API Documentation use?

The VRChat API Documentation uses apiKey, basic authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list steam transactions with the VRChat API Documentation?

Yes. Use the GET `/Steam/transactions` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the VRChat API Documentation?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list steam transactions through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list steam transactions'. Jentic returns the matching VRChat API Documentation operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the VRChat API Documentation have?

The VRChat API Documentation exposes 271 endpoints covering authentication, avatars, calendar operations.

### Can I limit what my agent is allowed to do with the VRChat API?

Yes. Jentic One is self-hosted, so you set the rules that decide which VRChat operations and credentials your agent may use. You pick the exact operations it can call, so a read-only agent can hit GET `/analysis/{fileId}/{versionId}` while write actions such as POST /agreement stay off the list until you add them. Because VRChat carries the file and version ids in the URL path, you can pin a rule to reading analysis for one specific file version.