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

# PacketFabric API

Use [/v2/auth/login](https://api.packetfabric.com) endpoint to get the token.


Use that token and "Authorize" button to authenticate your requests.


You can also use that token to authorize your `curl` request:

```
curl -X GET "https://api.packetfabric.com/v2/activity-logs" -H "accept: */*" -H "Authorization: Bearer 12a30d30-20c0-4f62-a982-eb1424631094"
```

Python code to authenticate and utilize the
[Bearer token](https://swagger.io/docs/specification/authentication/bearer-authentication/):

```
import requests
login_url = 'https://api.packetfabric.com/v2/auth/login'
login_payload = {
    'login': 'admin',
    'password': 'p4ssw0rd'
}
r = requests.post(login_url, json=login_payload)
auth_token = r.json()['token']
request_header = {
    'Authorization': f'Bearer {auth_token}'
}
contacts_url = 'https://api.packetfabric.com/v2/contacts'
r = requests.get(contacts_url, headers=request_header)
```

*For resellers only*:

To make the request on behalf of reseller's customer - add `On-Behalf: customer UUID` header to the request:

```
curl -X GET "https://api.packetfabric.com/v2/activity-logs" -H "accept: */*" -H "Authorization: Bearer 12a30d30-20c0-4f62-a982-eb1424631094" -H "On-Behalf: 11111111-2222-3333-4444-eb1424631094"
```

*For API Key Authentication*
To utilize an API Key instead of login/password, you will need to generate a key and save the token.
Using that token, as the Bearer token, you can then login.

```
api_key = <TOKEN>
request_header = {
    'Authorization': f'Bearer {api_key}'
}
contacts_url = 'https://api.packetfabric.com/v2/contacts'
r = requests.get(contacts_url, headers=request_header)
```

## For AI agents

Use [/v2/auth/login](https://api.packetfabric.com) endpoint to get the token.


Use that token and "Authorize" button to authenticate your requests.


You can also use that token to authorize your `cu...

## Scope

Provides access to PacketFabric API functionality as defined in the OpenAPI specification.

## Capabilities

- Get activity log entry
- Get activity log entries
- Add the new API key
- Get the list of user's API keys
- Deletes API key by UUID
- Login
- Login

## Use cases

### Basic PacketFabric API Integration

Integrate PacketFabric API into your application to access its core functionality.

Example prompt: Use the PacketFabric API API to access vendor services and data.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v2/activity-logs/{log_uuid} | Get activity log entry |
| GET | /v2/activity-logs | Get activity log entries |
| POST | /v2/api-keys | Add the new API key |
| GET | /v2/api-keys | Get the list of user's API keys |
| DELETE | /v2/api-keys/{uuid} | Deletes API key by UUID |
| POST | /v2/auth/login | Login |
| GET | /v2/auth/login | Login |

## Key resources

- **Main API** — Primary PacketFabric API resources and operations

## Why Jentic

- **Setup:** Wiring PacketFabric by hand means handling its bearer-token auth against api.packetfabric.com, managing token issuance through /v2/auth/login, and building your own retry and error handling. Through Jentic you install once, import the PacketFabric API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** PacketFabric puts resource ids in the URL path (for example /v2/api-keys/{uuid} and /v2/activity-logs/{log_uuid}), and you choose which operations the agent may call. Limit it to what it needs, such as reading activity logs, so destructive operations like deleting an API key are not included unless you add them.
- **Credential handling:** Your PacketFabric 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 'list PacketFabric activity logs' or 'create an API key', and Jentic returns the matching PacketFabric operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## FAQ

### What authentication does the PacketFabric API use?

The PacketFabric API uses bearer authentication.

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

The PacketFabric API has 341 endpoints available.

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

Yes. Because you run Jentic One yourself, your own rules decide which PacketFabric operations and credentials the agent can use. You can allow it to read activity logs at /v2/activity-logs and /v2/activity-logs/{log_uuid} while leaving out destructive calls such as deleting an API key at /v2/api-keys/{uuid}. Since PacketFabric puts resource ids in the URL path, you control both which endpoints run and which resources they touch.