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 Rental API is one of 46 APIs that Rentberry publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 12 operations across 10 paths, and defines 43 schemas. It is described by OpenAPI 3.2.0, at version 4.

Requests are made against the base URL https://api.rentberry.com/.

12 operations 10 paths 43 schemas 6 GET6 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 12

Across 10 paths, the API surfaces 12 operations — 6 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Rental 12

Rental

GET
/v{version}/rental
Get list of user rentals
get_api_v1_application_rentals_list 2 params → 200401
POST
/v{version}/rental
Create a new rental
post_api_v1_rental_create 1 param body → 200400401
GET
/v{version}/rental/chargeable/{userType}
Get list of chargeable rentals
get_api_v1_chargeable_rentals_list 3 params → 200401
GET
/v{version}/rental/{id}
Get rental details
get_api_v1_rental_get 2 params → 200401403
POST
/v{version}/rental/{id}
Update an existing rental
post_api_v1_rental_update 2 params body → 200400401403
GET
/v{version}/rental/activate/{reference}
Activate rental by tenant
get_api_v1_rental_activate 2 params → 200401404409
POST
/v{version}/rental/archive/{rental}
Archive a rental
post_api_v1_rental_archive 2 params → 200401403
POST
/v{version}/rental/invite-homeowner
Send invitation to homeowner
post_api_v1_rental_invite_homeowner 1 param body → 204400401
POST
/v{version}/rental/invite-tenant/{rental}
Resend invitation to tenant
post_api_v1_rental_invite_tenant 2 params → 204401403
GET
/v{version}/rental/list
Get short list of user rentals
get_api_v1_rental_list_short 1 param → 200401
POST
/v{version}/rental/{id}/document
Upload document to rental
post_api_v1_rental_add_document 2 params body → 200401403
GET
/v{version}/rental/{id}/document/download/{document}
Download rental document
get_api_v1_rental_download_document 3 params → 200401403404

Schemas 43

The contract defines 43 schemas that model the data the API accepts and returns. The most detailed are Listing (71 properties), Listing7 (67 properties), User (39 properties), Rental (23 properties). Each schema is shown below with its type and property counts.

ApplicantReference
object
6 properties 3 required
ApplicantReference2
object
6 properties 3 required
Company
object
12 properties
UserStripeCustomer
object
4 properties
ListingApplication4
object
18 properties
UserStripeCustomer6
object
4 properties
ListingApplication
object
19 properties
Bounds
object
2 properties
Country
object
4 properties
OpenHouseApplication
object
11 properties
Applicant4
object
14 properties 1 required
AdminLevelCollection
object
Maintenance
object
5 properties 1 required
UserCriminalReport
object
4 properties
RentalSubscription
object
10 properties
Listing7
object
67 properties 4 required
User6
object
20 properties 4 required
Rental
object
23 properties
VirtualTour
object
6 properties 1 required
UserOauthProvider
object
8 properties
User
object
39 properties 5 required
StripePayment
object
10 properties
Rental4
object
22 properties
UserCreditScore
object
5 properties
Listing
object
71 properties 4 required
RentalPayment
object
17 properties
UserRentalHistory
object
8 properties 3 required
ListingPicture
object
4 properties 1 required
UserDocument
object
6 properties 1 required
ListingAddress2
object
18 properties
ApplicantAttachment
object
6 properties
Applicant
object
15 properties 1 required
RentalType
object
10 properties 10 required
ListingAddress
object
18 properties
UserAddress
object
6 properties 4 required
UserRentalHistory2
object
8 properties 3 required
State2
object
3 properties
RentalPaymentUnit
object
4 properties
InviteHomeownerType
object
1 property 1 required
RentalPaymentAccount
object
4 properties
State
object
4 properties
Price
object
Coordinates
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rentberry-rental-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 Rental 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.