API Agreement

The Terms of Service apply to all access to and use of the Services, including API access and API-related use. This API Agreement provides additional API-specific terms. Except where this API Agreement expressly provides a more specific API-related rule, all rights, restrictions, disclaimers, limitations, indemnities, remedies, and obligations in the Terms of Service continue to apply to the API, API Credentials, API Documentation, Authorized Applications, API Data, Client systems, End Users, and API-related activity.

If there is a conflict between this API Agreement and the Terms of Service, this API Agreement controls only with respect to API-specific access, API Credentials, Authorized Applications, API Data, API Documentation, API security, API display, API retention, API deletion, API misuse, API suspension, and API-related activity. Nothing in this API Agreement limits, narrows, waives, or reduces any broader right, protection, disclaimer, limitation of liability, indemnity, remedy, or enforcement right provided to YGL or YGL Related Parties under the Terms of Service unless this API Agreement expressly states that it does so.

If there is a conflict between this API Agreement and any separate YGL API order form, written API approval, API registration, feature-specific API term, API documentation requirement, security requirement, data-source requirement, MLS requirement, third-party provider requirement, or written instruction from YGL applicable to a specific endpoint, field, data source, application, integration, jurisdiction, or use case, the more specific requirement controls for that endpoint, field, data source, application, integration, jurisdiction, or use case.

The Privacy Policy governs YGL's handling of personal information, except where a more specific consent, disclosure, authorization, or feature-specific term applies. Third-party provider terms, MLS rules, listing-source requirements, and syndication-partner requirements may apply to Client's use of particular data, services, integrations, or features, but they do not limit Client's obligations to YGL or YGL's rights, protections, disclaimers, limitations, or remedies unless YGL expressly agrees otherwise in writing.

Capitalized terms not defined in this API Agreement have the meanings given to them in the Terms of Service. For purposes of this API Agreement:

• "API Credentials" means API keys, tokens, secrets, passwords, certificates, private keys, client IDs, OAuth credentials, access tokens, refresh tokens, session credentials, webhook signing secrets, or other credentials, identifiers, or authentication methods issued, enabled, or used for API access.
• "API Data" means any data, content, record, file, field, image, document, form, communication, listing, property information, lead information, access instruction, account information, metadata, log, response, payload, or other material accessed, received, transmitted, displayed, exported, stored, processed, or otherwise made available through or in connection with the API. API Data may include User Data, YGL Data, MLS Data, third-party data, publicly sourced data, listing-source data, Sensitive API Data, or other information, each of which remains subject to the applicable restrictions in the Terms of Service, this API Agreement, applicable law, MLS rules, listing-source requirements, third-party rights, and any other applicable terms.
• "API Documentation" means any API documentation, endpoint description, field definition, schema, technical instruction, integration guide, sample code, developer communication, developer portal content, changelog, or other technical material made available by YGL relating to the API.
• "Authorized Application" means only the specific software application, website, platform, system, integration, workflow, or other technical implementation approved by YGL in writing, through an API registration form, through the Services, through API Documentation, through an account setting, or through another API approval method made available by YGL. Client may not use the API for any other application, website, platform, integration, customer, business line, account, data product, workflow, or material use case without YGL's prior written approval.
• "Client" means, for purposes of API obligations, the Admin User, each Account User who requests, enables, configures, accesses, uses, receives, stores, transmits, displays, controls, or otherwise utilizes the API, API Credentials, an Authorized Application, or API Data, and any person or entity on whose behalf such API access or use is requested, enabled, configured, accessed, used, received, stored, transmitted, displayed, controlled, or otherwise utilized. This definition does not require YGL to determine whether any Account User has authority to bind any separate person or entity outside the Services.
• "Client System" means any server, database, cloud service, application, website, device, network, development environment, repository, vendor system, analytics system, logging system, backup system, or other system owned, controlled, operated, or used by or on behalf of Client in connection with the API, API Credentials, an Authorized Application, or API Data.
• “Consumer End User” means a prospective tenant, tenant, lead, or other individual acting in a personal capacity who interacts with an Authorized Application solely to view rental listings, inquire about rental listings, submit rental-related information, communicate about rental listings, or participate in another rental-related process expressly enabled by YGL through the API for the Authorized Application.
• "End User" means only (a) Client's employees, agents, contractors, administrators, developers, or other authorized personnel using an Authorized Application internally for Client's own lawful professional real estate activities, and (b) Consumer End Users. End Users do not include data customers, data licensees, data recipients, resellers, brokers, landlords, property managers, listing services, marketplaces, aggregators, competitors, advertising networks, artificial-intelligence systems, machine-learning systems, analytics products, or other third-party business customers unless YGL expressly approves such use in writing.
• "Listing Provider Information" means contact details, names, identities, entity information, communications, instructions, notes, or other information relating to landlords, property owners, property managers, management companies, listing agents, listing sources, listing providers, Listing Providers, brokerages, offices, or other persons or entities that supply, authorize, manage, update, advertise, show, lease, or otherwise participate in rental listings, to the extent such information is accessed or received through the API.
• “Sensitive API Data” means any personal information, non-public information, tenant information, occupant information, lead information, Listing Provider Information, contact information, communications, access-related information to the extent expressly made available through the API, or other information that is confidential, sensitive, regulated, non-public, security-sensitive, or potentially privacy-sensitive.
• "Tenant/Occupant Information" means contact details, names, identities, communications, showing-related information, property-access-related information, occupancy-related information, or other information relating to tenants, occupants, prospective tenants, applicants, guarantors, leads, or other individuals, to the extent such information is accessed or received through the API.

API access is a limited privilege, not a right. YGL may approve, deny, condition, limit, suspend, revoke, or terminate API access at any time in its sole discretion. YGL may require Client to identify each Authorized Application, the owner or operator of the Authorized Application, the intended use case, public-facing URLs, data fields used, data display methods, End User groups, security measures, hosting providers, vendors, jurisdictions, and any other information YGL reasonably requests.

For API access, API Credentials, applications, integrations, websites, platforms, workflows, or use cases that existed before Client completed an API registration form or before YGL collected complete Authorized Application information, YGL may treat such access as conditionally authorized only to the limited extent actually known to YGL, technically enabled by YGL, and not prohibited by this API Agreement, the Terms of Service, API Documentation, applicable law, MLS rules, listing-source requirements, third-party rights, or YGL instructions. Such conditional or legacy access does not approve any undisclosed application, website, platform, vendor, customer, business line, data product, public display, external distribution, data retention model, monetization model, End User group, jurisdiction, or material use case. YGL may require Client to submit, update, certify, or supplement API registration information for any existing API access or Authorized Application as a condition of continued API access.

Client may use the API only for the Authorized Application and approved use case. Client may not materially change an Authorized Application or API use case without YGL's prior written approval. Material changes include using a different website, application, platform, integration, vendor, database, customer group, End User group, business line, data display, data retention model, monetization model, jurisdiction, or external distribution method, or using API Data for a purpose not previously approved by YGL.

Client is responsible for ensuring that all information provided to YGL regarding an Authorized Application, API use case, vendor, Client System, End User group, data use, display method, retention practice, jurisdiction, and related API activity is complete, accurate, and current. If any such information is incomplete, inaccurate, outdated, omitted, or not previously provided, Client must promptly update or supplement the information upon request by YGL or before continuing API use if the missing or changed information is material to YGL’s approval, security review, compliance review, billing, risk assessment, or API-access controls.

