PacketFabric API

Name: PacketFabric API
Brand: PacketFabric API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsPackage Registrybearer341 EndpointsREST

For 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...

Use for: I need to access PacketFabric API, How do I use the packetfabric.com API?, Get data from packetfabric.com

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

Install Jentic One Beta

Connect the PacketFabric API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PacketFabric 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpacketfabric.com%2Fpacketfabric" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpacketfabric.com%2Fpacketfabric" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 PacketFabric API.

Get activity log entry

Get activity log entries

Add the new API key

Get the list of user's API keys

GET STARTED

Start building with PacketFabric API

Explore with Jentic One

View OpenAPI Document

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) ```

Key Endpoints

341 endpoints — use [/v2/auth/login](https://api.

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

GET

/v2/auth/login

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using PacketFabric API through Jentic.

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.

PacketFabric API

Connect the PacketFabric API to your agent

Capabilities

Start building with PacketFabric API

Use Cases

Key Endpoints

Why Jentic?

FAQs