repull 0.2.46 → 0.2.47
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/lib/repull/api/booking_com_api.rb +4 -4
- data/lib/repull/api/connect_api.rb +2 -2
- data/lib/repull/api/connections_api.rb +70 -0
- data/lib/repull/api/listings_api.rb +4 -4
- data/lib/repull/models/booking_property_action_request.rb +13 -3
- data/lib/repull/models/booking_property_action_response.rb +33 -19
- data/lib/repull/models/booking_property_open_result.rb +264 -0
- data/lib/repull/models/connect_session_abandoned_payload.rb +24 -2
- data/lib/repull/models/listing_active_response.rb +16 -4
- data/lib/repull/models/listing_status_batch_response.rb +16 -4
- data/lib/repull/models/map_connect_booking_rooms_response_property_status.rb +3 -3
- data/lib/repull/models/start_connection_import202_response.rb +147 -0
- data/lib/repull/models/start_connection_import202_response_data.rb +269 -0
- data/lib/repull/models/start_connection_import_request.rb +184 -0
- data/lib/repull/version.rb +1 -1
- data/lib/repull.rb +4 -0
- data/openapi/v1.json +193 -13
- metadata +6 -2
data/openapi/v1.json
CHANGED
|
@@ -4481,9 +4481,21 @@
|
|
|
4481
4481
|
"externalAccountId": {
|
|
4482
4482
|
"type": "string",
|
|
4483
4483
|
"nullable": true,
|
|
4484
|
-
"description": "Booking.com: the Hotel ID the user entered while waiting for the Extranet approval.",
|
|
4484
|
+
"description": "Booking.com: the Hotel ID the user entered while waiting for the Extranet approval. Booking.com Extranet in `awaiting_room_mapping`: the Booking.com account id of the connected login.",
|
|
4485
4485
|
"example": "17168363"
|
|
4486
4486
|
},
|
|
4487
|
+
"connectionId": {
|
|
4488
|
+
"type": "string",
|
|
4489
|
+
"nullable": true,
|
|
4490
|
+
"description": "Booking.com Extranet in `awaiting_room_mapping`: the connection record of the connected login (the `X-Account-Id`). Absent otherwise.",
|
|
4491
|
+
"example": "1701"
|
|
4492
|
+
},
|
|
4493
|
+
"fixUrl": {
|
|
4494
|
+
"type": "string",
|
|
4495
|
+
"format": "uri",
|
|
4496
|
+
"nullable": true,
|
|
4497
|
+
"description": "Booking.com Extranet in `awaiting_room_mapping`: a durable link that reopens Connect on the room-mapping step for this login. Send the host there to finish. `null` when there is nothing to resume."
|
|
4498
|
+
},
|
|
4487
4499
|
"nextStep": {
|
|
4488
4500
|
"type": "string",
|
|
4489
4501
|
"description": "What to tell the user, in plain English."
|
|
@@ -9675,6 +9687,53 @@
|
|
|
9675
9687
|
"active": {
|
|
9676
9688
|
"type": "boolean",
|
|
9677
9689
|
"description": "The resulting active state after the toggle."
|
|
9690
|
+
},
|
|
9691
|
+
"bookingProperties": {
|
|
9692
|
+
"type": "array",
|
|
9693
|
+
"description": "Only when activating: what happened to the Booking.com properties this listing is mapped to. Activating a listing opens its Booking.com property if Booking.com still has it in a build stage. Empty when the listing has no Booking.com property.",
|
|
9694
|
+
"items": {
|
|
9695
|
+
"$ref": "#/components/schemas/BookingPropertyOpenResult"
|
|
9696
|
+
}
|
|
9697
|
+
}
|
|
9698
|
+
}
|
|
9699
|
+
},
|
|
9700
|
+
"BookingPropertyOpenResult": {
|
|
9701
|
+
"type": "object",
|
|
9702
|
+
"required": [
|
|
9703
|
+
"hotelId",
|
|
9704
|
+
"listingIds",
|
|
9705
|
+
"outcome",
|
|
9706
|
+
"bookingStatus",
|
|
9707
|
+
"blockers"
|
|
9708
|
+
],
|
|
9709
|
+
"description": "What happened to one Booking.com property when its listing was activated. Repull opens a Booking.com property automatically only while every listing mapped to it is active. Keep a listing that is not ready inactive and its property is never opened; activate it and Repull opens the property, provided Booking.com's own readiness check passes.",
|
|
9710
|
+
"properties": {
|
|
9711
|
+
"hotelId": {
|
|
9712
|
+
"type": "string",
|
|
9713
|
+
"description": "The Booking.com property (hotel id)."
|
|
9714
|
+
},
|
|
9715
|
+
"listingIds": {
|
|
9716
|
+
"type": "array",
|
|
9717
|
+
"items": {
|
|
9718
|
+
"type": "string"
|
|
9719
|
+
},
|
|
9720
|
+
"description": "The listings in this request that are mapped to the property."
|
|
9721
|
+
},
|
|
9722
|
+
"outcome": {
|
|
9723
|
+
"type": "string",
|
|
9724
|
+
"description": "`opened`: Booking.com's check passed and the property is now open. `refused`: Booking.com's check did not pass \u2014 `blockers` has its own reasons \u2014 and nothing changed. `not_needed`: Booking.com already has the property past its build stage (open, or closed by you), so it was left alone; use the `open` action on `POST /v1/channels/booking/properties/{id}` to reopen a closed property. `listing_inactive`: another listing on the same property is still inactive. `no_listing`: no listing is mapped to the property. `failed`: Booking.com did not answer; nothing changed \u2014 send the request again."
|
|
9725
|
+
},
|
|
9726
|
+
"bookingStatus": {
|
|
9727
|
+
"type": "string",
|
|
9728
|
+
"nullable": true,
|
|
9729
|
+
"description": "Booking.com's status for the property before anything was sent, e.g. `XML: Ready to open`, when it was read."
|
|
9730
|
+
},
|
|
9731
|
+
"blockers": {
|
|
9732
|
+
"type": "array",
|
|
9733
|
+
"items": {
|
|
9734
|
+
"type": "string"
|
|
9735
|
+
},
|
|
9736
|
+
"description": "Booking.com's own reasons it will not open the property, e.g. \"Room 1554900501 does not have kitchen or kitchenette\". Empty unless `outcome` is `refused`."
|
|
9678
9737
|
}
|
|
9679
9738
|
}
|
|
9680
9739
|
},
|
|
@@ -9728,6 +9787,13 @@
|
|
|
9728
9787
|
"type": "string"
|
|
9729
9788
|
},
|
|
9730
9789
|
"description": "Listing ids that were already in the requested state, in request order."
|
|
9790
|
+
},
|
|
9791
|
+
"bookingProperties": {
|
|
9792
|
+
"type": "array",
|
|
9793
|
+
"description": "Only when `active` is true: one entry per Booking.com property the listings in the request are mapped to, saying whether it was opened. Every listing in the request counts, including those in `unchanged`, so sending `active: true` again retries an open Booking.com refused. Empty when none of the listings has a Booking.com property.",
|
|
9794
|
+
"items": {
|
|
9795
|
+
"$ref": "#/components/schemas/BookingPropertyOpenResult"
|
|
9796
|
+
}
|
|
9731
9797
|
}
|
|
9732
9798
|
}
|
|
9733
9799
|
},
|
|
@@ -16457,9 +16523,11 @@
|
|
|
16457
16523
|
"blocked",
|
|
16458
16524
|
"not_needed",
|
|
16459
16525
|
"status_unknown",
|
|
16460
|
-
"failed"
|
|
16526
|
+
"failed",
|
|
16527
|
+
"listing_inactive",
|
|
16528
|
+
"no_listing"
|
|
16461
16529
|
],
|
|
16462
|
-
"description": "`opened`: it was being built and is now open. `not_needed`: it was already past that stage. `blocked`: Booking.com will not open it yet \u2014 see `blockers`. `status_unknown`: its status could not be read. `failed`: Booking.com did not answer the open request."
|
|
16530
|
+
"description": "`opened`: it was being built and is now open. `not_needed`: it was already past that stage. `blocked`: Booking.com will not open it yet \u2014 see `blockers`. `status_unknown`: its status could not be read. `failed`: Booking.com did not answer the open request. `listing_inactive`: a listing mapped to the property is inactive, so it was not opened \u2014 activate it when it is ready and Repull opens the property. `no_listing`: no listing is mapped to it."
|
|
16463
16531
|
},
|
|
16464
16532
|
"statusBefore": {
|
|
16465
16533
|
"type": "string",
|
|
@@ -16994,11 +17062,15 @@
|
|
|
16994
17062
|
"required": [
|
|
16995
17063
|
"action"
|
|
16996
17064
|
],
|
|
16997
|
-
"description": "Take this listing's Booking.com property off sale
|
|
17065
|
+
"description": "Take this listing's Booking.com property off sale or put it back (`unlist` / `relist`), or open or close the property itself on Booking.com (`open` / `close`).",
|
|
16998
17066
|
"properties": {
|
|
16999
17067
|
"action": {
|
|
17000
17068
|
"type": "string",
|
|
17001
|
-
"description": "`unlist` closes the room's availability across the whole forward window, so the property stops selling. `relist` re-syncs the real calendar: dates that are genuinely blocked (a reservation, an owner stay) stay blocked, and only the closure `unlist` wrote lifts. They are not mirror images, and that is deliberate."
|
|
17069
|
+
"description": "`unlist` closes the room's availability across the whole forward window, so the property stops selling. `relist` re-syncs the real calendar: dates that are genuinely blocked (a reservation, an owner stay) stay blocked, and only the closure `unlist` wrote lifts. They are not mirror images, and that is deliberate.\n\n`open` runs Booking.com's readiness check and opens the property only if it passes \u2014 on a property that is not ready it changes nothing and answers `422 booking_rejected` with Booking.com's reasons in `blockers`. It opens a property Booking.com has in a build stage (`XML: Being built`, `XML: Ready to open`) or closed. `close` closes the property on Booking.com with `reason`."
|
|
17070
|
+
},
|
|
17071
|
+
"reason": {
|
|
17072
|
+
"type": "string",
|
|
17073
|
+
"description": "`close` only: the reason Booking.com records for closing the property. Default `PROPERTY_NOT_AVAILABLE`."
|
|
17002
17074
|
},
|
|
17003
17075
|
"hotelId": {
|
|
17004
17076
|
"type": "string",
|
|
@@ -17012,8 +17084,7 @@
|
|
|
17012
17084
|
"listingId",
|
|
17013
17085
|
"channel",
|
|
17014
17086
|
"action",
|
|
17015
|
-
"hotelId"
|
|
17016
|
-
"selling"
|
|
17087
|
+
"hotelId"
|
|
17017
17088
|
],
|
|
17018
17089
|
"properties": {
|
|
17019
17090
|
"listingId": {
|
|
@@ -17025,6 +17096,19 @@
|
|
|
17025
17096
|
"action": {
|
|
17026
17097
|
"type": "string"
|
|
17027
17098
|
},
|
|
17099
|
+
"propertyStatus": {
|
|
17100
|
+
"type": "string",
|
|
17101
|
+
"description": "`open` / `close` only: the property's state on Booking.com after the call."
|
|
17102
|
+
},
|
|
17103
|
+
"changed": {
|
|
17104
|
+
"type": "boolean",
|
|
17105
|
+
"description": "`open` / `close` only: false when the property was already in that state, so nothing was sent."
|
|
17106
|
+
},
|
|
17107
|
+
"bookingStatus": {
|
|
17108
|
+
"type": "string",
|
|
17109
|
+
"nullable": true,
|
|
17110
|
+
"description": "`open` / `close` only: Booking.com's status for the property before the call, e.g. `XML: Ready to open`."
|
|
17111
|
+
},
|
|
17028
17112
|
"hotelId": {
|
|
17029
17113
|
"type": "string",
|
|
17030
17114
|
"description": "The Booking.com property that was acted on. Always read it back \u2014 a listing can be mapped to several, and this states which one changed."
|
|
@@ -17036,7 +17120,7 @@
|
|
|
17036
17120
|
},
|
|
17037
17121
|
"selling": {
|
|
17038
17122
|
"type": "boolean",
|
|
17039
|
-
"description": "Whether the property is now on sale. **This is the state of the property on Booking.com, not of the listing in Repull** \u2014 `active` (what Repull bills and serves) is untouched by both actions and is deliberately not echoed here so the two can never be read as one field."
|
|
17123
|
+
"description": "`unlist` / `relist` only. Whether the property is now on sale. **This is the state of the property on Booking.com, not of the listing in Repull** \u2014 `active` (what Repull bills and serves) is untouched by both actions and is deliberately not echoed here so the two can never be read as one field."
|
|
17040
17124
|
}
|
|
17041
17125
|
}
|
|
17042
17126
|
},
|
|
@@ -20726,7 +20810,7 @@
|
|
|
20726
20810
|
"get": {
|
|
20727
20811
|
"operationId": "list_connections",
|
|
20728
20812
|
"summary": "List PMS/OTA connections",
|
|
20729
|
-
"description": "Returns every PMS and OTA connection in the workspace, each with its `status`.\n\n**Account ids.** `externalAccountId` is the platform's own account id (Airbnb host id, Booking.com hotel id, the Booking.com account id behind an Extranet login, the PMS account id; `null` when the platform does not give us one) and `id` is our connection record, the `X-Account-Id`.\n\n**Access level.** Every connection carries `accessType`: `read_only`, `messaging` or `full_access`, or `null` when unknown. Airbnb: the tier the host's token was granted with. Vrbo: bookings and messages only (`messaging`) or with the calendar push (`full_access`). Booking.com: always `full_access`. Booking.com Extranet: always `messaging` (reads reservations, messages and reviews and replies; never writes rates or availability). PMS: `read_only` when every write-policy switch is off, else `full_access`. See the `ConnectionAccessType` schema.\n\n**One entry per Booking.com Extranet login.** Each Booking.com account that invites the Repull user connects as its own login, with its own `externalAccountId` \u2014 the Booking.com account id (handle `booking_extranet:{externalAccountId}`). A new login adds an entry next to the existing ones and never replaces them
|
|
20813
|
+
"description": "Returns every PMS and OTA connection in the workspace, each with its `status`.\n\n**Account ids.** `externalAccountId` is the platform's own account id (Airbnb host id, Booking.com hotel id, the Booking.com account id behind an Extranet login, the PMS account id; `null` when the platform does not give us one) and `id` is our connection record, the `X-Account-Id`.\n\n**Access level.** Every connection carries `accessType`: `read_only`, `messaging` or `full_access`, or `null` when unknown. Airbnb: the tier the host's token was granted with. Vrbo: bookings and messages only (`messaging`) or with the calendar push (`full_access`). Booking.com: always `full_access`. Booking.com Extranet: always `messaging` (reads reservations, messages and reviews and replies; never writes rates or availability). PMS: `read_only` when every write-policy switch is off, else `full_access`. See the `ConnectionAccessType` schema.\n\n**One entry per Booking.com Extranet login.** Each Booking.com account that invites the Repull user connects as its own login, with its own `externalAccountId` \u2014 the Booking.com account id (handle `booking_extranet:{externalAccountId}`). A new login adds an entry next to the existing ones and never replaces them. Each login is its own connection with its own `id` (the `X-Account-Id`, and `account.id` in webhooks), and each login's listings, reservations, conversations and reviews stay under its own account (filter them with `?account=booking_extranet:{externalAccountId}`).\n\n**Spot connections that need attention.** A connection whose `status` is not `active` may need the host to do something before it works \u2014 most commonly a Booking.com Extranet connection where the invited user was granted only partial access (`status: \"needs_permissions\"`). A Smoobu connection still on a legacy single API key carries `action.reason: \"reauth_required\"` while its `status` is `active`: Smoobu stops accepting those keys on October 31, 2026, and `fixUrl` opens the form for a new API key + secret (the connection id stays the same). A Booking.com Extranet login whose rooms are imported but none matched to a listing carries `action.reason: \"needs_mapping\"` while its `status` is `active`: nothing syncs until the host maps the rooms, and `fixUrl` opens the room-mapping step. These connections carry two extra fields:\n\n- `action` \u2014 `{ required: true, reason, message }`. `reason` is a stable machine code (`needs_permissions`, `needs_mapping`, `reauth_required`); `message` is a host-facing one-liner describing what to do.\n- `fixUrl` \u2014 a durable link that reopens the hosted Connect flow **bound to that account, on the fix screen** (e.g. \"grant full access\" + a Re-check button). It is safe to store and show in your own dashboard.\n\n**Self-serve repair:** when `action.required` is true, surface a \"Fix\" button that opens `fixUrl` in a new tab (or embed it). The host resolves the issue (e.g. grants the user full access in Booking.com) and clicks Re-check; the import finishes on its own and the connection flips back to `active` \u2014 no re-invite, no support ticket. Poll this endpoint (or read it after the host returns) to confirm `action` has cleared.",
|
|
20730
20814
|
"tags": [
|
|
20731
20815
|
"Connect"
|
|
20732
20816
|
],
|
|
@@ -27850,7 +27934,7 @@
|
|
|
27850
27934
|
"patch": {
|
|
27851
27935
|
"operationId": "updateListingActive",
|
|
27852
27936
|
"summary": "Deactivate or reactivate a listing",
|
|
27853
|
-
"description": "Toggle a listing's active state. Send `{ \"active\": false }` to **deactivate** (exclude the listing from Repull) or `{ \"active\": true }` to **reactivate** it.\n\n\"Deactivate\" keeps the listing row \u2014 it is NOT a hard delete, and it NEVER touches the upstream channel (Airbnb / Hospitable / Booking.com). Repull only mutates its own copy of the inventory. Deactivating is the self-serve way to get back under the plan-listings cap without paying.\n\nReactivation respects the plan-listings cap: if activating this listing would push you over the cap for your tier, the call returns `402 listings_limit_exceeded` and the listing stays inactive. Deactivate another listing or upgrade first.\n\nIdempotent: setting a listing to the state it's already in returns 200.\n\nTo change many listings at once, all or nothing, use `POST /v1/listings/status`.",
|
|
27937
|
+
"description": "Toggle a listing's active state. Send `{ \"active\": false }` to **deactivate** (exclude the listing from Repull) or `{ \"active\": true }` to **reactivate** it.\n\n\"Deactivate\" keeps the listing row \u2014 it is NOT a hard delete, and it NEVER touches the upstream channel (Airbnb / Hospitable / Booking.com). Repull only mutates its own copy of the inventory. Activating opens the listing's Booking.com property if Booking.com still has it in a build stage and its check passes; `bookingProperties` in the response says what happened. Deactivating is the self-serve way to get back under the plan-listings cap without paying.\n\nReactivation respects the plan-listings cap: if activating this listing would push you over the cap for your tier, the call returns `402 listings_limit_exceeded` and the listing stays inactive. Deactivate another listing or upgrade first.\n\nIdempotent: setting a listing to the state it's already in returns 200.\n\nTo change many listings at once, all or nothing, use `POST /v1/listings/status`.",
|
|
27854
27938
|
"tags": [
|
|
27855
27939
|
"Listings"
|
|
27856
27940
|
],
|
|
@@ -29369,8 +29453,8 @@
|
|
|
29369
29453
|
},
|
|
29370
29454
|
"post": {
|
|
29371
29455
|
"operationId": "booking_property_action",
|
|
29372
|
-
"summary": "Take a property off sale / put it back (unlist/relist)",
|
|
29373
|
-
"description": "Stop this listing's Booking.com property being sold, or start it again. `id` is a **Repull listing id**, not a Booking.com hotel id, as on the GET.\n\n**Booking.com has no unlist, so this is an availability write.** Airbnb has a real deactivate; Booking.com does not. `unlist` closes the mapped room across the whole forward window, so the property stops selling. `relist` is not its mirror image: it re-syncs the true calendar, so dates that are genuinely blocked (a reservation, an owner stay) stay blocked and only the closure `unlist` wrote lifts. Re-opening everything would sell dates that are not for sale.\n\n**Which property gets closed.** A listing can be mapped to more than one Booking.com property \u2014 the same unit re-listed under a new property keeps its old mapping, and workspaces routinely sit on five or six. With exactly one, send nothing. With several, name one with `hotelId` (or `?hotel_id=`); omit it and the request is refused with **`409 ambiguous_booking_mapping`** listing the candidates, and nothing is written. That refusal matters more here than on a publish: writing content into the wrong property is recoverable, closing the wrong property's availability takes real inventory off sale while the property you meant keeps selling. Naming a property this listing is not mapped to is a `404` that names the ones it is.\n\n**This does not change the listing in Repull.** `active` \u2014 what Repull bills and serves \u2014 is untouched by both actions and is deliberately not echoed in the response, so the two ideas can never be read as one field. To take a listing off the market on every channel at once, use `POST /v1/listings/{id}/offline`.\n\nAny other action returns a structured `422` naming the ones that are supported. To push content use `POST /v1/listings/{id}/publish/booking`; to map rooms use `POST /v1/connect/booking/map-rooms`.\n\nReturns `403 listing_inactive` when the listing is inactive. An inactive listing keeps syncing, but cannot be read or changed through the API until it is activated.",
|
|
29456
|
+
"summary": "Take a property off sale / put it back, or open / close it (unlist/relist/open/close)",
|
|
29457
|
+
"description": "Stop this listing's Booking.com property being sold, or start it again. `id` is a **Repull listing id**, not a Booking.com hotel id, as on the GET.\n\n**Booking.com has no unlist, so this is an availability write.** Airbnb has a real deactivate; Booking.com does not. `unlist` closes the mapped room across the whole forward window, so the property stops selling. `relist` is not its mirror image: it re-syncs the true calendar, so dates that are genuinely blocked (a reservation, an owner stay) stay blocked and only the closure `unlist` wrote lifts. Re-opening everything would sell dates that are not for sale.\n\n**Which property gets closed.** A listing can be mapped to more than one Booking.com property \u2014 the same unit re-listed under a new property keeps its old mapping, and workspaces routinely sit on five or six. With exactly one, send nothing. With several, name one with `hotelId` (or `?hotel_id=`); omit it and the request is refused with **`409 ambiguous_booking_mapping`** listing the candidates, and nothing is written. That refusal matters more here than on a publish: writing content into the wrong property is recoverable, closing the wrong property's availability takes real inventory off sale while the property you meant keeps selling. Naming a property this listing is not mapped to is a `404` that names the ones it is.\n\n**This does not change the listing in Repull.** `active` \u2014 what Repull bills and serves \u2014 is untouched by both actions and is deliberately not echoed in the response, so the two ideas can never be read as one field. To take a listing off the market on every channel at once, use `POST /v1/listings/{id}/offline`.\n\n**Opening and closing the property on Booking.com.** `open` runs Booking.com's readiness check and, only if it passes, opens the property. On a property that is not ready it changes nothing and answers **`422 booking_rejected`** with Booking.com's own reasons in `blockers` (for example \"Room 1554900501 does not have kitchen or kitchenette\"), so it is safe to ask. It opens a property Booking.com has in a build stage (`XML: Being built`, `XML: Ready to open`) or closed; an open property answers `changed: false`. `close` closes the property on Booking.com, with an optional `reason` (default `PROPERTY_NOT_AVAILABLE`). An inactive listing cannot be opened (`403 listing_inactive`), and neither can a property another inactive listing shares.\n\n**When Repull opens a property by itself.** Repull opens a Booking.com property automatically only while every listing mapped to it is active. Keep a listing that is not ready inactive and its property is never opened; activate it and Repull opens the property, provided Booking.com's own readiness check passes. Activate with `POST /v1/listings/status` (or `PATCH /v1/listings/{id}`); its response has a `bookingProperties` entry per property saying whether it opened. Deactivating never closes a property that is already open \u2014 use `close` for that.\n\nAny other action returns a structured `422` naming the ones that are supported. To push content use `POST /v1/listings/{id}/publish/booking`; to map rooms use `POST /v1/connect/booking/map-rooms`.\n\nReturns `403 listing_inactive` when the listing is inactive. An inactive listing keeps syncing, but cannot be read or changed through the API until it is activated.",
|
|
29374
29458
|
"tags": [
|
|
29375
29459
|
"Booking.com"
|
|
29376
29460
|
],
|
|
@@ -31855,7 +31939,7 @@
|
|
|
31855
31939
|
"post": {
|
|
31856
31940
|
"operationId": "setListingsStatus",
|
|
31857
31941
|
"summary": "Activate or deactivate listings in bulk",
|
|
31858
|
-
"description": "Sets up to 500 listings active or inactive in one call. Send `{ \"listingIds\": [\"4118\", \"4119\"], \"active\": false }` to deactivate them, or `\"active\": true` to activate them.\n\nAn inactive listing is not counted toward your plan's listing limit or billed. It is NOT deleted and the upstream channel (Airbnb / Booking.com / your PMS)
|
|
31942
|
+
"description": "Sets up to 500 listings active or inactive in one call. Send `{ \"listingIds\": [\"4118\", \"4119\"], \"active\": false }` to deactivate them, or `\"active\": true` to activate them.\n\nAn inactive listing is not counted toward your plan's listing limit or billed. It is NOT deleted and nothing is pushed to the upstream channel (Airbnb / Booking.com / your PMS) \u2014 its data keeps syncing, so it is complete the moment you activate it again. Until then it cannot be read, changed, or receive webhooks.\n\n**Activating opens the listing's Booking.com property.** Repull opens a Booking.com property automatically only while every listing mapped to it is active. Keep a listing that is not ready inactive and its property is never opened; activate it and Repull opens the property, provided Booking.com's own readiness check passes. `bookingProperties` in the response says, per property, whether it was opened or what Booking.com said is missing. Sending `active: true` again for a listing that is already active retries the open. Deactivating never closes a property that is already open \u2014 use the `close` action on `POST /v1/channels/booking/properties/{id}`.\n\n**All or nothing.** Nothing changes unless the whole request can be applied:\n- If any id is not one of your listings, the call returns `404` naming those ids.\n- If activating would take you over your plan's listing limit, the call returns `402 listings_limit_exceeded`. Only listings that are currently inactive count toward the new total, so re-sending ids that are already active never trips the limit.\n\nDeactivating is always allowed, including when your account is already over its limit \u2014 it is how you get back under it.\n\n**Idempotent.** Ids already in the requested state are returned in `unchanged`; ids this call changed are returned in `updated`.\n\nFor a single listing, `PATCH /v1/listings/{id}` does the same.",
|
|
31859
31943
|
"tags": [
|
|
31860
31944
|
"Listings"
|
|
31861
31945
|
],
|
|
@@ -41431,6 +41515,102 @@
|
|
|
41431
41515
|
"$ref": "#/components/responses/Unauthorized"
|
|
41432
41516
|
}
|
|
41433
41517
|
}
|
|
41518
|
+
},
|
|
41519
|
+
"post": {
|
|
41520
|
+
"operationId": "startConnectionImport",
|
|
41521
|
+
"summary": "Refresh a connection's listings",
|
|
41522
|
+
"description": "Refresh listings: picks up listings you've added on Airbnb since you connected. Re-reads the connected account's listings and their calendars (pricing and availability) now; a new property comes in as a new listing and existing listings are refreshed. Nothing else is re-imported: no reservations, conversations, reviews or payouts.\n\nThe same import runs on its own once a day for every connected Airbnb account, and when the host reconnects. Call this when you know a property was just added and do not want to wait.\n\nNew listings obey your plan's active-listing limit: past it, and when the property is unlisted on Airbnb, they arrive inactive. Existing listings keep their status.\n\nThe import runs in the background (`202`). It is recorded like any other import (trigger `resync`, one `listings` stage): follow it on `GET /v1/connections/{id}/imports` or wait for `account.import.completed`, then read the new listings with `GET /v1/listings`.\n\nAirbnb connections only for now. Returns `409 conflict` while a listings import of the account is already running, and `409 connection_reauth_required` when the account is disconnected.",
|
|
41523
|
+
"tags": [
|
|
41524
|
+
"Connections"
|
|
41525
|
+
],
|
|
41526
|
+
"parameters": [
|
|
41527
|
+
{
|
|
41528
|
+
"name": "id",
|
|
41529
|
+
"in": "path",
|
|
41530
|
+
"required": true,
|
|
41531
|
+
"schema": {
|
|
41532
|
+
"type": "string"
|
|
41533
|
+
},
|
|
41534
|
+
"description": "Airbnb connection handle `airbnb:{hostId}` \u2014 the `provider` and `externalAccountId` of an Airbnb connection on `GET /v1/connect`, or the account of an `account.*` webhook."
|
|
41535
|
+
}
|
|
41536
|
+
],
|
|
41537
|
+
"requestBody": {
|
|
41538
|
+
"required": false,
|
|
41539
|
+
"content": {
|
|
41540
|
+
"application/json": {
|
|
41541
|
+
"schema": {
|
|
41542
|
+
"type": "object",
|
|
41543
|
+
"properties": {
|
|
41544
|
+
"scope": {
|
|
41545
|
+
"type": "string",
|
|
41546
|
+
"enum": [
|
|
41547
|
+
"listings"
|
|
41548
|
+
],
|
|
41549
|
+
"default": "listings",
|
|
41550
|
+
"description": "What to import. `listings` = the account's listings and their calendars (pricing and availability). The only scope; the full import runs when an account is connected."
|
|
41551
|
+
}
|
|
41552
|
+
}
|
|
41553
|
+
}
|
|
41554
|
+
}
|
|
41555
|
+
}
|
|
41556
|
+
},
|
|
41557
|
+
"responses": {
|
|
41558
|
+
"202": {
|
|
41559
|
+
"description": "The import is queued.",
|
|
41560
|
+
"content": {
|
|
41561
|
+
"application/json": {
|
|
41562
|
+
"schema": {
|
|
41563
|
+
"type": "object",
|
|
41564
|
+
"properties": {
|
|
41565
|
+
"data": {
|
|
41566
|
+
"type": "object",
|
|
41567
|
+
"properties": {
|
|
41568
|
+
"connection": {
|
|
41569
|
+
"type": "string",
|
|
41570
|
+
"description": "The connection handle, e.g. `airbnb:1234567`."
|
|
41571
|
+
},
|
|
41572
|
+
"scope": {
|
|
41573
|
+
"type": "string",
|
|
41574
|
+
"enum": [
|
|
41575
|
+
"listings"
|
|
41576
|
+
]
|
|
41577
|
+
},
|
|
41578
|
+
"status": {
|
|
41579
|
+
"type": "string",
|
|
41580
|
+
"enum": [
|
|
41581
|
+
"queued"
|
|
41582
|
+
]
|
|
41583
|
+
},
|
|
41584
|
+
"queuedAt": {
|
|
41585
|
+
"type": "string",
|
|
41586
|
+
"format": "date-time"
|
|
41587
|
+
}
|
|
41588
|
+
},
|
|
41589
|
+
"required": [
|
|
41590
|
+
"connection",
|
|
41591
|
+
"scope",
|
|
41592
|
+
"status",
|
|
41593
|
+
"queuedAt"
|
|
41594
|
+
]
|
|
41595
|
+
}
|
|
41596
|
+
}
|
|
41597
|
+
}
|
|
41598
|
+
}
|
|
41599
|
+
}
|
|
41600
|
+
},
|
|
41601
|
+
"400": {
|
|
41602
|
+
"$ref": "#/components/responses/BadRequest"
|
|
41603
|
+
},
|
|
41604
|
+
"401": {
|
|
41605
|
+
"$ref": "#/components/responses/Unauthorized"
|
|
41606
|
+
},
|
|
41607
|
+
"404": {
|
|
41608
|
+
"$ref": "#/components/responses/NotFound"
|
|
41609
|
+
},
|
|
41610
|
+
"409": {
|
|
41611
|
+
"$ref": "#/components/responses/Conflict"
|
|
41612
|
+
}
|
|
41613
|
+
}
|
|
41434
41614
|
}
|
|
41435
41615
|
},
|
|
41436
41616
|
"/v1/listings/promotions/bulk": {
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: repull
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.2.
|
|
4
|
+
version: 0.2.47
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Ivan Nikolov
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2026-11-
|
|
11
|
+
date: 2026-11-13 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: typhoeus
|
|
@@ -219,6 +219,7 @@ files:
|
|
|
219
219
|
- lib/repull/models/booking_property_action_request.rb
|
|
220
220
|
- lib/repull/models/booking_property_action_response.rb
|
|
221
221
|
- lib/repull/models/booking_property_listings_inner.rb
|
|
222
|
+
- lib/repull/models/booking_property_open_result.rb
|
|
222
223
|
- lib/repull/models/booking_publish_result.rb
|
|
223
224
|
- lib/repull/models/booking_publish_section_error.rb
|
|
224
225
|
- lib/repull/models/booking_rate_write_occupancy.rb
|
|
@@ -781,6 +782,9 @@ files:
|
|
|
781
782
|
- lib/repull/models/set_listing_markup_request.rb
|
|
782
783
|
- lib/repull/models/start_booking_extranet_login200_response.rb
|
|
783
784
|
- lib/repull/models/start_booking_extranet_login_request.rb
|
|
785
|
+
- lib/repull/models/start_connection_import202_response.rb
|
|
786
|
+
- lib/repull/models/start_connection_import202_response_data.rb
|
|
787
|
+
- lib/repull/models/start_connection_import_request.rb
|
|
784
788
|
- lib/repull/models/submit_beds24_credentials200_response.rb
|
|
785
789
|
- lib/repull/models/submit_beds24_credentials_request.rb
|
|
786
790
|
- lib/repull/models/submit_bookingsync_credentials_request.rb
|