YGL's approval of an Authorized Application, API registration, API endpoint, API field, API credential, display method, use case, or integration does not constitute legal advice, compliance advice, brokerage advice, verification of rights, verification of authority, approval of Client's conduct, or determination that Client's use complies with applicable law, MLS rules, listing-source requirements, third-party rights, privacy obligations, consumer-protection obligations, fair-housing laws, broker-fee laws, application-fee laws, landlord-tenant laws, advertising laws, or any separate agreement or obligation applicable to Client.

Client is solely responsible for ensuring that each Authorized Application and all API-related activity comply with this API Agreement, the Terms of Service, API Documentation, applicable law, MLS rules, listing-source requirements, third-party provider requirements, and all agreements or obligations applicable to Client.

Subject to Client's ongoing compliance with this API Agreement, the Terms of Service, API Documentation, and all applicable requirements, YGL grants Client a limited, revocable, non-exclusive, non-transferable, non-sublicensable license to access and use the API solely to build, operate, maintain, and support the Authorized Application for the approved use case and permitted End Users.

This license does not grant Client any ownership interest in the API, API Documentation, API Credentials, API Data, YGL Data, MLS Data, the Services, YGL intellectual property, YGL systems, YGL databases, YGL data structures, YGL software, YGL workflows, YGL field definitions, YGL compilations, YGL analytics, or any other YGL property. All rights not expressly granted are reserved by YGL and applicable rights holders.

The API license is conditioned on Client's continued compliance with all technical, security, rate-limit, display, refresh, retention, deletion, source-specific, MLS-specific, privacy, and use-case restrictions communicated by YGL. YGL may modify, condition, restrict, suspend, revoke, or terminate the license at any time as provided in this API Agreement and the Terms of Service.

API Credentials are confidential information of YGL. Client may use API Credentials only for the Authorized Application and approved use case. Client is responsible for all activity occurring through API Credentials issued to, enabled for, stored by, transmitted by, or used in connection with Client, the Account, an Account User, an Authorized Application, or a Client System, whether or not the activity was authorized by Client.

Client must implement appropriate technical and organizational safeguards for API Credentials, including secure generation, storage, rotation, logging, access control, and transmission. Client may not embed API Credentials in client-side code, browser-accessible code, public websites, public mobile applications, publicly distributed software, public repositories, screenshots, support tickets, unsecured logs, analytics tools, or any location where they could reasonably be accessed by unauthorized persons.

Client may allow API Credentials to be used only by Client's employees or individual contractors who have a legitimate need to access the API for the Authorized Application and who are bound by written confidentiality, security, and use restrictions at least as protective of YGL as this API Agreement. Client may not sell, rent, sublicense, assign, transfer, disclose, publish, lend, share, or otherwise provide API Credentials to any third party, vendor, customer, developer, contractor, platform, integration, or service provider without YGL's prior written approval.

Client must promptly rotate, revoke, disable, or replace API Credentials if Client knows or suspects that API Credentials have been lost, stolen, disclosed, leaked, misused, compromised, embedded in an insecure location, used for an unauthorized purpose, or accessed by an unauthorized person. YGL may rotate, revoke, disable, limit, suspend, or replace API Credentials at any time without liability, including for security, compliance, operational, risk-management, legal, listing-source, MLS, third-party-provider, or platform-integrity reasons.

Client may use API Data only within the Authorized Application, only for the approved use case, only for permitted End Users, only to the extent technically enabled by YGL, and only for Client's own lawful professional real estate activities. Permitted API use may include displaying approved rental listing information, supporting Client's internal listing-management or rental-marketing workflow, allowing Consumer End Users to view or inquire about specific rental listings, coordinating rental-related communications to the extent expressly enabled by YGL, or supporting other API uses expressly approved by YGL.

Client may use User Data submitted by Client through the API only as permitted by the Terms of Service, this API Agreement, applicable law, and all applicable consents, authorizations, disclosures, and third-party requirements. Data submitted, transmitted, imported, updated, or managed by Client through the API is User Data to the extent it is provided, authorized, approved, or made available by Client or on Client's behalf through the Services.

Client represents and warrants that Client has all rights, permissions, licenses, consents, authorizations, notices, legal bases, and authority necessary to submit, transmit, import, update, display, process, store, use, and authorize YGL to process any User Data, personal information, Sensitive API Data, listing information, images, documents, communications, or other materials transmitted to or through the API by Client or on Client's behalf.

Client is solely responsible for all data, content, records, fields, listings, settings, instructions, communications, account information, and other materials created, submitted, transmitted, imported, updated, modified, deleted, suppressed, overwritten, or otherwise changed through the API by Client, an Account User, an Authorized Application, Client System, vendor, contractor, developer, service provider, or anyone using API Credentials associated with Client or the Account. Client is solely responsible for testing, validating, monitoring, controlling, backing up, and implementing safeguards for all API requests, update logic, synchronization processes, automated scripts, bulk updates, field mappings, data transformations, and integration workflows. YGL is not responsible for any mistaken, unintended, incomplete, inaccurate, unauthorized, duplicative, excessive, or erroneous creation, update, modification, deletion, suppression, overwrite, synchronization, mapping, or other change made through the API by or on behalf of Client.

Client may not, and may not permit or assist any Account User, End User, vendor, customer, contractor, developer, service provider, affiliate, or third party to:

• sell, resell, rent, lease, sublicense, assign, transfer, disclose, publish, syndicate, redistribute, or otherwise provide API access, API Credentials, API Data, YGL Data, MLS Data, or Sensitive API Data to any third party except as expressly permitted by this API Agreement, API Documentation, an Authorized Application approval, or YGL in writing.;
• use the API or API Data for any application, platform, website, integration, customer, business line, data product, data service, workflow, or use case that is not an Authorized Application or approved use case;
• copy, scrape, extract, harvest, crawl, bulk download, bulk export, aggregate, compile, reconstruct, mirror, cache, store, or retain API Data except as expressly permitted by this API Agreement and the API Documentation;
• create, operate, support, verify, enhance, supplement, train, develop, or improve any separate product, database, listing service, rental marketplace, feed, website, marketing service, data service, analytics product, artificial-intelligence system, machine-learning model, scoring system, valuation model, competing service, or commercial or non-commercial service using API Data without YGL's prior written approval;
• use API Data for lead generation, broker recruitment, landlord recruitment, property-owner recruitment, property-manager recruitment, tenant solicitation outside the approved rental workflow, unsolicited marketing, mass messaging, spam, data brokering, resale, profiling, competitive analysis, benchmarking, reverse engineering, or any purpose not expressly approved by YGL;
• use the API to circumvent, avoid, disable, replace, interfere with, or bypass YGL platform features, billing, user seats, account permissions, access controls, compliance controls, disclosures, opt-ins, opt-outs, display restrictions, rate limits, export restrictions, source restrictions, MLS restrictions, YGL user interfaces, or YGL workflows;
• use the API in a manner that implies YGL sponsorship, endorsement, partnership, brokerage relationship, agency relationship, referral relationship, cooperation agreement, compensation arrangement, fee-sharing arrangement, listing authorization, advertising authorization, showing authorization, application-submission right, transaction approval, or legal compliance determination;
• use API Data to state or imply that any tenant, applicant, landlord, property owner, broker, agent, property manager, listing source, Listing Provider, or other party is required to work with, compensate, contact, apply through, submit materials through, or otherwise engage any particular broker, agent, user, Client, or third party unless that statement is accurate, lawful, properly authorized, and supported by a valid agreement outside the Services;
• modify, obscure, remove, suppress, or contradict any attribution, disclaimer, notice, disclosure, warning, source label, field label, branding, copyright notice, proprietary notice, opt-out mechanism, or other requirement provided by YGL or required by the API Documentation;
• access or use the API through automated tools, scripts, bots, credential sharing, session hijacking, token reuse, spoofing, unauthorized credentials, excessive traffic, denial-of-service activity, security testing without authorization, or any method that violates this API Agreement, the Terms of Service, API Documentation, or applicable law;
• use API Data for any unlawful, discriminatory, misleading, harassing, abusive, unsafe, fraudulent, invasive, privacy-violating, security-violating, or unrelated purpose; or
• attempt to reverse engineer, decompile, disassemble, copy, derive, test, probe, map, reproduce, or exploit YGL systems, databases, data structures, API endpoints, schemas, rate limits, business logic, security controls, source restrictions, or other non-public technical or operational information except to the limited extent expressly permitted by applicable law and not waivable by contract.

