The 'Advertising' integration focuses on allowing 3rd party systems and customized websites to sync available properties from Palace to display up-to-date advertising on a company's website.<BR><BR><BR>The 'Advertising Integration' area does NOT require an upgrade from a 'Standard' API account to a 'Premium' API Account. There is a NO cost involved in using these contracts unless you are a 3rd Par. The API exposes 5 endpoints.
5 endpoints<p>The 'Agreement' integration focuses on allowing 3rd party systems to sync contacts / properties from Palace and create new 'Owners', 'Properties', 'Tenancies' and 'Sub-Tenants'. It also allows for sending official 'Agreements' back to Palace as a file document (PDF Recommended).<br><br>The 'Agreement Integration' area does NOT require an upgrade from a 'Standard' API account to a 'Premium' API . The API exposes 14 endpoints.
14 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.