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

# Roblox API

The Roblox API. See https://create.roblox.com/docs/cloud/open-cloud for more details. The API exposes 855 endpoints secured with apiKey, oauth2 authentication.

## For AI agents

Programmatically create creator store product, get creator store product. Covers 855 operations with apiKey, oauth2 authentication.

## Scope

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

## Capabilities

- Create Creator Store Product
- Get Creator Store Product
- Update Creator Store Product
- List Group Forum Categories
- Monitor Roblox API operational status and events

## Use cases

### Developer Tools Operations

Use the Roblox API to perform developer tools operations programmatically. The API provides 855 endpoints covering core functionality including create creator store product, get creator store product, update creator store product.

Example prompt: Call POST `/cloud/v2/creator-store-products` to create creator store product

### Automated Accounts Management

Automate accounts operations by combining multiple Roblox API endpoints. Agents can get creator store product and then update creator store product in a single workflow.

Example prompt: Call GET `/cloud/v2/creator-store-products/{creator_store_product_id}` to get creator store product, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Roblox API 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, oauth2 tokens manually.

Example prompt: Search Jentic for 'create creator store product', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/cloud/v2/creator-store-products` | Create Creator Store Product |
| GET | `/cloud/v2/creator-store-products/{creator_store_product_id}` | Get Creator Store Product |
| PATCH | `/cloud/v2/creator-store-products/{creator_store_product_id}` | Update Creator Store Product |
| GET | `/cloud/v2/groups/{group_id}` | Get Group |
| GET | `/cloud/v2/groups/{group_id}/forum-categories` | List Group Forum Categories |
| GET | `/cloud/v2/groups/{group_id}/forum-categories/{forum_category_id}/posts` | List Group Forum Posts |
| GET | `/cloud/v2/groups/{group_id}/forum-categories/{forum_category_id}/posts/{post_id}/comments` | List Group Forum Comments |
| GET | `/cloud/v2/groups/{group_id}/join-requests` | List Group Join Requests |

## Key resources

- **Accounts** — Access and manage Roblox account information.
- **Assets** — Upload, update, and manage assets programmatically. Supported asset types include Audio, Decals, Ima
- **Avatars** — Customize user avatars and manage outfits programmatically, including body colors, scales, and [thum
- **Badges** — Create and manage experience badges to recognize player achievements. [Create](#post_legacy_badges_v
- **Bans and blocks** — Manage user restrictions using the Ban API, which includes real-time alt account detection. [Univers

## Why Jentic

- **Setup:** Wiring the Roblox API by hand means managing an x-api-key or OAuth 2.0 credential, sending it on every call to the apis.roblox.com host, and threading group and product ids through the cloud v2 paths yourself. Through Jentic you install once, import the Roblox API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Roblox puts the resource id in the URL path (`/cloud/v2/groups/{group_id}`, `/cloud/v2/creator-store-products/{creator_store_product_id}`), so a rule can pin your agent to one group or store product. You choose the operations it may call, so writes like creating or patching a store product are not included unless you add them.
- **Credential handling:** Your Roblox API key and OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a creator store product' or 'read group forum posts', and Jentic returns the matching Roblox API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Roblox API use?

The Roblox API uses apiKey, oauth2 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 create creator store product with the Roblox API?

Yes. Use the POST `/cloud/v2/creator-store-products` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Roblox API?

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 create creator store product through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create creator store product'. Jentic returns the matching Roblox API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Roblox API have?

The Roblox API exposes 855 endpoints covering accounts, assets, avatars operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Roblox API operations and credentials the agent may use. Because Roblox puts the resource id in the URL path, such as `/cloud/v2/groups/{group_id}` and `/cloud/v2/creator-store-products/{creator_store_product_id}`, you can pin the agent to a single group or store product. You also choose the operations it may call, so writes like creating or patching a store product stay out of reach unless you add them.