API Data remains subject to the ownership rights, licenses, restrictions, and third-party rights described in the Terms of Service and this API Agreement. Client acquires no ownership, proprietary, database, compilation, export, retention, derivative, commercial-exploitation, or continuing-access rights in API Data, YGL Data, MLS Data, listing-source data, third-party data, or Sensitive API Data.

YGL Data accessed or received through the API is provided under a limited, revocable, non-exclusive, non-transferable license solely for Client's lawful professional real estate activities through the Authorized Application and approved use case, subject to this API Agreement, the Terms of Service, API Documentation, applicable law, MLS rules, listing-source requirements, third-party rights, and any separate rights, permissions, authorizations, or agreements required outside the Services.

Client may not rely on API access, technical enablement, API Documentation, API fields, API responses, YGL approval of an Authorized Application, or YGL's continued provision of any endpoint, field, data source, listing, feed, feature, or credential as granting, verifying, creating, approving, or evidencing any right to advertise, market, syndicate, display, share, show, access, enter, lease, negotiate, submit applications for, collect fees for, claim compensation for, copy, download, export, retain, republish, redistribute, or otherwise use any listing, property information, communication, document, or other API Data except as expressly permitted through the API and independently authorized by applicable law, listing-source requirements, third-party rights, and any separate agreements or permissions required outside the Services.

Nothing in this API Agreement prevents Client from using information that Client lawfully obtained independently outside the Services and outside the API, provided that Client does not use the API, API Data, YGL Data, MLS Data, or data obtained through the Services to scrape, extract, reconstruct, verify, supplement, enhance, redistribute, republish, commercialize, or exploit that independently obtained information.

Client is solely responsible for the accuracy, legality, completeness, timeliness, display, formatting, labeling, disclosure, attribution, and use of API Data in an Authorized Application. API Data is provided on an "as is" and "as available" basis and may be inaccurate, incomplete, delayed, outdated, removed, restricted, mislabeled, unavailable, or subject to third-party rights, source restrictions, MLS restrictions, jurisdiction-specific restrictions, or other limitations.

Client must refresh API Data at intervals required by YGL, the API Documentation, applicable MLS rules, applicable listing-source requirements, or applicable law. If no specific refresh interval is stated, Client must use commercially reasonable refresh practices appropriate for rental listing data and must not display stale API Data as current. Client may not represent that API Data is complete, verified, current, available, legally compliant, authorized, or endorsed by YGL.

Client must promptly remove, suppress, modify, relabel, or update API Data in the Authorized Application and all Client Systems when YGL modifies, removes, suppresses, disables, expires, restricts, relabels, corrects, or stops making available the corresponding data through the API, or when YGL instructs Client to remove, suppress, modify, relabel, or update the data. Client must comply with takedown, suppression, removal, correction, or update instructions from YGL within the timeframe specified by YGL, or if no timeframe is specified, as soon as reasonably practicable.

Client is solely responsible for all disclosures, notices, labels, disclaimers, broker-license information, fair-housing disclosures, fee disclosures, compensation disclosures, source disclosures, data-source labels, advertising disclosures, privacy disclosures, and other information required for Client's display or use of API Data. YGL may require Client to display specific attribution, notices, disclaimers, labels, source information, timestamps, links, or other information in connection with API Data.

Client must not modify, omit, reformat, merge, manipulate, summarize, translate, map, normalize, or combine API Data in a manner that makes the data inaccurate, misleading, unlawful, discriminatory, incomplete, stale, wrongly attributed, improperly labeled, or inconsistent with YGL's instructions, API Documentation, source restrictions, MLS restrictions, or applicable law.

The API may make available certain information relating to tenants, occupants, landlords, property owners, property managers, management companies, listing agents, listing providers, Listing Providers, listing sources, or other parties associated with a rental listing, but only to the extent such information is expressly made available by YGL through the API, API Documentation, account configuration, written approval, or other API-access controls.

Client may use tenant information, occupant information, Listing Provider Information, listing-source information, contact information, and other sensitive API Data only for legitimate rental-related communications and activities directly connected to the applicable rental listing, including listing management, listing marketing, leasing communications, inquiry handling, rental-related coordination, and other lawful professional real estate activities permitted by this API Agreement, the Terms of Service, API Documentation, applicable law, listing-source requirements, third-party rights, and any separate agreements or permissions required outside the Services.

Client may not use tenant information, occupant information, Listing Provider Information, listing-source information, contact information, or other API Data for unsolicited marketing, mass messaging, spam, broker recruitment, landlord recruitment, tenant solicitation outside the Authorized Application, data enrichment, resale, data brokering, competitive analysis, unrelated advertising, unrelated communications, or any purpose not expressly permitted by this API Agreement, the Terms of Service, API Documentation, applicable law, and any applicable consent, authorization, listing-source requirement, or third-party right.

Client is responsible for maintaining appropriate confidentiality, security, access controls, and safeguards for all tenant information, occupant information, Listing Provider Information, listing-source information, contact information, and other sensitive API Data received through the API. Client may disclose such information only to Client’s authorized personnel, service providers, and End Users to the limited extent necessary for the Authorized Application and the permitted purposes described in this API Agreement.

Client may access, use, display, transmit, store, or process only the API endpoints, fields, data, functionality, and account resources that YGL expressly makes available to Client through the API. No other portion of the Services, account data, User Data, YGL Data, MLS Data, third-party data, workflow data, communications, documents, reports, records, credentials, settings, metadata, logs, or system information is made available through the API unless YGL expressly enables such access for Client and the specific Authorized Application.

Client may not attempt to access, retrieve, infer, scrape, extract, export, store, display, transmit, process, or use any data, field, endpoint, account resource, system function, or Service component that is not expressly enabled for Client through the API. Client may not use the API, API Credentials, API Documentation, error messages, response structures, metadata, system behavior, or other technical information to discover, infer, reconstruct, access, extract, or use data or functionality that YGL has not expressly made available to Client.

