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

# PocketSmith

PocketSmith provides programmatic access to developer tools functionality. The API exposes 56 endpoints secured with apiKey, oauth2 authentication.

## For AI agents

Programmatically get the authorised user, get user. Covers 56 operations with apiKey, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get the authorised user
- Update user
- Delete institution
- Create institution in user

## Use cases

### Developer Tools Operations

Use the PocketSmith to perform developer tools operations programmatically. The API provides 56 endpoints covering core functionality including get the authorised user, get user, update user.

Example prompt: Call GET /me to get the authorised user

### Automated Accounts Management

Automate accounts operations by combining multiple PocketSmith endpoints. Agents can get user and then update user in a single workflow.

Example prompt: Call GET `/users/{id}` to get user, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call PocketSmith 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, oauth2 tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/me` | Get the authorised user |
| GET | `/users/{id}` | Get user |
| PUT | `/users/{id}` | Update user |
| GET | `/institutions/{id}` | Get institution |
| PUT | `/institutions/{id}` | Update institution |
| DELETE | `/institutions/{id}` | Delete institution |
| POST | `/users/{id}/institutions` | Create institution in user |
| GET | `/users/{id}/institutions` | List institutions in user |

## Key resources

- **Accounts** — Operations for accounts
- **Attachments** — Operations for attachments
- **Categories** — Operations for categories
- **Currencies** — Operations for currencies
- **Events** — Operations for events

## Why Jentic

- **Setup:** Wiring PocketSmith by hand means choosing between an X-Developer-Key header and OAuth2, then threading user and institution ids through the api.pocketsmith.com/v2 paths yourself. Through Jentic you install once, import PocketSmith from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** PocketSmith puts the user and institution id in the URL path (`/users/{id}`, `/institutions/{id}`), so a rule can pin your agent to one user's records. You choose the operations it may call, so destructive ones like institution deletion are not included unless you add them.
- **Credential handling:** Your PocketSmith developer key or OAuth 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 the authorised user' or 'add an institution', and Jentic returns the matching PocketSmith operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the PocketSmith use?

The PocketSmith uses apiKey, oauth2 authentication. 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 the authorised user with the PocketSmith?

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

### What are the rate limits for the PocketSmith?

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 authorised user through Jentic?

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

### How many endpoints does the PocketSmith have?

The PocketSmith exposes 56 endpoints covering accounts, attachments, categories operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which PocketSmith operations and credentials the agent may use. PocketSmith puts the user and institution id in the URL path, such as `/users/{id}` and `/institutions/{id}`, so a rule can pin the agent to a single user's records. You also choose exactly which operations it may call, so destructive ones like DELETE `/institutions/{id}` stay off limits unless you explicitly add them.