The Husly API

The API is part of the Agency plan. The account owner creates a key under My account -> API keys. The full key is shown exactly ONCE, so store it right away.

# Who am I? Returns the account id and the key's scopes.
curl https://api.husly.app/api/v1/me \
  -H "Authorization: Bearer hsly_live_ab12cd34ef56_..."

# List the sites on this account.
curl https://api.husly.app/api/v1/sites \
  -H "Authorization: Bearer hsly_live_ab12cd34ef56_..."

Authorization: Bearer hsly_live_ab12cd34ef56_XXXXXXXXXXXXXXXXXXXXXXXX

# or

X-Api-Key: hsly_live_ab12cd34ef56_XXXXXXXXXXXXXXXXXXXXXXXX

Never put a key in browser-side code or in a public repository - it reaches the whole account. Keep it in a server-side environment variable. A leaked key can be revoked immediately and replaced.

curl -X POST https://api.husly.app/api/v1/sites/SITE_ID/posts \
  -H "Authorization: Bearer hsly_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "slug": "kevadised-pakkumised",
    "title":   { "et": "Kevadised pakkumised", "en": "Spring offers" },
    "excerpt": { "et": "Lühike sissejuhatus.", "en": "A short intro." },
    "status": "published",
    "authorName": "Mari Maasikas",
    "layoutJson": {
      "contentWidth": "narrow",
      "blocks": [
        { "id": "b1", "type": "richtext", "props": {
            "content": { "et": "<p>Tere tulemast!</p>", "en": "<p>Welcome!</p>" } } }
      ]
    }
  }'

The current version is v1. We will not reshape a v1 response in a way that breaks your integration - new fields may appear, existing ones will not vanish. A breaking change would mean a new path (/api/v2/).

A partner key starts with hsly_partner_ and works only under /api/partner/v1/rentals. An account API key (hsly_live_) does not work here, and a partner key does not work in the account API.

# The site, its terms, and what this key may do.
curl https://api.husly.app/api/partner/v1/rentals/me \
  -H "Authorization: Bearer hsly_partner_ab12cd34ef56_..."

# What is free from 12 to 14 June, with the lowest price.
curl "https://api.husly.app/api/partner/v1/rentals/listings?from=2027-06-12&to=2027-06-14" \
  -H "Authorization: Bearer hsly_partner_ab12cd34ef56_..."

# Hold a car for 20 minutes...
curl -X POST https://api.husly.app/api/partner/v1/rentals/bookings \
  -H "Authorization: Bearer hsly_partner_ab12cd34ef56_..." \
  -H "Content-Type: application/json" \
  -d '{
    "listing": "toyota-rav4",
    "from": "2027-06-12",
    "to": "2027-06-14",
    "guest": { "name": "Mari Maasikas", "email": "[email protected]", "phone": "+372 5555 5555" },
    "termsAccepted": true,
    "hold": true,
    "reference": "AG-10442"
  }'

# ...and book it once the traveller says yes.
curl -X POST https://api.husly.app/api/partner/v1/rentals/bookings/BOOKING_ID/confirm \
  -H "Authorization: Bearer hsly_partner_ab12cd34ef56_..."

"hold": true keeps the dates for 20 minutes (at most 60) and writes to nobody. POST /bookings/:id/confirm books them; a hold that is not confirmed lets the dates go by itself. Sending the same "reference" again returns the same booking, not a second one. The price and the free days are the same as on the rental business's own site. A partner's booking is not paid on Husly: the partner settles the money with the renter.

{
  "mcpServers": {
    "husly-rentals": {
      "type": "http",
      "url": "https://api.husly.app/api/partner/v1/rentals/mcp",
      "headers": {
        "Authorization": "Bearer hsly_partner_ab12cd34ef56_..."
      }
    }
  }
}

Every field and every answer's shape is in the partner API's own reference and its OpenAPI 3.1 file, which you can load into Postman or generate a client from.

Ready to start?

The API is part of the Agency plan. If you already have an account, a key is a few clicks away.