YGL may add, remove, restrict, suppress, modify, rename, reclassify, or disable any API endpoint, field, data category, response, function, permission, account resource, or API capability at any time, with or without notice, for any reason permitted by this API Agreement or the Terms of Service.

MLS Data remains subject to all applicable MLS rules, regulations, licenses, display requirements, technical standards, permitted-use restrictions, retention restrictions, and third-party rights. Client may not access, receive, store, display, transmit, export, download, use, or redistribute MLS Data through the API except to the extent expressly enabled by YGL, permitted by the applicable MLS, and permitted by all applicable MLS rules and agreements.

Client is solely responsible for reviewing, understanding, and complying with all MLS rules applicable to any MLS Data Client accesses, receives, displays, stores, transmits, exports, downloads, uses, or otherwise processes through the API. MLS rules may change at any time, and Client must comply with updated MLS rules immediately upon publication by the applicable MLS or upon notice from YGL.

API Data may be subject to listing-source requirements, syndication-partner requirements, third-party provider requirements, third-party intellectual-property rights, privacy restrictions, display restrictions, retention restrictions, takedown rights, use-case restrictions, and other limitations. Client must comply with all such requirements and restrictions whether communicated through the Terms of Service, this API Agreement, API Documentation, YGL instructions, source labels, field labels, data feeds, third-party terms, MLS rules, or applicable law.

YGL may disclose relevant API use information, Authorized Application information, Client information, data-use information, logs, or suspected misuse information to MLSs, listing sources, syndication partners, third-party providers, rights holders, auditors, regulators, law enforcement, or other relevant persons or entities when YGL believes in its sole discretion that disclosure is appropriate for compliance, enforcement, investigation, security, privacy, legal, contractual, source-protection, or platform-integrity purposes.

Any violation of MLS rules, listing-source requirements, third-party provider requirements, or third-party rights constitutes a material breach of this API Agreement and may result in immediate suspension or termination of API access, removal of data access, notice to applicable MLSs or listing sources, and legal action.

YGL provides the API solely as a technology interface for accessing certain functionality or data made available through the Services. YGL is not a real estate broker, salesperson, agent, landlord, property manager, leasing agent, fiduciary, representative, referral source, application reviewer, credit decision-maker, property-access provider, showing agent, or party to any rental transaction.

API access, API Data, API display, API Documentation, Authorized Application approval, technical enablement, YGL field labels, YGL source labels, YGL data-source categories, YGL provider-type labels, YGL listing-feed labels, YGL operational labels, or any other API-related function does not create, verify, approve, evidence, or imply any brokerage relationship, agency relationship, representation agreement, listing agreement, management agreement, advertising authorization, showing authorization, property-access authorization, cooperation agreement, referral arrangement, compensation agreement, commission agreement, fee-sharing arrangement, tenant-representation agreement, landlord-representation agreement, contractual relationship, fiduciary duty, or other legal relationship or obligation.

Access to or display of listing information through the API does not by itself grant Client, any Account User, any End User, or any third party any right to advertise, market, syndicate, display, share, show, access, enter, lease, negotiate, submit applications for, collect fees for, claim compensation for, or otherwise use a property listing. Any such rights, permissions, authorizations, relationships, obligations, or compensation arrangements are determined solely by the applicable parties, applicable law, MLS rules, listing-source requirements, third-party rights, and separate agreements entered into directly between the applicable parties outside the Services.

Any listing-related fee, commission, compensation, concession, co-brokerage, cooperation, referral, application-fee, screening-fee, move-in-fee, deposit, payment, or other amount displayed, transmitted, stored, published, syndicated, exported, or otherwise made available through the API is provided solely by users or third-party listing sources. YGL does not set, recommend, negotiate, require, collect, hold, distribute, split, guarantee, endorse, validate, approve, verify, advertise, or enforce such amounts or arrangements.

Client is solely responsible for determining whether Client, Account Users, employees, contractors, agents, brokers, landlords, property managers, property owners, listing sources, Listing Providers, End Users, or other parties have been properly engaged, contracted with, authorized, licensed, appointed, or permitted to advertise a listing, show a property, collect a fee, receive compensation, share compensation, pay compensation, disclose compensation, negotiate on behalf of any party, screen an applicant, submit an application, provide access, communicate with tenants or occupants, or otherwise participate in any rental transaction.

Client may not use the API, API Data, or an Authorized Application to create, imply, advertise, demand, collect, charge, shift, split, disguise, relabel, characterize, facilitate, or process any broker fee, commission, referral fee, application fee, screening fee, move-in fee, compensation arrangement, payment, reimbursement, deposit, rent, service fee, technology fee, or other charge in violation of applicable law, MLS rules, consumer-protection requirements, landlord-tenant laws, real estate licensing laws, broker-fee laws, application-fee laws, security-deposit laws, fair-housing laws, third-party provider requirements, or any agreement or obligation applicable to Client.

Client is solely responsible for each Authorized Application and for all interactions, communications, notices, disclosures, consents, authorizations, listing inquiries, rental-related communications, and rental-related workflows involving End Users or other third parties through or in connection with the Authorized Application.

Client must ensure that each Authorized Application accurately describes the source, nature, status, availability, and limitations of listing information and does not mislead End Users about YGL, API Data, listing availability, rental terms, fees, compensation, deposits, application requirements, showing access, tenant communications, broker relationships, landlord relationships, property-management relationships, or any party's legal obligations.

Client is solely responsible for obtaining, providing, maintaining, and complying with all notices, disclosures, consents, authorizations, opt-ins, opt-outs, privacy notices, permissible-purpose certifications, signatures, communication consents, SMS consents, email consents, payment authorizations, electronic-signature consents, application authorizations, screening authorizations, and records required by applicable law, provider terms, listing-source requirements, MLS rules, third-party rights, and any agreement or obligation applicable to Client.

Client must not use API Data or an Authorized Application to send or facilitate unlawful, unauthorized, misleading, excessive, harassing, discriminatory, or unrelated communications. Client is solely responsible for compliance with all telemarketing, text messaging, email, privacy, consumer-protection, fair-housing, advertising, and electronic-communications laws applicable to communications sent by or on behalf of Client or through an Authorized Application.

Any notices, reminders, confirmations, emails, SMS messages, in-platform notices, API-delivered communications, or other communications sent, initiated, triggered, displayed, or facilitated through an Authorized Application are provided by Client for Client's own purposes. Such communications do not substitute for any legally required notice, disclosure, consent, authorization, service requirement, adverse-action notice, pre-adverse-action notice, notice of entry, notice to quit, eviction notice, termination notice, or other legal notice unless Client independently determines that they satisfy applicable legal requirements. YGL does not guarantee that any communication will be delivered, received, opened, read, understood, legally sufficient, properly served, or sent within any legally required timeframe.

Client may store or cache API Data only to the limited extent necessary to operate the Authorized Application for the approved use case and permitted End Users, and only for as long as necessary for that active, authorized purpose. API access is not a permanent data feed and does not grant Client any continuing right to retain API Data after the applicable listing, inquiry, lead, showing, application, document, transaction, account, or other authorized purpose ends.

