[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create your own SiteMinder API

> SiteMinder: a read-only Direct Booking API on the plans with Direct bookings, other APIs for partners. With Cotlet you build your own: do a job once with your AI agent, save it as an endpoint and call it from n8n or code.

Source: https://cotlet.dev/integrations/api/siteminder

SiteMinder's Direct Booking API reads a hotel's rates and availability with a key an admin generates, on the plans with Direct bookings; its other APIs need a partnership agreement (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your SiteMinder account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in SiteMinder session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=siteminder)

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by SiteMinder. SiteMinder is a trademark of its owner. If SiteMinder's own integrations cover what you need, use them first.

curl Node.js Python

curl

```
curl -X POST "https://cotlet.dev/api/v1/custom/reservations-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-21"}'
```

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/reservations-for-day";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ date: "2026-11-21" }),
});
const { data } = await res.json();
```

Python

```
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/reservations-for-day",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-21"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"guest": "Anna B.",
"room_type": "Deluxe King",
"channel": "Booking.com",
"nights": 2,
"status": "confirmed"
},
{
"guest": "Leo P.",
"room_type": "Twin",
"channel": "Direct",
"nights": 1,
"status": "confirmed"
}
]
}
```

01 Build

## How do you build a SiteMinder endpoint with Cotlet?

1. 01  
authx.siteminder.com  
Signed in  
### Sign in to SiteMinder in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List tomorrow's arrivals with guest, room type, channel and nights.  
### Do the job once with your agent.  
For example: "List tomorrow's arrivals with guest, room type, channel and nights."
3. 03  
Save endpoint  
Name  
reservations-for-day  
Input  
date  
Returns  
guest, room\_type, channel, nights, status  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a date or a room type, and the fields it returns.
4. 04  
$ POST /api/v1/custom/reservations-for-day  
200 OK  
### Call it with your Cotlet API key.  
Each endpoint gets its own address, `POST https://cotlet.dev/api/v1/custom/<name>`. You send JSON in and get JSON back, from the same signed-in SiteMinder session.

02 Endpoints

## Example endpoints you could build for SiteMinder

Cotlet ships no fixed list of SiteMinder endpoints. You decide which endpoints you build and what each one returns.

- POST `/api/v1/custom/reservations-for-day`  
### Arrivals for a day  
Guest, room type, channel, nights and status for each reservation
- POST `/api/v1/custom/rates-for-dates`  
### Rates for dates  
Rate and rooms left per room type and night
- POST `/api/v1/custom/reservations-by-channel`  
### Reservations by channel  
Count and revenue per channel for a period
- POST `/api/v1/custom/cancellations`  
### Cancellations for a period  
Guest, dates, room type and channel of each cancellation
- POST `/api/v1/custom/set-rate` writes  
### Set a rate  
The new rate for a room type and night, after your OK
- POST `/api/v1/custom/<name>`

A call to an endpoint you built could look like this:

Request

```
curl -X POST "https://cotlet.dev/api/v1/custom/reservations-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-21"}'
```

The answer is JSON, with your fields under `data`:

Response · 200 OK

```
{
"data": [
{
"guest": "Anna B.",
"room_type": "Deluxe King",
"channel": "Booking.com",
"nights": 2,
"status": "confirmed"
},
{
"guest": "Leo P.",
"room_type": "Twin",
"channel": "Direct",
"nights": 1,
"status": "confirmed"
}
]
}
```

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

## What can you use your SiteMinder endpoints for?

- Schedule Cotlet endpoint Slack or email  
### A morning arrivals list in n8n or Make.  
Today's arrivals and new cancellations, sent to the front desk by Slack or email.
- Schedule endpoint Google Sheets  
### A rate sheet.  
Rates and rooms left for the next 30 nights, pulled into Google Sheets each morning.
- Monthly endpoint Dashboard  
### A channel report.  
Reservations by channel each month, for your own dashboard.
- Chat agent endpoint rooms left  
### Your own guest assistant.  
A chat agent that checks rooms left for a night before it answers a guest.

04 Access

## What can an endpoint see and change?

An endpoint works in your own SiteMinder session, so it can read and change only what your SiteMinder login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as setting a rate, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

DRY RUN · nothing sent

$ POST /api/v1/custom/set-rate

would POST authx.siteminder.com/... set Deluxe King rate to $217 on 28 Nov

`set-rate`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does SiteMinder have an official API?

SiteMinder: the Direct Booking API reads property data, rates and availability, and "your account must have an active Direct Booking subscription". For the other APIs, "Before you can access SiteMinder APIs, you need to complete a partnership agreement with our Ecosystem team." Its MCP server is for channel partners (checked 20 Nov 2026). The full picture with sources: [Does SiteMinder have an API or MCP server?](https://cotlet.dev/api-status/siteminder.md)

Want ChatGPT or Claude to work in SiteMinder instead of code? See the [SiteMinder MCP server](https://cotlet.dev/integrations/siteminder-api-mcp-server.md).

2/3

Official API

Read only, higher plan

[Full API & MCP report](https://cotlet.dev/api-status/siteminder.md)

06 Pricing

## What does it cost?

per successful call

 10 credits

when a call fails

 0

in the smallest pack

≈ 500 calls

free trial, no card

 7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

## SiteMinder API with Cotlet: questions

### Is this an official SiteMinder API?

No. Cotlet is independent and not affiliated with SiteMinder. The endpoints you build run in your own signed-in SiteMinder account.

### Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

### What happens when SiteMinder changes its screens?

An endpoint works while SiteMinder works the way it did when you built it. If SiteMinder changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

### How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

POST /api/v1/custom/<name>

## Build your first SiteMinder endpoint

Sign in once, do the job with your agent and save it as an endpoint.

[Try it free now](https://cotlet.dev/app/signup?app=siteminder)

No card. Takes about 5 minutes.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
