Otelpuan API

The Otelpuan API for hotel search, prices, and reviews.

Find a hotel, compare rooms and prices for your dates, and read guest feedback with REST or MCP.

REQUEST GET
USE CASE Find hotel suggestions and pass hotel_id directly to reviews.
curl "https://api.stayapi.com/v1/otelpuan/search" \
  -G \
  -H "x-api-key: $STAYAPI_KEY" \
  -d "query=Turkler"
RESPONSE 200 OK
2.41s
{
  "success": true,
  "query": "Turkler",
  "hotels": [
    {
      "hotel_id": "25322",
      "name": "Türkler Otel",
      "url": "https://www.otelpuan.com/Turkler-Otel",
      "location": "Trabzon Şehir Merkezi"
    }
  ],
  "total": 1
}
99.9% uptime ~3s avg response Live, not cached

Trusted by hospitality teams at

Overview

What the Otelpuan API gives you.

Search hotel suggestions by name, or resolve a public hotel URL when you have one. Both return hotel_id for guest reviews; search results go directly to reviews without a resolver call. Search is not exhaustive city inventory.

Reviews are paginated in groups of up to 10. Stay months use YYYY-MM; stay_date_text retains the source format. Publication dates are unavailable.

Keep the resolver result for the display name, URL, and aggregate rating. ID-based reviews return null for these fields and include individual guest ratings and the review count.

Use the hotel URL returned by Search for Rooms & prices. Supply stay dates and guests to read board plans, stay totals, daily prices, and cancellation terms. Reviews continue to use hotel_id.

01

Start with a name or URL

Search hotel names or resolve a public hotel URL, then request reviews by ID.

02

Prices for your stay

Use the hotel URL, dates, and guests to check room offers and cancellation terms.

03

REST and MCP

Search, resolve URLs, check room prices, and read reviews with your StayAPI key.

Use cases

What teams build on the Otelpuan API.

The same endpoints, pointed at different jobs. These are the ones we see most.

01

Guest feedback summaries.

Summarize recurring themes in the returned comments.

02

Rating analysis.

Keep individual guest scores alongside the aggregate 0–10 rating.

03

Review collection.

Request pages in sequence and use review IDs to identify records.

04

Room comparison.

Compare board plans and cancellation terms for the same stay and guest count.

Also over MCP

Otelpuan data, inside your AI agent.

The same endpoints are exposed as MCP tools. Connect Claude, Cursor, or Claude Code, ask in plain English, and the agent calls the tool and answers from live Otelpuan data.

Pricing

50 free requests on signup.
Pick a plan when you need more.

Flat monthly plans, every endpoint included on every plan. 1 request = 1 credit. No per-endpoint multipliers, no surprise overages.

01 Free

Wire it up. See the schema.

$0 to start
50 credits on signup
  • 50 free requests
  • Every endpoint included
  • No credit card required
  • Same schema as paid
Start free
02 Basic

Kick the tires in production.

$49 per month
1,500 requests / mo
  • 1,500 requests / month
  • Every endpoint included
  • Per-endpoint usage dashboard
  • Email support
Start Basic
50% off
04 Scale

Daily pulls in production.

$900 $450 per month
100,000 requests / mo
  • 100,000 requests / month
  • Every endpoint included
  • Per-endpoint usage dashboard
  • Priority email support
Start scaling
05 Custom

Above 100k / month, annual terms, white-glove onboarding.

Let's talk
1M+ requests / mo
  • 1M+ requests / month
  • Volume rate on the call
  • Per-endpoint usage dashboard
  • Priority email + Slack support
Book a scoping call

Every plan ships every endpoint. Same uptime, same schema, same response time.

Questions

What people ask about the Otelpuan API.

Don't see your question? Email us at info@stayapi.com.

How do I get Otelpuan hotel reviews?

Send hotel_id to GET /v1/otelpuan/hotel/reviews with your X-API-Key header. If you only have a public hotel URL, resolve it with GET /v1/otelpuan/hotel/url-to-id first.

How many reviews are returned per page?

Up to 10. Start with page=1 and follow page_info.has_next_page.

Are review publication dates available?

No. review_date is null. stay_date is a YYYY-MM stay month; stay_date_text preserves source text such as 2026 Ocak and describes the stay, not publication.

Can I filter or sort the reviews?

No sorting or filtering parameters are supported. The endpoint preserves the source order.

How do I check rooms and prices?

Pass the hotel URL from Search, check_in, check_out, and guests to GET /v1/otelpuan/hotel/rooms or otelpuan_hotel_rooms. Adults default to 2; optional child_ages accepts up to 4 comma-separated ages from 0–16. Preserve the returned total_price; daily amounts may not sum to the provider stay total; both are preserved as supplied. An empty rooms array is a successful result.

Does search return every hotel in a city?

No. Search returns hotel-name suggestions. There are no page, limit, or filter controls; an empty match succeeds with an empty hotels array.

Two ways to start.

Both end with live Otelpuan data in your stack. The fast path is on the left.

01 · the fast path

Try it free

50 free requests after sign up. Fastest way to see if the schema fits.

Start free
  • Live API key in 30 seconds
  • No credit card required
  • Same schema as paid
02 · the scoped path

Book a scoping call

15 minutes. Volume + endpoint mix. Walk out with a quote.

Book a demo
  • Quote on the call, not after
  • Engineering, not sales
  • No deck, no slides