Client may not export, download, provide, or make available API Data to End Users or third parties in bulk, offline, syndicated, scraped, downloadable, machine-readable, searchable, reusable, or redistributable formats, including CSV, spreadsheet, database, feed, PDF, screenshot collection, archive, API, or bulk file format, except to the limited extent expressly approved by YGL in writing or expressly required for a specific authorized rental transaction and permitted by applicable law, MLS rules, listing-source requirements, and third-party rights.

Client must delete or destroy API Data when it is no longer necessary for the authorized purpose for which it was made available, when YGL instructs Client to delete it, when API access terminates, when the Authorized Application is no longer authorized, or when this API Agreement terminates. During any suspension, restriction, limitation, or revocation of API access, Client must stop accessing the API, stop using API Credentials, and stop displaying, distributing, refreshing, or newly processing API Data to the extent required by YGL, and must delete, destroy, suppress, return, or restrict API Data if YGL so instructs. Unless YGL states a shorter period or applicable law requires a shorter period, Client must complete deletion or destruction of YGL Data, MLS Data, Sensitive API Data, cached API Data, and stored API Data within thirty (30) days after termination of API access, termination of this API Agreement, deauthorization of the Authorized Application, or YGL's deletion instruction, except to the limited extent retention is required by applicable law.

If Client retains API Data because retention is required by applicable law, Client may retain only the minimum data required, only for the legally required retention period, and only in a secure, non-public, non-operational, access-restricted archive used solely for legal, regulatory, accounting, dispute-resolution, or compliance purposes. Client may not use legally retained API Data for marketing, solicitation, recruitment, data enrichment, analytics products, database building, resale, redistribution, display, or any other active business purpose.

Deletion from active systems may occur before deletion from encrypted backups, disaster-recovery systems, logs, or archival systems maintained in the ordinary course of business, provided that such retained copies are protected by appropriate safeguards, are not restored to active use except for legal, security, disaster-recovery, or compliance purposes, and are deleted or overwritten according to Client's ordinary backup-retention cycle. This backup exception does not permit Client to continue using, displaying, distributing, or processing API Data for ordinary business purposes after deletion is required.

Upon YGL's request, Client must certify in writing that Client has deleted, destroyed, suppressed, returned, or restricted API Data as required by this API Agreement and must provide reasonable information requested by YGL to verify compliance.

Client must maintain an information-security program appropriate to the nature, scope, volume, and sensitivity of API Data and Client's API use. Client's safeguards must include, at a minimum, encryption of API communications in transit, appropriate protection of API Data at rest, secure credential management, least-privilege access controls, multi-factor authentication for administrative access where reasonably available, vulnerability management, secure coding practices, logging and monitoring, timely patching, malware protection, vendor oversight, incident-response procedures, and employee and contractor confidentiality obligations.

Client must comply with all applicable privacy, data-security, consumer-protection, fair-housing, landlord-tenant, real estate licensing, consumer-reporting, electronic-communications, and other laws applicable to Client's access to or use of API Data. Client must not collect, access, store, transmit, display, disclose, or process personal information or Sensitive API Data through the API or an Authorized Application unless Client has all required rights, permissions, consents, authorizations, notices, legal bases, and safeguards necessary to do so.

Client must promptly, and in any event no later than seventy-two (72) hours after discovery, notify YGL in writing of any actual or suspected unauthorized access to, acquisition of, disclosure of, loss of, misuse of, alteration of, unavailability of, compromise of, or security incident involving the API, API Credentials, API Data, Sensitive API Data, an Authorized Application, or any Client System used in connection with the API ("Security Incident"). If the Security Incident involves actual or suspected compromise of API Credentials or active unauthorized API access, Client must notify YGL as soon as practicable and take immediate steps to stop the unauthorized access.

Client's notice must include all information reasonably requested by YGL to assess the scope, cause, impact, affected data, affected persons, affected systems, remediation, and legal or contractual implications of the Security Incident. Client must cooperate with YGL's investigation, preserve relevant logs and evidence, rotate or revoke affected credentials, remediate vulnerabilities, stop affected API activity, prevent recurrence, and provide updates as reasonably requested by YGL.

Client may not issue any public statement, customer notice, regulatory notice, press release, or third-party communication that identifies YGL, attributes fault to YGL, describes YGL systems, or describes YGL data or security practices in connection with a Security Incident without YGL's prior written approval, except to the extent Client is legally required to do so. If Client is legally required to provide such notice without prior approval, Client must provide YGL with advance notice and a reasonable opportunity to review the notice to the extent legally permitted.

Client is responsible for all costs, losses, claims, notices, remediation, investigation, forensic review, credit monitoring, regulatory response, third-party demands, damages, and expenses arising from or relating to a Security Incident caused by Client, Client's Account Users, Client's employees, contractors, developers, vendors, service providers, End Users, Client Systems, API Credentials, Authorized Application, or Client's failure to comply with this API Agreement.

Client is responsible for all acts and omissions of Client's employees, contractors, developers, vendors, service providers, hosting providers, consultants, affiliates, agents, representatives, and other persons or entities that access, process, store, transmit, display, support, develop, host, secure, or otherwise handle the API, API Credentials, API Data, an Authorized Application, or Client Systems on Client's behalf.

Client may not permit any vendor, contractor, developer, service provider, affiliate, or third party to access API Credentials, API Data, or Sensitive API Data unless that person or entity has a legitimate need to do so for the Authorized Application, is bound by written confidentiality, security, privacy, data-use, retention, deletion, and misuse restrictions at least as protective of YGL as this API Agreement, and is not using the API or API Data for its own independent purposes. For avoidance of doubt, API Credentials may be disclosed to, accessed by, or used by any vendor, contractor, developer, service provider, hosting provider, affiliate, or other third party only to the extent permitted under Section 5 and only if such access or use is expressly approved by YGL in writing or otherwise expressly authorized by YGL through the Services, API Documentation, account configuration, credential configuration, or other API-access controls.

YGL may require Client to identify vendors, contractors, developers, service providers, hosting providers, or other third parties involved in the Authorized Application or Client's API use. YGL may require Client to remove, restrict, replace, or obtain approval for any vendor, contractor, developer, service provider, hosting provider, or other third party if YGL believes that such person or entity creates legal, security, privacy, operational, compliance, source, MLS, or platform-integrity risk.

YGL may impose, modify, enforce, or remove limits on API calls, endpoints, fields, data volume, payload size, pagination, concurrency, frequency, refresh rates, historical access, caching, query scope, geographic scope, data-source access, listing-feed access, account access, or other technical or operational parameters. Client may not circumvent or attempt to circumvent any rate limit, technical restriction, access control, compliance control, source restriction, MLS restriction, field restriction, endpoint restriction, or other limitation.

YGL may modify, restrict, suspend, disable, remove, rename, reclassify, replace, deprecate, discontinue, or refuse to provide any API endpoint, field, method, payload, data source, feed, webhook, credential, Authorized Application, display method, export function, API Documentation, or API component at any time, with or without notice, if YGL believes doing so is appropriate for legal compliance, regulatory compliance, consumer protection, broker-fee compliance, application-fee compliance, privacy, data security, safety, platform integrity, MLS requirements, listing-source requirements, third-party provider requirements, syndication-partner requirements, risk management, operational needs, product changes, or the protection of YGL, users, Limited Individual Users, listing sources, third parties, or YGL Related Parties.

