How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Goodlord Insurance Claim API

Resource 'InsuranceClaim' operations.

Goodlord Insurance Claim API is one of 15 APIs that Goodlord publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include InsuranceClaim. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 5 operations across 3 paths, and defines 34 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 4 base URLs: https://insurance-app.goodlord.co/, https://insurance-app.staging.goodoverlord.com/, https://insurance-app.qa1.goodoverlord.com/, https://insurance-app.demo.goodlord.co/.

5 operations 3 paths 34 schemas 2 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.goodoverlord.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Goodlord Insurance Claim API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (JWT). By default, every request must be authenticated.

  • JWT — Value for the Authorization header parameter.

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 2 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

InsuranceClaim 5

Resource 'InsuranceClaim' operations.

GET
/api/v1/insurance_claims
Retrieves the collection of InsuranceClaim resources.
api_insurance_claims_get_collection 13 params → 200403
POST
/api/v1/insurance_claims
Creates a InsuranceClaimCreate resource.
api_insurance_claims_post body → 201400422
GET
/api/v1/insurance_claims/{id}
Retrieves a InsuranceClaim resource.
api_insurance_claims_id_get 2 params → 200403404
PATCH
/api/v1/insurance_claims/{id}
Update insurance claim details
api_insurance_claims_id_patch 1 param body → 200400422404
POST
/api/v1/insurance_claims/{id}/submit
Submit an insurance claim
api_insurance_claims_idsubmit_post 1 param body → 201400422403

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are InsuranceClaim (119 properties), InsuranceClaimCreate.InsuranceClaimGetDto-insurance_claim.read (119 properties), InsuranceClaimUpdate.InsuranceClaimGetDto-insurance_claim.read (119 properties), InsuranceClaim-insurance_claim.read (119 properties). Each schema is shown below with its type and property counts.

JsonApiCollectionBaseSchema
JsonApiCollectionBaseSchemaNoPagination
object
3 properties 1 required
InsuranceClaim.csv
object
119 properties
Payment
object
14 properties
RentSchedule
object
8 properties
Company-insurance_claim.read
object
3 properties
Company
object
3 properties
RentScheduleRowAuditGetDto
object
5 properties
Payment.csv-insurance_claim.read
object
13 properties
ConstraintViolation
object
Unprocessable entity
5 properties
RentSchedule.jsonapi
object
2 properties
Payment.jsonapi
object
2 properties
InsuranceClaim-insurance_claim.read
object
119 properties
InsuranceClaimUpdate.InsuranceClaimGetDto-insurance_claim.read
object
119 properties
Company.csv-insurance_claim.read
object
3 properties
File.csv-insurance_claim.read
object
7 properties
InsuranceClaim
object
119 properties
InsuranceClaimCreate.InsuranceClaimGetDto.csv-insurance_claim.read
object
119 properties
Payment-insurance_claim.read
object
13 properties
RentScheduleRow
object
15 properties
File.jsonapi
object
2 properties
ConstraintViolation.jsonapi
object
1 property
InsuranceClaim.csv-insurance_claim.read
object
119 properties
InsuranceClaim.jsonapi
object
2 properties
InsuranceClaimCreate.InsuranceClaimGetDto-insurance_claim.read
object
119 properties
Error.jsonapi
object
1 property
InsuranceClaimCreate.InsuranceClaimPostDto.jsonapi-insurance_claim.read
object
1 property
RentScheduleRow.jsonapi
object
2 properties
InsuranceClaimUpdate.InsuranceClaimGetDto.csv-insurance_claim.read
object
119 properties
Error
object
A representation of common errors.
8 properties
File
object
9 properties
File-insurance_claim.read
object
7 properties
Company.jsonapi
object
1 property
InsuranceClaimUpdate.InsuranceClaimPatchDto.jsonapi-insurance_claim.read
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

goodlord-insuranceclaim-api-openapi.yml Raw ↑

Other APIs Goodlord publishes across the network.

Goodlord Agent API
Goodlord Application API
Goodlord Authentication API
Goodlord Company API
Goodlord File API
Goodlord Media API
Goodlord Payment API
Goodlord Rent Schedule API
Goodlord Rent Schedule Row API
Goodlord Rent Schedule Row Post Dto API
Goodlord Rent Schedule Row Update API
Goodlord Role API
Where this information came from

This is an independent, third-party profile of Goodlord Insurance Claim API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.