canonical: https://jentic.com/apis/snipe-it.readme.io/snipe-it-readme

# Snipe It Readme Snipe-IT Asset Management

Snipe-IT REST API for IT asset management including hardware, users, licenses, locations, and more. The API exposes 79 endpoints secured with bearer authentication.

## For AI agents

Programmatically create a new asset, list all assets. Covers 79 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- Create a new asset
- List all assets
- Get asset by ID
- Update an asset
- Partially update an asset
- Delete an asset
- Find asset by asset tag

## Use cases

### Maps and Geolocation Operations

Use the Snipe-IT Asset Management to perform maps geolocation operations programmatically. The API provides 79 endpoints covering core functionality including create a new asset, list all assets, get asset by id.

Example prompt: Call POST /hardware to create a new asset

### Automated Hardware Management

Automate hardware operations by combining multiple Snipe-IT Asset Management endpoints. Agents can list all assets and then get asset by id in a single workflow.

Example prompt: Call GET /hardware to list all assets, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Snipe-IT Asset Management 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 'create a new asset', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/hardware` | Create a new asset |
| GET | `/hardware` | List all assets |
| GET | `/hardware/{id}` | Get asset by ID |
| PUT | `/hardware/{id}` | Update an asset |
| PATCH | `/hardware/{id}` | Partially update an asset |
| DELETE | `/hardware/{id}` | Delete an asset |
| GET | `/hardware/bytag/{assetTag}` | Find asset by asset tag |
| GET | `/hardware/byserial/{serial}` | Find asset by serial number |

## Key resources

- **Hardware** — Asset/hardware management
- **Users** — User management
- **Licenses** — License management
- **Locations** — Location management
- **Companies** — Company management

## Why Jentic

- **Setup:** Wiring Snipe-IT Asset Management by hand means sending your bearer token on every request, filling in your own host in the `/api/v1` base, and handling paging across hardware yourself. Through Jentic you install once, import Snipe-IT Asset Management from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Snipe-IT puts the asset id in the URL path (`/hardware/{id}`), so a rule can pin your agent to hardware operations: it can read and create assets and nothing else. You choose the operations it may call, so destructive ones like deleting or overwriting an asset are not included unless you add them.
- **Credential handling:** Your Snipe-IT Asset Management 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 'create a new asset' or 'look up hardware by asset tag', and Jentic returns the matching Snipe-IT operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### What authentication does the Snipe-IT Asset Management use?

The Snipe-IT Asset Management 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 create a new asset with the Snipe-IT Asset Management?

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

### What are the rate limits for the Snipe-IT Asset Management?

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 a new asset through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new asset'. Jentic returns the matching Snipe-IT Asset Management operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Snipe-IT Asset Management have?

The Snipe-IT Asset Management exposes 79 endpoints covering hardware, users, licenses operations.

### Can I limit what my agent is allowed to do with the Snipe-IT Asset Management API?

Yes. Because you run Jentic One yourself, you decide which Snipe-IT operations the agent may call and which credentials it may use. Since Snipe-IT puts the asset id in the URL path, such as `/hardware/{id}`, you can pin the agent to reading and creating hardware assets while withholding destructive calls like deleting or overwriting an asset. Only the operations you approve are ever exposed to the agent.