YGL may apply API controls differently based on jurisdiction, property location, account location, user location, billing location, transaction location, account type, user role, listing source, listing-feed type, provider type, data-source category, feature type, transaction type, property type, API use case, Authorized Application, End User type, complaint history, account activity, third-party provider requirement, MLS requirement, listing-source requirement, applicable law, regulatory guidance, enforcement risk, security risk, or other information available to YGL.

YGL may require additional acknowledgments, attestations, certifications, disclosures, notices, consents, confirmations, documentation, technical changes, security changes, display changes, deletion certifications, workflow steps, or feature-specific terms before allowing access to or continued use of any API endpoint, field, data source, feed, credential, Authorized Application, or API component.

YGL may monitor, log, analyze, review, audit, and investigate API usage, API Credentials, Authorized Applications, API Data access, API calls, API responses, error rates, usage patterns, endpoints, fields, rate-limit activity, security events, display methods, caching, data retention, data deletion, End User access, and other API-related activity for security, operations, billing, product, compliance, enforcement, source-protection, MLS, legal, audit, and platform-integrity purposes.

Upon YGL's request, Client must provide reasonable information, documentation, screenshots, data-flow diagrams, security descriptions, access-control descriptions, vendor information, use-case descriptions, field mappings, display examples, retention descriptions, deletion certifications, logs, audit records, and other information reasonably requested by YGL to verify compliance with this API Agreement, the Terms of Service, API Documentation, MLS rules, listing-source requirements, third-party provider requirements, applicable law, or YGL instructions.

YGL may test, inspect, or review any public-facing portion of an Authorized Application and may require Client to provide test credentials or reasonable access to non-public portions of the Authorized Application for compliance review. YGL is not obligated to conduct any audit or review, and any audit, review, test, approval, failure to audit, failure to object, or continued API access does not constitute approval of Client's use, legal advice, compliance advice, waiver, or acceptance of any non-compliance.

If Client fails to cooperate with a compliance review or audit, or if YGL believes that Client's API use may violate this API Agreement, the Terms of Service, API Documentation, applicable law, MLS rules, listing-source requirements, third-party provider requirements, privacy obligations, security obligations, third-party rights, or platform-integrity requirements, YGL may suspend, restrict, or terminate API access immediately without liability.

API access may require payment of API access fees, subscription fees, usage-based fees, transaction fees, overage fees, integration fees, support fees, setup fees, data-source fees, taxes, or other charges as described on the YGL website, in the Services, in the Account Billing page, in API Documentation, in an order form, in an invoice, in an account setting, or otherwise communicated by YGL. By requesting, enabling, accessing, or using the API, Client authorizes YGL and its payment processor to charge the payment method associated with the Account for all applicable API-related fees, taxes, and other charges.

The billing, payment, tax, cancellation, non-payment, collection, and billing-correction provisions of the Terms of Service apply to API fees and API-related charges. YGL's failure to bill, delay in billing, inadvertent omission of a charge, billing-system error, pricing calculation error, invoice error, tax calculation error, or other billing discrepancy does not waive YGL's right to charge and collect amounts validly incurred for API access or API use.

YGL may change API fees, billing methods, usage tiers, rate limits, included usage, overage fees, technical restrictions, or payment requirements upon reasonable notice posted through the Services, API Documentation, the developer portal, the Account Billing page, email, invoice, or other reasonable method. Continued API use after such notice constitutes acceptance of the updated fees, billing methods, usage tiers, and payment requirements.

Either party may terminate this API Agreement with respect to future API access at any time by discontinuing API access or providing notice as applicable. YGL may suspend, restrict, limit, disable, revoke, or terminate API access, API Credentials, an Authorized Application, access to specific endpoints, access to specific fields, access to specific data sources, or this API Agreement at any time, with or without cause, with or without prior notice, and without liability.

YGL may take immediate action if YGL believes that Client's API use may violate this API Agreement, the Terms of Service, API Documentation, applicable law, MLS rules, listing-source requirements, third-party provider requirements, privacy obligations, security obligations, third-party rights, End User rights, Limited Individual User rights, consumer-protection requirements, fair-housing laws, broker-fee laws, application-fee laws, landlord-tenant laws, real estate licensing laws, or the integrity, availability, security, or reputation of the Services, YGL, YGL Related Parties, users, listing sources, MLSs, syndication partners, or third parties.

Upon suspension, restriction, limitation, revocation, expiration, or termination of API access or this API Agreement, Client must immediately stop accessing and using the API, stop using API Credentials, disable API-related functionality in the Authorized Application to the extent required by YGL, stop displaying, distributing, refreshing, or newly processing API Data except as expressly permitted by YGL in writing, and delete, destroy, suppress, return, or restrict API Data as required by Section 14 or as otherwise instructed by YGL.

Suspension, revocation, expiration, or termination of API access does not relieve Client of responsibility for any fees, taxes, API activity, API Data use, API Data retention, API Data deletion, Security Incident, indemnification obligation, confidentiality obligation, or violation occurring before suspension, revocation, expiration, or termination. YGL is not required to provide continued API access, transition assistance, historical data, exports, backups, replacement feeds, migration tools, or support after suspension, revocation, expiration, or termination unless YGL expressly agrees otherwise in writing.

YGL does not guarantee that the API, API Credentials, API Documentation, any endpoint, data source, feed, webhook, field, Authorized Application approval, integration, API response, or API Data will be uninterrupted, error-free, secure, timely, complete, accurate, backward-compatible, continuously available, or available at any particular volume, speed, latency, frequency, format, or level of functionality.

The API may be unavailable, delayed, limited, suspended, interrupted, degraded, modified, or discontinued due to maintenance, updates, software errors, system failures, hosting-provider issues, internet or telecommunications failures, third-party service failures, MLS or listing-source issues, syndication-partner issues, payment-processor issues, credit-reporting or screening-provider issues, electronic-signature-provider issues, messaging-provider issues, cyberattacks, security incidents, excessive traffic, emergency measures, legal or compliance concerns, product changes, operational needs, or other causes.

Unless YGL expressly agrees otherwise in a separate written agreement signed by YGL, YGL does not provide any API service-level agreement, uptime commitment, support-response commitment, backward-compatibility commitment, data-recovery commitment, migration commitment, delivery commitment, processing-time commitment, endpoint-continuity commitment, or guarantee that any API component will remain available, operate without interruption, or be restored within any particular period of time.

YGL may provide API support, technical assistance, examples, documentation, or implementation guidance in its discretion. Any such assistance is provided for convenience only and does not make YGL responsible for Client's Authorized Application, Client Systems, compliance, security, data use, display, or implementation decisions.

YGL has no obligation to reverse, undo, restore, reconstruct, correct, investigate, repair, support, or otherwise remediate any mistaken, unintended, incomplete, inaccurate, unauthorized, duplicative, excessive, or erroneous API request, update, modification, deletion, suppression, overwrite, synchronization, mapping, bulk action, or other change made by or on behalf of Client, except to the extent YGL expressly agrees otherwise in writing. If YGL provides assistance, restoration, data correction, investigation, support, export, backup retrieval, or remediation, such assistance is provided in YGL’s discretion, does not create any continuing obligation, warranty, service-level commitment, data-recovery commitment, or admission of responsibility, and may be conditioned on payment of applicable fees.

