Correct documentation errors found in implementation review

Fix discrepancies against the current implementation: recurring
rdate/exdate format, booking listing filters and start/end semantics,
service types and sellable listings, attribute types and required
flags, missing serialized attributes, public slots response shape,
CORS prerequisite, verification code status, six digit SMS token and
outdated locale lists. Switch private API examples to Bearer auth.

Also split the pagination guide into Pagination and a new Example
Requests guide.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ARj1YRv8rDzdq8SHKpMHrT

Author: espen

_endpoints/account.md

@@ -18,31 +18,31 @@ Information and settings for your account.
   <tr><td>google_analytics</td><td>String</td><td></td></tr>
   <tr><td>css_url</td><td>String</td><td></td></tr>
   <tr><td>time_zone</td><td>String</td><td>Required</td></tr>
-  <tr><td>verification_method</td><td>Integer</td><td></td></tr>
+  <tr><td>verification_method</td><td>String</td><td>Values: no_verification, email, sms, authenticated, id_porten, vipps.</td></tr>
   <tr><td>address</td><td>String</td><td></td></tr>
   <tr><td>country_code</td><td>String</td><td>Required. ISO 3166-1 alpha-2.</td></tr>
   <tr><td>logo</td><td>File</td><td></td></tr>
-  <tr><td>template</td><td>Integer</td><td>Required</td></tr>
+  <tr><td>template</td><td>String</td><td>Values: amsterdam, lviv, timisoara.</td></tr>
   <tr><td>service_template</td><td>String</td><td></td></tr>
-  <tr><td>locale</td><td>String</td><td>Required. Supported locales: 'en', 'sv' and 'nb'. Default: 'en'.</td></tr>
-  <tr><td>currency</td><td>String</td><td>ISO4217 currency code</td></tr>
+  <tr><td>locale</td><td>String</td><td>Required. Supported locales: cs, da, de, en, en-GB, en-US, es, fr, he, it, lt, lv, ms, nb, nl, pl, ru, sl, sq, sv. Default: 'en'.</td></tr>
+  <tr><td>currency</td><td>String</td><td>Required. ISO4217 currency code</td></tr>
   <tr><td>email_notification</td><td>Boolean</td><td></td></tr>
   <tr><td>mail_notification_recipient</td><td>Email</td><td></td></tr>
   <tr><td>sms_notification</td><td>Boolean</td><td></td></tr>
   <tr><td>phone_number</td><td>String</td><td></td></tr>
   <tr><td>confirm_manually</td><td>Boolean</td><td></td></tr>
-  <tr><td>settings</td><td>Array</td><td></td></tr>
+  <tr><td>settings</td><td>Object</td><td>Key/value. Stored as strings.</td></tr>
   <tr><td>public_access</td><td>Boolean</td><td></td></tr>
   <tr><td>interval_rounding</td><td>Integer</td><td>Default setting for all services for rounding to next available time. '15' will round 10:07 to become 10:15 as next available slot time.</td></tr>
   <tr><td>slot_generation</td><td>String</td><td>Default: dynamic. Values: dynamic (next available), fixed.</td></tr>
   <tr><td>future_bookable_period</td><td>String</td><td>Natural language date/time relative to current time.</td></tr>
   <tr><td>first_bookable_period</td><td>String</td><td>Natural language date/time relative to current time.</td></tr>
   <tr><td>payment_provider</td><td>String</td><td></td></tr>
   <tr><td>footer</td><td>Text</td><td></td></tr>
-  <tr><td>verification_methods</td><td>String</td><td></td></tr>
+  <tr><td>verification_methods</td><td>Array</td><td>Array of strings, see verification_method for values.</td></tr>
   <tr><td>reminder_sms</td><td>Boolean</td><td></td></tr>
   <tr><td>closed_for_holidays</td><td>Boolean</td><td></td></tr>
-  <tr><td>new_user_text</td><td>Liquid-Text</td><td>Above booking form.</td></tr>
+  <tr><td>reservation_form_text</td><td>Liquid-Text</td><td>Above booking form.</td></tr>
   <tr><td>new_booking_text</td><td>Liquid-Text</td><td>Booking confirmation page.</td></tr>
   <tr><td>booking_form</td><td>Liquid-Text</td><td>Custom booking form.</td></tr>
   <tr><td>person_form</td><td>Liquid-Text</td><td>For custom data in administration system.</td></tr>
@@ -114,8 +114,8 @@ Response
 
 <table>
   <tr><th>Name</th><th>Type</th><th>Description</th></tr>
