canonical: https://jentic.com/apis/swaggerhub.palace/advertising-integration-api

# Palace Advertising Integration API

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.

## For AI agents

Programmatically all current available properties with detailed data, withdrawn or leased details. Covers 5 operations.

## Scope

Does not handle payments, communications, or crm - use for marketing only.

## Capabilities

- All current available properties with detailed data
- Withdrawn or leased details
- Array of images and meta data
- Get VaultRE property advertising portal codes
- Monitor Advertising Integration API operational status and events

## Use cases

### Marketing Operations

Use the Advertising Integration API to perform marketing operations programmatically. The API provides 5 endpoints covering core functionality including all current available properties with detailed data, withdrawn or leased details, array of images and meta data.

Example prompt: Call GET /v2AvailableProperties/JSON to all current available properties with detailed data

### Automated developers Management

Automate developers operations by combining multiple Advertising Integration API endpoints. Agents can withdrawn or leased details and then array of images and meta data in a single workflow.

Example prompt: Call GET /v2PreviousAvailableProperty/JSON/{PropertyCode} to withdrawn or leased details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Advertising Integration API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'all current available properties with detailed data', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v2AvailableProperties/JSON | All current available properties with detailed data |
| GET | /v2PreviousAvailableProperty/JSON/{PropertyCode} | Withdrawn or leased details |
| GET | /v2AvailablePropertyImages/JSON/{PropertyCode} | Array of images and meta data |
| GET | /v2AvailablePropertyImagesURL/JSON/{PropertyCode} | Array of image URL's and meta data |
| GET | /v2PalaceVaultAdvertisingCodes/JSON | Get VaultRE property advertising portal codes |

## Key resources

- **developers** — Operations available to regular developers

## Why Jentic

- **Setup:** Wiring the Advertising Integration API by hand means targeting the getpalace.com RestService host, tracking each property code through its JSON paths, and parsing the availability and image responses yourself. Through Jentic you install once, import the Advertising Integration API from the API Directory, and since it takes no credential your agent calls it straight away.
- **Permission scoping:** The Advertising Integration API puts the property code in the URL path (/v2AvailablePropertyImages/JSON/{PropertyCode}), so a rule can pin your agent to one property's advertising data and nothing else. Every endpoint here is a read, so you choose which GET operations it may call and no write reaches the service.
- **Credential handling:** The Advertising Integration API needs no credential to call, so there is nothing to store. If you add related services later, any credential is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list available properties' or 'get property advertising images', and Jentic returns the matching Advertising Integration API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the Advertising Integration API use?

The Advertising Integration API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I all current available properties with detailed data with the Advertising Integration API?

Yes. Use the GET /v2AvailableProperties/JSON endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Advertising Integration API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I all current available properties with detailed data through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'all current available properties with detailed data'. Jentic returns the matching Advertising Integration API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Advertising Integration API have?

The Advertising Integration API exposes 5 endpoints covering developers operations.

### Can I limit what my agent is allowed to do with the Advertising Integration API?

Yes. Because Jentic One is self-hosted, your own rules decide which operations the agent may call, so you can allow only the reads you want, such as GET /v2AvailableProperties/JSON or GET /v2PalaceVaultAdvertisingCodes/JSON. Since this API carries the property code in the URL path, for example GET /v2AvailablePropertyImages/JSON/{PropertyCode}, a rule can pin the agent to one property's advertising data and nothing else. Every endpoint is a read, so no write ever reaches the service.