API Credentials, non-public API Documentation, non-public endpoint information, non-public schema information, non-public rate-limit information, non-public technical information, non-public security information, non-public business information, and non-public API Data are confidential information of YGL or applicable rights holders. Client must protect such information from unauthorized access, use, disclosure, copying, or distribution using at least the same degree of care that Client uses to protect its own confidential information, and in no event less than reasonable care.

As between Client and YGL, YGL owns and retains all rights, title, and interest in and to the API, API Documentation, API Credentials, Services, software, platform, websites, applications, tools, workflows, databases, data structures, user interface, design, layout, functionality, templates, reports, analytics, algorithms, business processes, know-how, trademarks, service marks, logos, trade names, and other YGL intellectual property, excluding User Data, MLS Data, and third-party materials that YGL does not own.

Client may not copy, reproduce, modify, adapt, translate, create derivative works from, reverse engineer, decompile, disassemble, sell, resell, license, sublicense, rent, lease, distribute, publish, display, exploit, or otherwise use the API, API Documentation, API Credentials, Services, or YGL intellectual property except as expressly permitted by this API Agreement or authorized by YGL in writing.

Client may not use YGL's name, trademarks, service marks, logos, trade names, branding, screenshots, interface elements, or other identifying materials in any manner, or suggest any sponsorship, endorsement, affiliation, approval, partnership, brokerage relationship, agency relationship, referral relationship, or cooperation arrangement by or with YGL, without YGL's prior written consent. Client must not represent that an Authorized Application is operated by YGL unless YGL expressly authorizes that representation in writing.

If Client provides YGL with suggestions, ideas, requests, comments, feedback, bug reports, enhancement requests, or recommendations regarding the API, API Documentation, Services, data fields, workflows, or related features, Client grants YGL a perpetual, irrevocable, worldwide, royalty-free, fully paid, transferable, and sublicensable license to use, copy, modify, implement, commercialize, and otherwise exploit such feedback for any purpose without restriction or compensation to Client.

The disclaimers, warranty exclusions, limitations of liability, exclusions of damages, indemnification obligations, and related protections in the Terms of Service apply to this API Agreement, the API, API Credentials, API Documentation, API Data, Authorized Applications, Client Systems, End Users, API-related activity, and all claims arising out of or relating to API access or use.

Except as expressly stated in this API Agreement or the Terms of Service, YGL provides the API, API Credentials, API Documentation, API Data, endpoints, fields, data sources, feeds, webhooks, and related API functionality "AS IS" and "AS AVAILABLE," without warranties of any kind, express or implied. YGL specifically disclaims all implied warranties of merchantability, fitness for a particular purpose, title, non-infringement, accuracy, completeness, availability, timeliness, security, compatibility, and uninterrupted operation.

To the maximum extent permitted by law, for all API-related claims, the total cumulative liability of YGL and YGL Related Parties arising out of or relating to this API Agreement, the API, API Credentials, API Documentation, API Data, an Authorized Application, Client Systems, API access, API use, API suspension, API termination, API errors, API unavailability, API modifications, API Data, or any API-related activity shall not exceed the greater of: (a) the total API-specific fees paid by Client to YGL for API access during the twelve (12) months preceding the event giving rise to the claim, excluding fees paid for non-API Services; or (b) five hundred dollars ($500). If no separate API-specific fee is charged, the cap in clause (b) applies. Nothing in this paragraph expands YGL's liability beyond any limitation that would otherwise apply under the Terms of Service.

Client agrees to indemnify, defend, and hold harmless YGL and YGL Related Parties from and against any and all claims, demands, actions, proceedings, investigations, liabilities, damages, losses, fines, penalties, settlements, costs, and expenses, including reasonable attorneys' fees, arising out of or relating to:

• Client's violation of this API Agreement, the Terms of Service, API Documentation, applicable law, MLS rules, listing-source requirements, third-party provider requirements, third-party rights, or any agreement or obligation applicable to Client;
• Client's Authorized Application, including any claim by or relating to an End User, Consumer End User, Account User, landlord, property owner, property manager, broker, agent, tenant, applicant, guarantor, occupant, listing source, MLS, syndication partner, third-party provider, customer, vendor, regulator, advocacy organization, or other third party;
• Client's display, publication, transmission, storage, retention, deletion, export, download, modification, suppression, labeling, relabeling, use, misuse, reliance on, failure to update, or unauthorized use of API Data, including any use or alleged use of API Data in connection with advertising, marketing, syndication, communications, fees, compensation, deposits, rental transactions, property access, showings, applications, screening, documents, electronic signatures, payments, or other rental-related workflows, whether or not such functionality is supported by the API, enabled for Client, or authorized by YGL;
• Client's failure to remove, suppress, update, relabel, delete, destroy, restrict, or certify deletion of API Data as required by YGL, this API Agreement, API Documentation, applicable law, MLS rules, listing-source requirements, or third-party rights;
• any allegation that Client lacked rights, permissions, licenses, authority, approvals, consents, notices, legal bases, or authorizations for Client's API use, User Data, API Data use, Authorized Application, communications, End User interactions, listings, photographs, documents, forms, access-related information, rental-related information, or any rental-related workflow, transaction, communication, or activity connected to Client's API use or Authorized Application;
• any allegation that Client's Authorized Application, API use, User Data, API Data use, communications, displays, workflows, or rental-related activities infringe, misappropriate, or violate any intellectual property, privacy, publicity, contractual, property, consumer-protection, data-security, fair-housing, landlord-tenant, real estate licensing, broker-fee, application-fee, security-deposit, advertising, telemarketing, email, SMS, credit-reporting, electronic-signature, payment-processing, or other right or law, whether or not such activity is supported by the API, enabled for Client, or authorized by YGL;
• any Security Incident, API Credential compromise, unauthorized access, credential misuse, data misuse, privacy violation, security violation, failure to safeguard API Data, or failure to notify YGL as required by this API Agreement;
• Client's vendors, contractors, developers, service providers, hosting providers, affiliates, agents, employees, administrators, Account Users, End Users, or anyone accessing or using the API, API Credentials, API Data, Client Systems, or the Authorized Application through or on behalf of Client;
• any violation of MLS rules, listing-source requirements, third-party provider requirements, third-party rights, or source-specific restrictions;
• any claim that the Authorized Application, Client's API use, or Client's use, misuse, display, communication, or handling of API Data created, implied, advertised, required, facilitated, or misrepresented any brokerage relationship, agency relationship, listing agreement, showing authorization, property-access right, application right, screening right, document-submission right, compensation arrangement, fee, commission, referral, payment, rental requirement, transaction obligation, YGL endorsement, YGL approval, or YGL participation in a rental transaction, whether or not such functionality is supported by the API, enabled for Client, or authorized by YGL;
• any payment dispute, chargeback, refund request, billing dispute, unpaid fee, reversed payment, tax issue, collection matter, or payment-processing issue arising from Client's API access, Authorized Application, Account, End User activity, or API-related payment instructions; or
• any dispute between Client and any Account User, End User, Consumer End User, tenant, applicant, guarantor, occupant, landlord, property owner, property manager, broker, agent, listing source, MLS, syndication partner, third-party provider, vendor, customer, or other third party arising out of or relating to the API, API Data, an Authorized Application, communications, listings, fees, compensation, property access, showings, applications, documents, payments, rental transactions, or any other rental-related communication, workflow, claim, or activity connected to Client's API use or Authorized Application, whether or not such functionality is supported by the API, enabled for Client, or authorized by YGL.

