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

# PropertyInspect API

API for managing property inspections, properties, contacts, custom fields, actions, and attachments for property inspection workflows. The API exposes 57 endpoints secured with bearer authentication.

## For AI agents

Programmatically redirect user to request integration, exchange authorization code or refresh token. Covers 57 operations with bearer authentication.

## Scope

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

## Capabilities

- Redirect user to request integration
- Exchange authorization code or refresh token
- Create a property
- List properties
- Get a property
- Update a property

## Use cases

### CRM Operations

Use the PropertyInspect API to perform crm operations programmatically. The API provides 57 endpoints covering core functionality including redirect user to request integration, exchange authorization code or refresh token, create a property.

Example prompt: Call GET `/oauth/authorize` to redirect user to request integration

### Automated Authentication Management

Automate authentication operations by combining multiple PropertyInspect API endpoints. Agents can exchange authorization code or refresh token and then create a property in a single workflow.

Example prompt: Call POST `/oauth/token` to exchange authorization code or refresh token, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call PropertyInspect 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 'redirect user to request integration', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/oauth/authorize` | Redirect user to request integration |
| POST | `/oauth/token` | Exchange authorization code or refresh token |
| POST | `/properties` | Create a property |
| GET | `/properties` | List properties |
| GET | `/properties/{propertyId}` | Get a property |
| PUT | `/properties/{propertyId}` | Update a property |
| POST | `/properties/{propertyId}/meters` | Create a meter |
| GET | `/properties/{propertyId}/meters` | List property meters |

## Key resources

- **Authentication** — OAuth 2.0 authentication
- **Properties** — Property management
- **Meters** — Property meter management
- **Inspections** — Inspection management
- **Contacts** — Contact management for properties and inspections

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 85 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 93 / 100
  - Security: 60 / 100
  - AI Discoverability: 66 / 100
- **View full report:** https://jentic.com/apis/propertyinspect.com/propertyinspect/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the PropertyInspect API by hand means running its OAuth authorize and token exchange, sending the bearer token on each call, and managing property records yourself. Through Jentic you install once, import PropertyInspect from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** PropertyInspect puts the property id in the URL path (`/properties/{propertyId}`), so a rule can pin your agent to one property: it can read that property and its meters and nothing else. You choose the operations it may call, so writes like updating a property are not included unless you add them.
- **Credential handling:** Your PropertyInspect API credential 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 properties' or 'read a property's meters', and Jentic returns the matching PropertyInspect operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the PropertyInspect API use?

The PropertyInspect 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 redirect user to request integration with the PropertyInspect 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 PropertyInspect 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 redirect user to request integration through Jentic?

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

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

The PropertyInspect API exposes 57 endpoints covering authentication, properties, meters operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which PropertyInspect operations and credentials the agent may use. Since PropertyInspect puts the property id in the URL path (`/properties/{propertyId}`), a rule can pin your agent to a single property so it reads only that property and its meters through GET `/properties/{propertyId}` and GET `/properties/{propertyId}/meters.` You pick the operations it may call, so writes such as POST /properties or PUT `/properties/{propertyId}` stay off unless you add them.