-  <tr><td>from</td><td>Date</td><td></td></tr>
-  <tr><td>to</td><td>Date</td><td></td></tr>
+  <tr><td>from</td><td>Date</td><td>Default: beginning of the current week.</td></tr>
+  <tr><td>to</td><td>Date</td><td>Default: end of the week of from.</td></tr>
 </table>
 
 ## Users

_endpoints/bookings.md

@@ -25,10 +25,10 @@ description: API reference for the Makeplans bookings endpoint — attributes, s
   <tr><td>paid_at</td><td>Datetime</td><td>Only for output</td></tr>
   <tr><td>external_id</td><td>String</td><td>Not required</td></tr>
   <tr><td>paid_amount</td><td>Decimal</td><td>Only for output</td></tr>
-  <tr><td>invoiced_at</td><td>Datetime</td><td>Only for output</td></tr>
+  <tr><td>invoiced_at</td><td>Date</td><td>Only for output</td></tr>
   <tr><td>revision_count</td><td>Integer</td><td>Automatically set</td></tr>
-  <tr><td>created_by</td><td>String</td><td>Automatically set</td></tr>
-  <tr><td>updated_by</td><td>String</td><td>Automatically set</td></tr>
+  <tr><td>created_by</td><td>Integer</td><td>Automatically set. User id.</td></tr>
+  <tr><td>updated_by</td><td>Integer</td><td>Automatically set. User id.</td></tr>
   <tr><td>external_url</td><td>String</td><td>Not required</td></tr>
   <tr><td>external_host_url</td><td>String</td><td>Not required</td></tr>
   <tr><td>booked_by_person_id</td><td>Integer</td><td>Only for output. Person who made the booking (e.g. parent booking for child).</td></tr>
@@ -81,7 +81,7 @@ Bookings on a waitlist are set to `waitlisted`. A waitlisted booking is not acti
 
 ## Active bookings
 
-Bookings with states `awaiting_verification`, `awaiting_payment`, `awaiting_confirmation` or `confirmed` are considered to be active. Bookings with state `awaiting_verification` will be updated with state `verification_expired` after the current time passes `expires_at`. However updating states rely on automatic tasks so you must use the `active` attribute to check whether a booking is active or not. Only active bookings will be returned unless you specify: a booking by id, a specific state such as bookings that are awaiting confirmation, to return all bookings for a resource or dates, or for a person.
+Bookings with states `awaiting_verification`, `awaiting_payment`, `awaiting_confirmation` or `confirmed` are considered to be active. Bookings with state `awaiting_verification` will be updated with state `verification_expired` after the current time passes `expires_at`. However updating states rely on automatic tasks so you must use the `active` attribute to check whether a booking is active or not. Only active bookings will be returned unless you request a booking by id, specify a specific state such as bookings that are awaiting confirmation, or use the `all` or `visible` listings.
 
 ## Listing
 
@@ -97,11 +97,11 @@ See query parameters for filtering the output beyond the default outputs.
 
 `GET /bookings/all` will return all bookings of all states (including `declined`, `cancelled`, `deleted`, and `verification_expired`). This is a useful output for synchronisation when you need to keep a track of deleted bookings.
 
-`GET /bookings/visible` will return all active bookings as well as those declined or cancelled. This is the preferred output if you want to provide a list of all bookings for visual presentation.
+`GET /bookings/visible` will return all active bookings as well as those declined, cancelled or waitlisted. This is the preferred output if you want to provide a list of all bookings for visual presentation.
 
-`GET /bookings/no_status` will return all active bookings with no status set.
+`GET /bookings/no_status` will return past confirmed bookings with a person where the status is not `completed` or `no_show`.
 
