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

Rentberry Screening API

Screening

Rentberry Screening API is one of 46 APIs that Rentberry publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Screening. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and authentication docs.

This API exposes 8 operations across 7 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 4.

Requests are made against a single base URL, https://api.rentberry.com/.

8 operations 7 paths 21 schemas 1 DELETE2 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4
Base URL
https://api.rentberry.com/
Resource Areas
1

Paths & Operations 8

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

Screening 8

Screening

GET
/v{version}/screening
Get homeowner screening requests
get_api_v1_screening_request_list 4 params → 200401
POST
/v{version}/screening
Create screening requests
post_api_v1_screening_request_create 1 param body → 200400401
GET
/v{version}/screening/{reference}
Get screening request by reference
get_api_v1_screening_request_get 2 params → 200404
POST
/v{version}/screening/resend/{id}
Resend screening request email
post_api_v1_screening_request_resend 2 params → 200401403404405406
DELETE
/v{version}/screening/{id}
Cancel screening request
delete_api_v1_screening_request_cancel 2 params → 200401403404405406407
POST
/v{version}/screening/screen/{reference}/paydeprecated
Pay for screening (deprecated)
post_api_v1_screening_screen_pay 2 params body → 200402
POST
/v{version}/screening/validate/{reference}
Validate tenant data for screening
post_api_v1_screening_validate_screening_data 2 params body → 200400402404405
POST
/v{version}/screening/screen/{reference}
Perform tenant screening
post_api_v1_screening_screen_user 2 params body → 200400402404405406

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are User (39 properties), User7 (19 properties), ScreeningRequest2 (15 properties), ScreeningRequest (15 properties). Each schema is shown below with its type and property counts.

AccountCreditScoreType
object
1 property 1 required
User
object
39 properties 5 required
Company
object
12 properties
AccountAddressType
object
6 properties 5 required
State
object
4 properties
UserStripeCustomer7
object
4 properties
AccountCreditScoreCheckType
object
8 properties 8 required
ScreeningRequest2
object
15 properties
UserOauthProvider
object
8 properties
UserAddress
object
6 properties 4 required
ScreeningRequestCreateType
object
3 properties 3 required
UserStripeCustomer
object
4 properties
UserRentalHistory
object
8 properties 3 required
UserCriminalReport
object
4 properties
ScreeningResponse
object
FeatureTicket
object
7 properties
ScreeningRequest
object
15 properties
UserCreditScore
object
5 properties
ScreeningRequestsType
object
1 property 1 required
RentalPaymentAccount
object
4 properties
User7
object
19 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rentberry-screening-api-openapi.yml Raw ↑

Other APIs Rentberry publishes across the network.

Rentberry Geocoder (gRPC)
Rentberry Applications API
Rentberry Auth API
Rentberry Breadcrumbs API
Rentberry Complaints API
Rentberry Contract Templates API
Rentberry Contracts API
Rentberry Devices API
Rentberry Events API
Rentberry Features API
Rentberry Integration Requests API
Rentberry Landing Pages API
Where this information came from

This is an independent, third-party profile of Rentberry Screening 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.