YGL reserves the right, at Client's expense, to assume the exclusive defense and control of any matter subject to indemnification. Client must cooperate with YGL's defense of such claims and may not settle any claim in a manner that imposes any obligation, admission, liability, payment, restriction, or other burden on YGL or any YGL Related Party without YGL's prior written consent.

Client acknowledges that unauthorized access to or misuse of the API, API Credentials, API Documentation, API Data, YGL Data, MLS Data, Sensitive API Data, Tenant/Occupant Information, Listing Provider Information, YGL systems, YGL intellectual property, YGL confidential information, or the Services may cause immediate and irreparable harm to YGL, YGL Related Parties, users, Limited Individual Users, listing sources, MLSs, syndication partners, third-party providers, rights holders, or other third parties, for which monetary damages may be inadequate.

YGL may seek emergency, temporary, preliminary, or permanent injunctive or equitable relief in a court of competent jurisdiction, without first completing any pre-arbitration notice or cure period, to prevent, stop, investigate, remediate, or remedy actual or threatened unauthorized access, unauthorized API use, API Credential misuse, credential compromise, security violations, data theft, scraping, automated extraction, bulk downloading, bulk export, data misuse, misuse of YGL Data, misuse of MLS Data, misuse of Sensitive API Data, misuse of Tenant/Occupant Information, misuse of Listing Provider Information, violation of confidentiality or privacy obligations, infringement or misuse of intellectual property, interference with the operation or security of the Services, or other conduct that may cause immediate or irreparable harm.

A request for injunctive or equitable relief does not waive arbitration for any remaining claims that are subject to arbitration under the Terms of Service or this API Agreement.

The arbitration, class action waiver, coordinated filing, emergency and injunctive relief, small-claims, severability, governing-law, jurisdiction, and dispute-resolution provisions in the Terms of Service apply to this API Agreement and to all disputes, claims, demands, actions, causes of action, proceedings, liabilities, damages, losses, costs, or expenses arising out of or relating to this API Agreement, the API, API Credentials, API Documentation, API Data, Authorized Applications, Client Systems, API access, API use, API suspension, API termination, API misuse, API security, API Data display, API Data retention, API Data deletion, End User activity, or any other API-related activity.

For purposes of the Terms of Service dispute-resolution provisions, API-related disputes are disputes arising out of or relating to the Services, the Account, Account User access to or use of the Services, User Data, YGL Data, MLS Data, communications, transactions, payments, fees, charges, integrations, third-party services, or interactions made available, processed, transmitted, stored, displayed, or facilitated through the Services.

The emergency and injunctive relief exception in the Terms of Service includes API-related misuse, including unauthorized access, unauthorized API use, API Credential misuse, credential compromise, security violations, data theft, scraping, automated extraction, bulk downloading, bulk export, data misuse, misuse of YGL Data, misuse of MLS Data, misuse of Sensitive API Data, misuse of Tenant/Occupant Information, misuse of Listing Provider Information, violation of confidentiality or privacy obligations, infringement or misuse of intellectual property, and interference with the operation, availability, integrity, or security of the API or Services.

This API Agreement is governed by the laws specified in the Terms of Service. Any court proceeding permitted under the Terms of Service or this API Agreement shall be brought in the courts specified in the Terms of Service, except that YGL may seek injunctive or equitable relief in any court of competent jurisdiction where necessary to prevent, stop, investigate, remediate, or remedy immediate or irreparable harm.

Entire Agreement. This API Agreement, together with the Terms of Service, Privacy Policy, API Documentation, API registration, API approvals, order forms, invoices, account settings, feature-specific API terms, and any other YGL terms incorporated by reference or accepted in connection with API access, constitutes the entire agreement between Client and YGL regarding API access and supersedes all prior or contemporaneous understandings, communications, proposals, representations, or agreements regarding API access.

Notices. YGL may provide API-related notices by email, in-platform notice, account dashboard notice, developer portal notice, API Documentation notice, API response notice, posting through the Services, posting on the YGL website, invoice notice, billing page notice, or other reasonable method. Notices sent to Client are deemed given when sent, posted, or made available. Client is responsible for maintaining accurate account, technical, security, billing, and developer contact information. Legal notices to YGL must be sent to legal@yougotlistings.com and to any additional address or notice method YGL may designate through the Services or on its website.

Assignment. Client may not assign, transfer, delegate, sublicense, or otherwise provide this API Agreement, API access, API Credentials, an Authorized Application approval, or any rights or obligations under this API Agreement without YGL's prior written consent. Any attempted assignment, transfer, delegation, sublicense, or unauthorized sharing is void. YGL may assign or transfer this API Agreement, in whole or in part, and may delegate, subcontract, license, sublicense, or otherwise arrange for the performance, operation, hosting, support, enforcement, or exercise of any rights or obligations under this API Agreement, without Client's consent, including in connection with a merger, acquisition, corporate reorganization, sale of assets, financing, change of control, or transfer of the Services, API, data, or related business operations.

No Waiver. YGL's failure or delay in exercising any right, remedy, power, or privilege under this API Agreement does not constitute a waiver of that right, remedy, power, or privilege. Any waiver must be in writing and signed by YGL to be effective.

Severability. If any provision of this API Agreement is found to be invalid, unlawful, or unenforceable, that provision will be enforced to the maximum extent permitted by law, and the remaining provisions will remain in full force and effect, except as otherwise provided in the Terms of Service arbitration and class action waiver provisions.

No Third-Party Beneficiaries. Except as expressly stated in this API Agreement or the Terms of Service, this API Agreement does not create any third-party beneficiary rights in any person or entity that is not a party to this API Agreement. YGL Related Parties may enforce protections expressly provided to them under this API Agreement and the Terms of Service.

Relationship of the Parties. Nothing in this API Agreement creates any partnership, joint venture, agency, fiduciary, employment, franchise, brokerage, representation, referral, compensation, commission, fee-sharing, landlord-tenant, property-management, or other special relationship between Client and YGL. Client and YGL are independent contracting parties.

Headings. Section titles and headings are provided for convenience only and do not affect the interpretation of this API Agreement.

Electronic Acceptance. Electronic acceptance of this API Agreement, activation of API access, creation or use of API Credentials, use of the API, connection of an Authorized Application, continued API use after notice of updated terms, or other electronic indication of assent has the same legal effect as a handwritten signature to the fullest extent permitted by law.

Survival. Any provisions that by their nature should survive termination shall survive termination of this API Agreement and API access, including provisions relating to definitions, order of precedence, API Data ownership and restrictions, prohibited uses, Sensitive API Data, MLS Data, listing-source restrictions, no brokerage/no relationship provisions, End User responsibilities, retention, deletion, certification, security, Security Incidents, vendors, monitoring, audit, fees, unpaid amounts, billing corrections, taxes, confidentiality, intellectual property, branding restrictions, disclaimers, limitation of liability, indemnification, injunctive relief, arbitration, class action waiver, governing law, jurisdiction, notices, no waiver, assignment, and any other provisions necessary to interpret or enforce this API Agreement.