323
edits
Changes
Jump to navigation
Jump to search
'''Step 1: Get an invite code'''== Invite codes and refresh tokens ==
A room can have up = Best Practices === Token Management ==Tokens last 24 hours. This means that you do not need to 16 pricesretrieve a new token for each request. Getting a new token costs credits so it is best to use an existing one when possible.
In the control panel== Retrieving information at high frequencies ==If you need to get data such as new messages or bookings when they come in you do not need to perform frequent GET requests. Instead, these you can use webhooks to be set under Prices -> Daily Price Setupnotified as soon as a new message/booking etc arrives.
In == Sending information at high frequencies ==If you need to send large amounts of information such as messages at high frequencies it is best to send them grouped in bulk POST requests instead of sending one request per message. For example, you could send one POST request every 30 seconds containing all messages sent in the API these can be accessed through GET and POST /inventory/calendarpast 30 seconds. { "data": [== Sending or getting information in one call == { "calendar": [ { "price1": 100If you need to retrieve information about multiple different things, such as information about several properties, "price2": 300you can retrieve that in one call by specifying multiple IDs in the one request instead of performing one GET request per property. The same principle applies when POSTing information, "price3": 200for example, ..you can create or update multiple properties in one call. } ] } ] }
In addition, there is ==Where can I see the possible values for a limit of 100 top level JSON array item per POST requestbooking's apiSourceId (API Source ID)== [[/API_V2.0_apisourceids | apiSourceId values can be found here.]]
= Authentication =
There are two kinds of tokens, long life tokens which have read only access, and refresh tokens which generate tokens that can read and make changes.
To use most API endpoints you will need to include a token header.
'''Step 1: Get an invite code or long life token''' Invite codes and long life tokens can be generated here [https://beds24.com/control3.php?pagetype=apiv2 Invite Codes]
For more information about invite codes, [[API_V2.0#Invite_codes|see here]].
This step is the only one that must be done manually, all other steps can be performed and automated programmatically.
'''Step 2: Get If using an invite code, get a refresh token using the invite code''' Skip this step if using a long life token
You can use the invite code generated in step one with GET /authentication/setup.
This will return a ''token'' and a ''refresh token''.
<span style="color:#019cde; font-size: 150%;“ >{{#fas:info-circle}} </span> ''Tokens'' generated from refresh tokens expire after 24 hours.
'''Step 3: Use the token to authenticate calls'''
The ''token'' returned in step 2 (either a long life token or a token generated using a refresh token) can be included as a header to authenticate calls to other API endpoints. <span style="color:#019cde; font-size: 150%;“ >{{#fas:info-circle}} </span> ''Tokens'' expire after 24 hours.
'''Step 4: Use the refresh token to generate new tokens'''
]
= Prices Endpoints = == Bookings == === GET /bookings === Get bookings matching specified criteria. === POST /bookings === Create or update bookings. === DELETE /bookings === Delete bookings by id. === GET /bookings/messages === Get messages for a booking. === POST /bookings/messages === Send messages or mark them as read. === PATCH /bookings/messages === Make changes in all messages in a selection. === GET /bookings/invoices === Get invoices for bookings. == Inventory == === GET /inventory/rooms/offers === Get offer based on specified criteria. === GET /inventory/rooms/availability === Get the availability status of dates. === GET /inventory/rooms/calendar === Get's per day values from the calendar. === POST /inventory/rooms/calendar === Modify per day calendar values. == Properties == === GET /properties === Get properties matching specified criteria. === POST /properties === Create or modify properties. === DELETE /properties === Delete properties by id. === DELETE /properties/rooms === Delete rooms of properties by id. == Accounts == === GET /accounts === Get accounts and sub-accounts. === POST /accounts === Create or modify accounts. == Webhooks == === POST Webhooks - bookings === The webhook payload sent to your URL from the booking webhook found here: Settings -> Properties -> Access -> Booking Webhook == Channels - settings == === GET /channels/settings === Get channel specific settings. === POST /channels/settings === Modify channel settings. == Channels - Airbnb == === GET /channels/airbnb/users === Get all Airbnb user ids connected to an account. === GET /channels/airbnb/listings === Get all Airbnb listings for a specified Airbnb user id. === POST /channels/airbnb === Perform actions at Airbnb. == Channels - Booking.com == === POST /channels/booking === Perform actions at Booking.com. === GET /channels/booking/reviews === Get reviews from Booking.com. == Channels - Stripe == You can collect the card directly with Stripe so you do not have any PCI DSS obligations. The procedure would be like this: 1) Make the booking via API and get the new Booking ID. 2) Make a call to API V2 POST /channels/stripe with the booking ID and any charges you want to collect. The line_items should be in the Stripe format for their checkout. https://docs.stripe.com/payments/checkout 3) POST /channels/stripe will return the session data required to instantly create a Stripe payment checkout you can show the booker and they can securely enter their card while on your site. https://docs.stripe.com/api/checkout/sessions 4) After the booker enters their card, it is automatically connected to the booking ID and can be charged by API or manually from the control panel. To use the Stripe endpoints, the process is basically the same as creating a normal Strip Checkout session, except by doing it via our API function it connects the payment to the booking. Use our API to create the Stripe session and then follow Stripes instructions and use the Stripe API or widgets to create a payment checkout for your page. The Stripe checkout session will create a Stripe checkout page for receiving payments into the properties Stripe account. Pass the line_items, success_url and cancel_url in the format required by the Stripe API to create a checkout session. The line_items format is defined in the Stripe documentation If the booking already exists, pass it's booking ID as "bookId" and any payments to this checkout session will be added to the bookings invoice. Setting "capture":false will authorize the amount but not collect the funds. The Stripe session will be returned, the session id can be used to create the Stripe checkout in your App. When initializing Stripe in your App, use this pk_live key and the stripe_account value (acct_) from the session response as follows: <code>var stripe = Stripe('pk_live_zWSW2ykzZoq4mYcKg9c8jmHS', {stripeAccount: 'acct_stripe_acccont-value-from-response'});</code> See here for more information https://stripe.com/docs/payments/checkout === POST /channels/stripe === Perform actions at Stripe. === GET /channels/stripe/paymentMethods === Get payment methods for a booking from Stripe. === GET /channels/stripe/charges === Get charges for a booking from Stripe.
= Webhooks === Booking webhooks ==To get price setup rules, include the "includePriceRules" parameter in GET access booking webhooks for API V2 please contact support. They can then be enabled under Settings > Properties > Access > Booking webhooks.== Other webhooks ==Information about other webhooks (including non API V2 webhooks) can be found here [https:/properties like this /apiwiki.beds24.com/v2index.php/properties?includePriceRules=trueCategory:Webhooks Webhooks]
= Examples =
==How long do invite codes/tokens last?==
Invite codes expire after 15 minutes24 hours.
Refresh tokens last forever so long as they are being used. Unused refresh tokens expire after 30 days.
Long life tokens last forever so long as they are being used. Unused long life tokens expire after 90 days. Tokens generated from refresh tokens expire after 24 hours.
==How big are tokens?==
==What is the maximum amount of data I can send in a POST request?==
The API has a limit of approximately 1MB per post POST payload. In addition, there is a limit of 10000 top level JSON array item per POST request.
