Encircleapp Encircle Public API
Agent-ready OpenAPI document · curated by JenticProductivityTask Managementbearer17 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage property claims, claim assignments, equipment records, and organizations on the Encircle restoration platform.
Use for: I need to create a new property claim record, List all property claims open for a contractor, Update the status of a property claim assignment, Find all equipment deployed on a specific claim
Not supported: Does not handle on-site photo upload, accounting, or carrier billing - use for property claim, assignment, and equipment record management only.
Jentic publishes the only available OpenAPI specification for Encircle Public API, keeping it validated and agent-ready. Encircle is a property restoration and insurance claims platform used by contractors and adjusters to manage on-site documentation, equipment, and claim assignments. The API exposes property claims, claim assignments, equipment records and specifications, organization data, and user lookups. Use it to integrate Encircle data into estimating tools, accounting systems, or claim management workflows that span vendors.
Install Jentic One Beta
Connect the Encircle Public API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Encircle Public 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.
1
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%2Fencircleapp.com%2Fencircle" | sh2
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%2Fencircleapp.com%2Fencircle" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Encircle Public API.
Create, list, retrieve, and update property claim records for restoration jobs
Manage claim assignments to track which crews and adjusters are working a claim
List, create, retrieve, and update equipment records used on a job
Look up equipment specifications to populate estimating templates
Find organizations and read their associated brands for partner-based workflows
Look up users by email address for assignment and audit logic
Use Cases
Patterns agents use Encircle Public API for, with concrete tasks.
★ Claim Workflow Integration
Pull property claims and assignments out of Encircle and into an estimating, scheduling, or accounting system so contractors run their business from one place. The API exposes list, retrieve, create, and update operations on property claims and their assignments. Restoration operations teams use this to keep field documentation in Encircle while back-office systems stay current automatically.
Iterate GET /v1/property_claims, then GET /v1/property_claims/{property_claim_id}/assignments per claim and write the merged record into the estimating system.
Equipment Tracking and Estimating
Track which equipment is deployed on which job and resolve specifications into estimating templates. The API exposes /v2/equipment for the deployed equipment list and /v2/equipment_specs for the specification catalogue. Estimating teams use this to keep dehumidifier, air mover, and similar equipment costs accurate per claim.
Call GET /v2/equipment to list deployed units and resolve each spec via GET /v2/equipment_specs/{equipment_spec_id} for the estimating roll-up.
Organization and User Resolution
Resolve partner organizations and individual users so a workflow can assign claims to the right crew or external partner. The API exposes GET /v1/organizations and GET /v1/users/{email_address} for these lookups, plus an organization brands endpoint for branded portals. Operations teams use this to drive accurate routing across multi-vendor claim networks.
Call GET /v1/users/{email_address} to resolve the user, then GET /v1/organizations to confirm the partner organization before posting a claim assignment.
Agent-Driven Claim Handoff
An agent watches new claims appear in Encircle, creates a matching record in the contractor's PSA or accounting system, assigns the right crew, and writes the assignment back. Through Jentic the agent searches by intent, loads the schemas, and chains calls without bespoke client code. The handoff that previously took manual data entry runs as a single agent task.
Search Jentic for 'create a property claim assignment', execute GET /v1/property_claims for new entries, then POST /v1/property_claims/{property_claim_id}/assignments to assign the chosen crew.
Key Endpoints
17 endpoints — jentic publishes the only available openapi specification for encircle public api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/v1/property_claims
List property claims
POST
/v1/property_claims
Create a property claim
PATCH
/v1/property_claims/{property_claim_id}
Update a property claim
POST
/v1/property_claims/{property_claim_id}/assignments
Assign a crew to a claim
GET
/v2/equipment
Find equipment records
GET
/v2/equipment_specs/{equipment_spec_id}
Get equipment specification
GET
/v1/organizations
Find organizations
GET
/v1/users/{email_address}
Get user by email
GET
/v1/property_claims
List property claims
POST
/v1/property_claims
Create a property claim
PATCH
/v1/property_claims/{property_claim_id}
Update a property claim
POST
/v1/property_claims/{property_claim_id}/assignments
Assign a crew to a claim
GET
/v2/equipment
Find equipment records
GET
/v2/equipment_specs/{equipment_spec_id}
Get equipment specification
GET
/v1/organizations
Find organizations
GET
/v1/users/{email_address}
Get user by email
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Encircle Public API by hand means handling its bearer auth, tracking its v1 and v2 route prefixes for claims and equipment, and building your own error handling against https://api.encircleapp.com. Through Jentic you install once, import the Encircle Public API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The Encircle Public API puts the property claim id in the URL path (/v1/property_claims/{property_claim_id}/...), so a rule can pin your agent to one claim: it can update that claim and add assignments to it and nothing else. You choose the operations it may call, so creating new claims is not included unless you add it.
Credential isolation
Your Encircle 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 'update a property claim' or 'look up an equipment spec', and Jentic returns the matching Encircle operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Bill the contractor or insurer once a claim closes
Pair with Stripe for collection on closed claims; not a substitute for claim management itself.
FAQs
Specific to using Encircle Public API through Jentic.
Why is there no official OpenAPI spec for Encircle Public API?
Encircle does not publish a stable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Encircle Public API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Encircle Public API use?
The API uses HTTP Bearer authentication. Send the access token in the Authorization header on every request. The JSON Web Key Set is exposed at GET /v1/json_web_key_set/{key_set} for token verification. Through Jentic the token is held encrypted in the vault and injected at execution time.
Can I create a property claim with the Encircle Public API?
Yes. POST /v1/property_claims accepts the claim payload. Use PATCH /v1/property_claims/{property_claim_id} to update it as the job progresses.
How do I assign a crew to a claim through Jentic?
Search Jentic for 'create a property claim assignment', load the schema for POST /v1/property_claims/{property_claim_id}/assignments, and execute it with the resolved user identifier.
What are the rate limits for the Encircle Public API?
The OpenAPI spec does not declare quantitative rate limits; Encircle enforces limits at the account level. Treat HTTP 429 responses as authoritative and back off using the Retry-After header where present.
Can I look up a user by email address?
Yes. GET /v1/users/{email_address} returns the user record, which is the recommended path before assigning that user to a claim or organization.
Can I limit what my agent is allowed to do with the Encircle Public API?
Yes. Because you run Jentic One yourself, your own rules decide which Encircle operations and credentials the agent may use. Since the property claim id sits in the URL path, such as /v1/property_claims/{property_claim_id}/assignments, you can pin the agent to a single claim so it can update that claim and add assignments to it and nothing else. You also choose the specific operations it may call, so creating new claims with POST /v1/property_claims stays off limits unless you explicitly allow it.
GET STARTED