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

# SnapShooter API

SnapShooter provides a REST API for managing cloud backups, including SSH keys, servers, storage, backup jobs, schedules, and restore operations. The API is currently in Alpha status. The API exposes 13 endpoints secured with bearer authentication.

## For AI agents

Programmatically get team information, create ssh key. Covers 13 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for storage and databases only.

## Capabilities

- Get team information
- Create SSH key
- List SSH keys
- Add a server
- Monitor SnapShooter API operational status and events

## Use cases

### Storage and Databases Operations

Use the SnapShooter API to perform storage operations programmatically. The API provides 13 endpoints covering core functionality including get team information, create ssh key, list ssh keys.

Example prompt: Call GET /team to get team information

### Automated Backup Solutions Management

Automate backup solutions operations by combining multiple SnapShooter API endpoints. Agents can create ssh key and then list ssh keys in a single workflow.

Example prompt: Call POST /ssh-keys to create ssh key, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SnapShooter 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 bearer tokens manually.

Example prompt: Search Jentic for 'get team information', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/team` | Get team information |
| POST | `/ssh-keys` | Create SSH key |
| GET | `/ssh-keys` | List SSH keys |
| POST | `/servers` | Add a server |
| GET | `/servers` | List servers |
| POST | `/storage` | Add storage destination |
| GET | `/storage` | List storage destinations |
| POST | `/jobs` | Create backup job |

## Key resources

- **Backup Solutions** — Operations for backup solutions
- **Jobs** — Operations for jobs
- **Servers** — Operations for servers
- **Ssh Keys** — Operations for ssh keys
- **Storage** — Operations for storage

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 81 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 58 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 67 / 100
- **View full report:** https://jentic.com/apis/snapshooter.com/snapshooter/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the SnapShooter API by hand means sending your bearer token on every request, pointing at the api.snapshooter.com/v1 host, and orchestrating server, storage, and job calls yourself. Through Jentic you install once, import the SnapShooter API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The SnapShooter API identifies work by operation rather than a resource id in the URL path, so limit the agent to the operations it needs, such as listing servers or reading team information. You choose that set, so creating servers, storage, or backup jobs is only included if you add it.
- **Credential handling:** Your SnapShooter API token 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 team information' or 'list backup servers', and Jentic returns the matching SnapShooter API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Dropbox** — Alternative storage API
- **Box** — Alternative storage API
- **Amazonaws** — Complementary storage API

## FAQ

### What authentication does the SnapShooter API use?

The SnapShooter API uses a Bearer token in the Authorization header. 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 team information with the SnapShooter API?

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

### What are the rate limits for the SnapShooter 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 team information through Jentic?

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

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

The SnapShooter API exposes 13 endpoints covering backup solutions, jobs, servers operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SnapShooter API operations and credentials the agent can use. Since the API identifies work by operation rather than a resource id in the URL, you can allow read-only calls such as listing servers or reading team information while excluding write operations. Creating servers, adding storage destinations, or starting backup jobs are only available to the agent if you choose to include them.