Rubrikinc Rubrik REST API
★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeapiKey, basic454 EndpointsREST
For 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.
Use for: I need to the aws account id of an aws s3 archival location, I want to disable location for archival and modification operations, Search for enable archival location for archival and modification operations, Find all refresh archive information for a list of data sources
Not supported: Does not handle payments, communications, or crm — use for cloud infrastructure only.
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.
Install Jentic One Beta
Connect the Rubrik REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rubrik REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Rubrik REST API.
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
Patterns agents use Rubrik REST API for, with concrete tasks.
★ 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.
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.
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.
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
454 endpoints — copyright © 2017-2021 rubrik inc.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Rubrik REST API apiKey, basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'get the aws account id of an aws s3 archival location') and Jentic returns the matching Rubrik REST API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Rubrik REST API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Rubrik REST API through Jentic.
What authentication does the Rubrik REST API use?
The Rubrik REST API uses apiKey, basic authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED