API Documentation

Returns your profile.

Partial update. Accepted fields: firstName, lastName, phone, userType (INDIVIDUAL | COMPANY), companyName, companyTaxId, instagram, facebook, telegram, hasWhatsapp, hasViber, agentLicense.

Changing phone (international format, e.g. +38267123456) resets its verified status unless your account is linked to an OAuth provider; verify the new number in the dashboard. A number already verified by another account answers 409.

curl -X PATCH https://stanovina.me/api/v1/me \
  -H "Authorization: Bearer stv_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"firstName": "Ana", "hasWhatsapp": true}'

Your listings, newest first. Query: ?status= (any listing status), ?page=, ?limit= (max 100).

Create a listing (as DRAFT). Required fields — the same set the website form requires:

• title, description — primary language (Montenegrin); titleEn/titleRu/descriptionEn/descriptionRu optional
• propertyType, listingType — see enums
• countryId — from /api/v1/reference/countries
• price, area — positive numbers
• priceOnRequest — optional boolean. Set it to true for a listing whose asking price is not public yet: price becomes unnecessary and is stored as 0. Such listings show “Cijena na upit” instead of a price, are skipped by the priceFrom/priceTo filters, sort last under priceAsc/priceDesc, and are left out of the price statistics. A PATCH setting it back to false must send a real price in the same request.

Optional: cityId, districtId (must belong to the city), currency, rooms, bedrooms, bathrooms, floor, totalFloors, yearBuilt, landArea, furnishing, latitude/longitude, address, distanceToSea, rental fields (deposit, utilitiesIncluded, utilitiesPrice, availableFrom, petsAllowed, annualRent) and amenity flags (hasParking, hasPool, hasBalcony, …). A listing without cityId won't appear on city/municipality pages — set it whenever you can.

Shortcuts: "imageUrls": [...] attaches photos from URLs in the same call (first URL becomes the main photo); "publish": true submits immediately after creation. If the publish step fails (no photos, unverified phone), the response still contains the created draft plus a publishError.

curl -X POST https://stanovina.me/api/v1/listings \
  -H "Authorization: Bearer stv_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Dvosoban stan, Budva",
    "description": "Stan od 55 m2 na 200 m od mora...",
    "propertyType": "APARTMENT",
    "listingType": "SALE",
    "countryId": "COUNTRY_ID",
    "cityId": "CITY_ID",
    "price": 120000,
    "area": 55,
    "rooms": 2,
    "hasBalcony": true,
    "imageUrls": ["https://example.com/photo1.jpg"],
    "publish": true
  }'

One of your listings, photos and location included.

Partial edit — send only what changes. Required fields cannot be blanked. Drafts stay drafts; see lifecycle for how edits affect live and in-review listings.

Submit a DRAFT, or resubmit a REJECTED listing. Validates ≥1 photo and a verified phone. Response: {"status": "ACTIVE"} or {"status": "PENDING_MODERATION"}.

Owner transitions: body {"status": "SOLD"}. Allowed: ACTIVE→SOLD, ACTIVE→RENTED, SOLD|RENTED→ACTIVE, REJECTED→PENDING_MODERATION.

Deletes a DRAFT and its photos. Non-drafts cannot be deleted.

Photos in display order. Each carries isMain (true at order 0).

Attach photos, appended after the existing ones. Two request shapes:

Multipart upload

curl -X POST https://stanovina.me/api/v1/listings/LISTING_ID/images \
  -H "Authorization: Bearer stv_YOUR_KEY" \
  -F "[email protected]" \
  -F "[email protected]"

By URL (server-side fetch)

curl -X POST https://stanovina.me/api/v1/listings/LISTING_ID/images \
  -H "Authorization: Bearer stv_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls": ["https://example.com/a.jpg", "https://example.com/b.jpg"]}'

URLs must be https:// and publicly reachable (private and internal addresses are refused). Per-URL failures don't fail the batch — they are returned in skipped with a reason.

Reorder. Either {"mainImageId": "IMAGE_ID"} — moves that photo to the front — or {"order": ["id1", "id2", ...]} listing every photo id exactly once.

Removes one photo; remaining photos close ranks (orders re-packed from 0), so deleting the main photo promotes the next one.