canonical: https://jentic.com/apis/rubrikinc.github.io/rubrikinc-github

# Rubrikinc Rubrik REST API

Copyright © 2017-2021 Rubrik Inc. [Legal](#section/Legal) Introduction Welcome to the Rubrik™ REST API documentation. The Rubrik REST API provides a RESTful interface for working with Rubrik clusters and Rubrik Edge virtual appliances. The Rubrik REST API can be used to query, configure, and control nearly all of the operations of the Rubrik software. Through authenticated and encrypted interactio. The API exposes 454 endpoints secured with apiKey, basic authentication.

## For AI agents

Programmatically get the aws account id of an aws s3 archival location, disable location for archival and modification operations. Covers 454 operations with apiKey, basic authentication.

## Scope

Does not handle payments, communications, or crm - use for cloud infrastructure only.

## Capabilities

- Get the AWS account ID of an AWS S3 archival location
- Disable location for archival and modification operations
- Enable archival location for archival and modification operations
- Refresh archive information for a list of data sources
- Clear cached authorization information
- Reschedule unsuccessful backup tasks

## Use cases

### Cloud Infrastructure Operations

Use the Rubrik REST API to perform cloud infrastructure operations programmatically. The API provides 454 endpoints covering core functionality including get the aws account id of an aws s3 archival location, disable location for archival and modification operations, enable archival location for archival and modification operations.

Example prompt: Call GET /archive/aws/s3/{id}/account_id to get the aws account id of an aws s3 archival location

### Automated Endpoint reference Management

Automate endpoint reference operations by combining multiple Rubrik REST API endpoints. Agents can disable location for archival and modification operations and then enable archival location for archival and modification operations in a single workflow.

Example prompt: Call POST /archive/location/{id}/owner/disable to disable location for archival and modification operations, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Rubrik REST 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, basic tokens manually.

Example prompt: Search Jentic for 'get the aws account id of an aws s3 archival location', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /archive/aws/s3/{id}/account_id | Get the AWS account ID of an AWS S3 archival location |
| POST | /archive/location/{id}/owner/disable | Disable location for archival and modification operations |
| POST | /archive/location/{id}/owner/enable | Enable archival location for archival and modification operations |
| POST | /archive/location/{location_id}/reader/refresh/data_sources | Refresh archive information for a list of data sources |
| DELETE | /authorization/cache | Clear cached authorization information |
| POST | /backup/retry | Reschedule unsuccessful backup tasks |
| GET | /backup/retry/{id} | Get status of reschedule attempt |
| POST | /backup/verify | Trigger a job for snapshot verification |

## Key resources

- **Endpoint reference** — Operations related to Endpoint reference
- **/archive** — Archival.
- **/authorization** — Authorization.
- **/backup** — Backup.
- **/blackout_window** — Blackout windows.

## Why Jentic

- **Setup:** Wiring the Rubrik REST API by hand means supporting both its basic auth and header token schemes, resolving the relative /api/v1 base against your cluster host, and handling archival operations yourself. Through Jentic you install once, import the Rubrik REST API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Rubrik puts the archival location id in the URL path (/archive/location/{id}/...), so a rule can pin your agent to one location: it can read that location and nothing else. You choose the operations it may call, so disabling or enabling an archival location is not included unless you add it.
- **Credential handling:** Your Rubrik 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 'get an S3 archival location's account id' or 'refresh data sources for an archive', and Jentic returns the matching Rubrik operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### What authentication does the Rubrik REST API use?

The Rubrik REST API 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 get the aws account id of an aws s3 archival location with the Rubrik REST API?

Yes. Use the GET /archive/aws/s3/{id}/account_id endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Rubrik REST 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 get the aws account id of an aws s3 archival location through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get the aws account id of an aws s3 archival location'. Jentic returns the matching Rubrik REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Rubrik REST API have?

The Rubrik REST API exposes 454 endpoints covering endpoint reference, /archive, /authorization operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Rubrik operations and credentials the agent can use. Because Rubrik puts the archival location id in the URL path (/archive/location/{id}/...), a rule can pin the agent to one location so it reads that location and nothing else. You choose the operations it may call, so state-changing endpoints like POST /archive/location/{id}/owner/disable or /owner/enable are excluded unless you add them.