-Response
+Abbreviated response. Responses include all attributes listed above, including the full `person` object and the related `resource`, `service` and `event` objects with id and title (use the `extended` parameter for their full data).
 
 ```json
 [
@@ -136,8 +136,8 @@ Response
   <tr><td>resource_id</td><td>Integer or array of integers</td><td></td></tr>
   <tr><td>person_id</td><td>Integer or array of integers</td><td></td></tr>
   <tr><td>external_id</td><td>String</td><td></td></tr>
-  <tr><td>start</td><td>Datetime</td><td>booked_from after param. Also accepts the values now and today.</td></tr>
-  <tr><td>end</td><td>Datetime</td><td>booked_to before param. Also accepts the values now and today.</td></tr>
+  <tr><td>start</td><td>Datetime</td><td>booked_to after param. Combine with end to return all bookings that overlap the period. Also accepts the values now and today.</td></tr>
+  <tr><td>end</td><td>Datetime</td><td>booked_from before param. Also accepts the values now and today.</td></tr>
   <tr><td>since</td><td>Datetime</td><td>updated_at after param. Also accepts the values now and today.</td></tr>
   <tr><td>collection_id</td><td>UUID</td><td></td></tr>
   <tr><td>state</td><td>String or array of strings</td><td>See states</td></tr>
@@ -231,8 +231,8 @@ The parameters for recurrence are not set in `booking` but in `recurring`.
 <table>
   <tr><th>Name</th><th>Type</th><th>Description</th></tr>
   <tr><td>rrule</td><td>String</td><td>Repeating pattern. Example: `FREQ=DAILY;UNTIL=19971224T000000Z`.</td></tr>
-  <tr><td>rdate</td><td>String</td><td>List of recurring dates. Example: `VALUE=DATE:19970101,19970120,19970217,19970421`.</td></tr>
-  <tr><td>exdate</td><td>String</td><td>List of dates that should be excluded from the recurring rule. Example: `VALUE=DATE:19970102`.</td></tr>
+  <tr><td>rdate</td><td>String</td><td>Comma separated list of recurring dates. Example: `19970101,19970120,19970217,19970421`.</td></tr>
+  <tr><td>exdate</td><td>String</td><td>Comma separated list of dates that should be excluded from the recurring rule. Example: `19970102`.</td></tr>
 </table>
 
 You should always specify COUNT or UNTIL with RRULE. The max number of occurrences is 731, regardless if a limit is set or not.

_endpoints/categories.md

@@ -33,6 +33,7 @@ Response
       "custom_data": null,
       "id": 1,
       "parent_id": null,
+      "priority_value": null,
       "title": "My first little category",
       "updated_at": "2012-09-20T15:34:16+02:00"
     }

_endpoints/coupons.md

@@ -11,10 +11,10 @@ description: API reference for the Makeplans coupons endpoint — attributes and
   <tr><td>id</td><td>Integer</td><td>Automatically set</td></tr>
   <tr><td>created_at</td><td>Datetime</td><td>Automatically set</td></tr>
   <tr><td>updated_at</td><td>Datetime</td><td>Automatically set</td></tr>
-  <tr><td>title</td><td>String</td><td>Required</td></tr>
+  <tr><td>title</td><td>String</td><td>Not required</td></tr>
   <tr><td>code</td><td>String</td><td>Required</td></tr>
-  <tr><td>value_type</td><td>String</td><td>Values: percentage or amount.</td></tr>
-  <tr><td>value</td><td>Integer</td><td>Required</td></tr>
+  <tr><td>value_type</td><td>String</td><td>Required. Values: percentage or amount.</td></tr>
+  <tr><td>value</td><td>Integer</td><td>Required. Maximum 100 when value_type is percentage.</td></tr>
   <tr><td>valid_from</td><td>Datetime</td><td></td></tr>
   <tr><td>valid_until</td><td>Datetime</td><td></td></tr>
   <tr><td>active</td><td>Boolean</td><td></td></tr>

_endpoints/message-templates.md

@@ -13,11 +13,11 @@ Message templates define the content of messages sent to customers for booking e
   <tr><td>id</td><td>Integer</td><td>Automatically set</td></tr>
   <tr><td>created_at</td><td>Datetime</td><td>Automatically set</td></tr>
   <tr><td>updated_at</td><td>Datetime</td><td>Automatically set</td></tr>
-  <tr><td>message_type</td><td>String</td><td>Values: confirmation, reminder, follow_up. See message types.</td></tr>
-  <tr><td>delivery_type</td><td>String</td><td>Values: email, sms.</td></tr>
-  <tr><td>subject</td><td>String</td><td>Message subject line. Only applicable for email.</td></tr>
-  <tr><td>template</td><td>Liquid-Text</td><td>Message body template.</td></tr>
-  <tr><td>delivery_timing</td><td>String</td><td>When the message should be delivered. See delivery timing.</td></tr>
+  <tr><td>message_type</td><td>String</td><td>Required. Values: confirmation, reminder, follow_up. See message types.</td></tr>
+  <tr><td>delivery_type</td><td>String</td><td>Required. Values: email, sms.</td></tr>
+  <tr><td>subject</td><td>String</td><td>Message subject line. Required for email, not applicable for sms.</td></tr>
+  <tr><td>template</td><td>Liquid-Text</td><td>Required. Message body template.</td></tr>
+  <tr><td>delivery_timing</td><td>String</td><td>When the message should be delivered. Required except for confirmation. See delivery timing.</td></tr>
   <tr><td>active</td><td>Boolean</td><td>Whether the template is active.</td></tr>
   <tr><td>services</td><td>Array</td><td>Service IDs this template applies to.</td></tr>
   <tr><td>settings</td><td>Object</td><td>Not required. Key/value. Stored as strings.</td></tr>

_endpoints/orders.md

@@ -42,6 +42,8 @@ The response includes nested `person` and `order_line_items`.
   <tr><td>quantity</td><td>Integer</td><td></td></tr>
   <tr><td>amount</td><td>Decimal</td><td>Unit price</td></tr>
   <tr><td>gift_card_id</td><td>Integer</td><td>Associated gift card if applicable</td></tr>
+  <tr><td>pass_id</td><td>Integer</td><td>Associated pass if applicable</td></tr>
+  <tr><td>subscription_id</td><td>Integer</td><td>Associated subscription if applicable</td></tr>
   <tr><td>booking_id</td><td>Integer</td><td>Associated booking if applicable</td></tr>
 </table>
 
@@ -79,6 +81,8 @@ Response
           "quantity": 1,
           "amount": "1000.0",
           "gift_card_id": null,
+          "pass_id": null,
+          "subscription_id": null,
           "booking_id": null
         }
       ]

_endpoints/people.md

@@ -77,7 +77,7 @@ Response
 
 ### Query Parameters
 
-You can search multiple columns at once, for example `email` and `phone_number`, or you can use the shorthand `search` to search email, phone number, national id no or name.
+You can search multiple columns at once, for example `email` and `phone_number` — people matching any of the specified columns are returned. Or you can use the shorthand `search` to search email, phone number, national id no or name.
 
 <table>
   <tr><th>Name</th><th>Type</th><th>Description</th></tr>
@@ -131,7 +131,7 @@ Please note that this token is perishable, meaning that it will be removed from
 
 ### Send perishable token
 
-`POST /people/perishable_token/send` will send a SMS with a five digit code (the token) or an email with a link which includes the token in the URL. Specify either `email` or `phone_number`.
+`POST /people/perishable_token/send` will send a SMS with a six digit code (the token) or an email with a link which includes the token in the URL. Specify either `email` or `phone_number`.
 
 ### Verify perishable token
 

_endpoints/resource-exception-dates.md

@@ -11,7 +11,7 @@ If a resource should be closed for a week then you would add resource exception
 If a resource should have opening hours 08:00 to 14:00 on January 5th 2016 instead of the default opening hours for that weekday which could be 09:00 to 15:00, then add it as a resource exception date.
 See [resource opening hours](/endpoints/resources/#default-opening-hours) for how to specify.
 
-A `null` value will fallback to the default availability for the resource. An empty array means the resource is closed on the specified exception date.
+A `null` value or an empty array means the resource is closed on the specified exception date. To fall back to the default availability for the resource, delete the exception date.
 
 Exception dates are related to a resource: `GET /resources/{resource_id}/exception_dates`.
 
@@ -37,7 +37,7 @@ An exception date without `service_id` applies to the resource. All endpoints be
 
 ## Listing
 
-`GET /resources/{resource_id}/exception_dates` will return all exception dates for resource with id `{resource_id}`.
+`GET /resources/{resource_id}/exception_dates` will return exception dates for resource with id `{resource_id}` within the specified period. Without `from` and `to` only the current week is returned.
 
 Response
 
@@ -49,6 +49,7 @@ Response
       "resource_id": 1,
       "exception_date": "2014-01-08",
       "opening_hours": ["08:00", "12:00", "12:30", "17:30"],
+      "service_id": null,
       "updated_at": "2012-09-20T15:34:16+02:00"
     }
   }
@@ -59,8 +60,8 @@ Response
 
 <table>
   <tr><th>Name</th><th>Type</th><th>Description</th></tr>
-  <tr><td>from</td><td>Date</td><td></td></tr>
-  <tr><td>to</td><td>Date</td><td></td></tr>
+  <tr><td>from</td><td>Date</td><td>Default: beginning of the current week.</td></tr>
+  <tr><td>to</td><td>Date</td><td>Default: end of the current week.</td></tr>
   <tr><td>service_id</td><td>Integer</td><td>Return exception dates scoped to this service. When not set only resource exception dates are returned.</td></tr>
 </table>
 

_endpoints/resources.md

@@ -61,6 +61,7 @@ Response
     "resource": {
       "capacity": 1,
       "created_at": "2012-09-20T15:34:16+02:00",
+      "custom_data": null,
       "id": 1,
       "opening_hours_mon": ["08:00", "16:00"],
       "opening_hours_tue": ["08:00", "11:00", "13:00", "17:30"],

_endpoints/services.md

@@ -1,15 +1,18 @@
 ---
 title: Services
 nav_order: 4
-description: API reference for the Makeplans services endpoint — the four service types and their attributes.
+description: API reference for the Makeplans services endpoint — service types and their attributes.
 ---
 
-There are four types of services:
+There are seven types of services:
 
 * Appointment
 * Attendance
 * Product
 * Gift card
+* Addon
+* Subscription
+* Pass
 
 Appointments can be booked within fixed opening hours as specified on the Resource and with exceptions specified in ResourceExceptionDate.
 
@@ -34,7 +37,7 @@ Attendance at an event is also a booking but the individual booking datetime or
   <tr><td>same_day</td><td>Boolean</td><td>Not required (default false)</td></tr>
   <tr><td>template</td><td>String</td><td>Component template (calendar view)</td></tr>
   <tr><td>interval_rounding</td><td>Integer</td><td>Overrides account default (see info on account object)</td></tr>
-  <tr><td>booking_type</td><td>String</td><td>Required. Values: appointment (default), attendance, product, gift_card</td></tr>
+  <tr><td>booking_type</td><td>String</td><td>Required. Values: appointment (default), attendance, product, gift_card, addon, subscription, pass</td></tr>
   <tr><td>custom_data</td><td>Object</td><td>Not required. Key/value. Stored as strings.</td></tr>
   <tr><td>booking_form</td><td>Liquid-Text</td><td>Custom booking form</td></tr>
   <tr><td>mail_verification</td><td>Liquid-Text</td><td></td></tr>
@@ -58,13 +61,19 @@ Attendance at an event is also a booking but the individual booking datetime or
   <tr><td>priority_strategy</td><td>String</td><td>Not required. Strategy for resource priority assignment.</td></tr>
   <tr><td>availability_type</td><td>String</td><td>Not required. Values: resource (default), provider. With resource the opening hours on the resource are used. With provider the opening hours on the [provider](/endpoints/providers/) are used.</td></tr>
   <tr><td>priority_value</td><td>Integer</td><td>Not required. Priority value for ordering.</td></tr>
+  <tr><td>quota</td><td>Integer</td><td>Number of uses. Required for subscription and pass unless `unlimited` is true. Not applicable for other types.</td></tr>
+  <tr><td>unlimited</td><td>Boolean</td><td>Unlimited number of uses. Only applicable for subscription and pass. Default: false.</td></tr>
+  <tr><td>billing_period</td><td>Integer</td><td>Required for subscription. Not applicable for other types.</td></tr>
+  <tr><td>renewal_price</td><td>Decimal</td><td>Only applicable for subscription.</td></tr>
+  <tr><td>validity_days</td><td>Integer</td><td>Number of days the pass is valid. Required for unlimited passes. Only applicable for pass.</td></tr>
+  <tr><td>linked_service_ids</td><td>Array</td><td>Ids of linked services.</td></tr>
 </table>
 
 ### Deprecated attributes
 
 <table>
   <tr><th>Name</th><th>Type</th><th>Description</th></tr>
-  <tr><td>booking_type_id</td><td>Integer</td><td>1: appointment. 2: attendance. 3: gift_card. 4: product.</td></tr>
+  <tr><td>booking_type_id</td><td>Integer</td><td>1: appointment. 2: attendance. 3: gift_card. 4: product. 5: addon. 6: subscription. 7: pass.</td></tr>
 </table>
 
 ## Listing
@@ -75,10 +84,16 @@ Attendance at an event is also a booking but the individual booking datetime or
 
 `GET /services/attendances` will return all services with booking_type=attendance.
 
-`GET /services/products` will return all services with booking_type=product or booking_type=gift_card.
+`GET /services/products` will return all sellable services (booking_type product, gift_card, addon, subscription or pass).
 
 `GET /services/gift_cards` will return all services with booking_type=gift_card.
 
+`GET /services/addons` will return all services with booking_type=addon.
+
+`GET /services/subscriptions` will return all services with booking_type=subscription.
+
+`GET /services/passes` will return all services with booking_type=pass.
+
 ### Query Parameters
 
 <table>