Electronic Tenant Solutions (tenanthandbooks.com) is a commercial real estate tenant handbook and building operations platform. Its API exposes buildings, contacts, certificates of insurance, preventative maintenance, amenity reservations, and service requests, letting you ingest property operations data into Nexla for analysis and reporting.
Power end-to-end data operations for your Electronic Tenant Solutions API with Nexla. Our bi-directional Electronic Tenant Solutions connector is purpose-built for Electronic Tenant Solutions, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Electronic Tenant Solutions or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Electronic Tenant Solutions workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating an Electronic Tenant Solutions credential, you need an API key for your Electronic Tenant Solutions account. The API authenticates every request using an API key sent in the x-api-key request header.
Sign in to your Electronic Tenant Solutions account, or contact your Electronic Tenant Solutions account administrator or support representative to request API access.
Obtain the API key issued for your account. The key scopes access to the buildings and property operations data your account is permitted to view.
Store the API key securely, as you will need it to configure your Nexla credential. Treat the key as sensitive information and rotate it if it is ever exposed.
The API key is sent in the x-api-key header on every request to the Electronic Tenant Solutions API (base URL https://api.tenanthandbooks.com/v1). For details on available endpoints and account setup, refer to the Electronic Tenant Solutions website.
After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Electronic Tenant Solutions API key in the API Key field. This key is sent in the x-api-key header for all API requests and must be kept confidential.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Electronic Tenant Solutions connector tile, then select the credential that will be used to connect to Electronic Tenant Solutions, and click Next; or, create a new Electronic Tenant Solutions credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Electronic Tenant Solutions endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
[Rest API] List Buildings
Returns a list of buildings your API Key has access to.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] Building Details
Returns details for a single building.
This endpoint returns a single record for the requested resource.
Requires a Building ID value (Building ID (from GET /v1/buildings)) to identify the record to fetch.
[Rest API] List CM Companies
List Contact Management companies.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] CM Company Details
Contact Management company details.
This endpoint returns a single record for the requested resource.
Requires a Company ID value (Company ID within Contact Management / COI) to identify the record to fetch.
[Rest API] List CM Groups
List Contact Management groups.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] CM Group Details
Contact Management group details.
This endpoint returns a single record for the requested resource.
Requires a Group ID value (Contact Management group ID) to identify the record to fetch.
[Rest API] List CM History
List Contact Management history notes.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] CM History Details
Contact Management history note details.
This endpoint returns a single record for the requested resource.
Requires a History Note ID value (Contact Management history note ID) to identify the record to fetch.
[Rest API] List Unread Text Messages
List unread Contact Management text messages.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] List CM Users
List Contact Management users.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] CM User Details
Contact Management user details.
This endpoint returns a single record for the requested resource.
Requires a User ID value (Contact Management user ID) to identify the record to fetch.
[Rest API] List Certificates
List Certificate of Insurance records.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] Certificate Details
Certificate of Insurance details.
This endpoint returns a single record for the requested resource.
Requires a Certificate ID value (Certificate of Insurance ID) to identify the record to fetch.
[Rest API] List COI Companies
List Certificate of Insurance companies.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] COI Company Details
Certificate of Insurance company details.
This endpoint returns a single record for the requested resource.
Requires a Company ID value (Company ID within Contact Management / COI) to identify the record to fetch.
[Rest API] Application Preferences
Preventative Maintenance application preferences for a building.
This endpoint returns a single record for the requested resource.
Requires a Building ID value (Building ID (from GET /v1/buildings)) to identify the record to fetch.
[Rest API] Display Preferences
Preventative Maintenance display preferences for a user.
This endpoint returns a single record for the requested resource.
Requires a User ID value (Contact Management user ID) to identify the record to fetch.
[Rest API] List Equipment
List Preventative Maintenance equipment.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] Equipment Details
Preventative Maintenance equipment details.
This endpoint returns a single record for the requested resource.
Requires a Equipment ID value (Preventative Maintenance equipment ID) to identify the record to fetch.
[Rest API] List Jobs
List Preventative Maintenance jobs.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] Job Details
Preventative Maintenance job details.
This endpoint returns a single record for the requested resource.
Requires a Job ID value (Preventative Maintenance job ID) to identify the record to fetch.
[Rest API] List Tasks
List Preventative Maintenance tasks.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] Task Details
Preventative Maintenance task details.
This endpoint returns a single record for the requested resource.
Requires a Task ID value (Preventative Maintenance task ID) to identify the record to fetch.
[Rest API] List Templates
List Preventative Maintenance job templates.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] Template Details
Preventative Maintenance template details.
This endpoint returns a single record for the requested resource.
Requires a Template ID value (Preventative Maintenance template ID) to identify the record to fetch.
[Rest API] List Amenities
List Reservations amenities.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] Amenity Details
Reservations amenity details.
This endpoint returns a single record for the requested resource.
Requires a Amenity ID value (Reservations amenity ID) to identify the record to fetch.
[Rest API] List Events
List Reservations events.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] Event Details
Reservations event details.
This endpoint returns a single record for the requested resource.
Requires a Event ID value (Reservations event ID) to identify the record to fetch.
[Rest API] List Reservations
List Reservations bookings.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] Reservation Details
Reservations booking details.
This endpoint returns a single record for the requested resource.
Requires a Reservation ID value (Reservations reservation ID) to identify the record to fetch.
[Rest API] List Service Requests
List Service Requests.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] Service Request Details
Service Request details.
This endpoint returns a single record for the requested resource.
Requires a Request ID value (Service Request ID) to identify the record to fetch.
[Rest API] List Service Types
List Service Request service types.
Nexla automatically handles pagination for this endpoint, iterating through all available pages so the full result set is ingested.
[Rest API] Service Type Details
Service Request service type details.
This endpoint returns a single record for the requested resource.
Requires a Service Type ID value (Service Request service type ID) to identify the record to fetch.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Electronic Tenant Solutions data sources can also be manually configured to ingest data from any valid Electronic Tenant Solutions API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Electronic Tenant Solutions data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
