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

# TitleTrackr API

API documentation for TitleTrackr's external integrations. TitleTrackr is a title abstract management platform that helps title companies manage orders, abstracts, and projects. Authentication This API uses OAuth 2.0 Authorization Code flow for authentication. After obtaining an access token, include it in requests as a Bearer token: Webhooks TitleTrackr supports real-time notifications via webhoo. The API exposes 11 endpoints secured with bearer authentication.

## For AI agents

Programmatically authorization request, token exchange. Covers 11 operations with bearer authentication.

## Scope

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

## Capabilities

- Authorization Request
- Token Exchange
- Get Current User
- Subscribe to Webhook
- Unsubscribe from Webhook
- List Webhook Subscriptions

## Use cases

### Developer Tools Operations

Use the TitleTrackr API to perform developer tools operations programmatically. The API provides 11 endpoints covering core functionality including authorization request, token exchange, get current user.

Example prompt: Call GET `/oauth/authorize` to authorization request

### Automated Authentication Management

Automate authentication operations by combining multiple TitleTrackr API endpoints. Agents can token exchange and then get current user in a single workflow.

Example prompt: Call POST `/api/oauth/token` to token exchange, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TitleTrackr 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 'authorization request', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/oauth/authorize` | Authorization Request |
| POST | `/api/oauth/token` | Token Exchange |
| GET | `/api/zapier/me` | Get Current User |
| POST | `/api/zapier/hooks/{eventType}/subscribe` | Subscribe to Webhook |
| DELETE | `/api/zapier/hooks/{eventType}/unsubscribe` | Unsubscribe from Webhook |
| GET | `/api/zapier/hooks` | List Webhook Subscriptions |
| GET | `/api/zapier/samples/orders` | Get Sample Orders |
| GET | `/api/zapier/samples/abstracts` | Get Sample Abstracts |

## Key resources

- **Authentication** — OAuth 2.0 authentication endpoints
- **User** — User and account information
- **Webhooks** — Webhook subscription management
- **Orders** — Order management
- **Samples** — Sample data for trigger testing

## Why Jentic

- **Setup:** Wiring the TitleTrackr API by hand means running its OAuth token exchange, handling the resulting bearer token, and managing retries against its Zapier-style hook endpoints yourself. Through Jentic you install once, import TitleTrackr from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** TitleTrackr routes its subscribe and unsubscribe calls by an event type in the URL path rather than a scoped account resource, so scope the agent by the operations it needs, such as listing hooks or reading order samples. You choose that set, so an unsubscribe operation is only available if you include it.
- **Credential handling:** Your TitleTrackr 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 'subscribe to order events' or 'read abstract samples', and Jentic returns the matching TitleTrackr 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 TitleTrackr API use?

The TitleTrackr 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 authorization request with the TitleTrackr API?

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

### What are the rate limits for the TitleTrackr 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 authorization request through Jentic?

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

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

The TitleTrackr API exposes 11 endpoints covering authentication, user, webhooks operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which TitleTrackr operations and credentials the agent can use. Because TitleTrackr routes its subscribe and unsubscribe calls by an event type in the URL path rather than a scoped account resource, you scope the agent by the operations it needs, such as listing webhook subscriptions or reading order and abstract samples. You choose that set, so an unsubscribe operation is available only if you include it.