Fix spelling, inconsistencies, and bugs across API documentation

Correct factual errors (wrong HTTP method for user creation, wrong noun
in event update, inverted ignore_capacity logic, singular webhook paths),
fix spelling mistakes and grammar across endpoints/guides/changelog,
standardize DateTime to Datetime, remove trailing slashes from listing
URLs, update curl examples to use Bearer auth, add missing attributes
to JSON examples and attribute tables, add date-handling examples, and
add update endpoint for providers.

Co-Authored-By: Claude <noreply@anthropic.com>

Author: espen

_endpoints/account.md

@@ -122,7 +122,7 @@ Response
 
 ## Users
 
-Users who can login into the account.
+Users who can log in to the account.
 
 ### Attributes for user role on the account
 
@@ -180,6 +180,6 @@ Response
 
 `GET /client/users/{user_link_id}` will get a user with id `{user_link_id}`.
 
-### Add new user
+## Add new user
 
-`GET /client/users` will create a new user. An email is sent to the user so the user can specify their password.
+`POST /client/users` will create a new user. An email is sent to the user so the user can specify their password.

_endpoints/bookings.md

@@ -8,8 +8,8 @@ nav_order: 2
 <table>
   <tr><th>Name</th><th>Type</th><th>Description</th></tr>
   <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>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>service_id</td><td>Integer</td><td>Not required</td></tr>
   <tr><td>event_id</td><td>Integer</td><td>Not required</td></tr>
   <tr><td>resource_id</td><td>Integer</td><td>Required</td></tr>
@@ -19,9 +19,9 @@ nav_order: 2
   <tr><td>expires_at</td><td>Datetime</td><td>Not required</td></tr>
   <tr><td>title</td><td>String</td><td>Not required</td></tr>
   <tr><td>notes</td><td>Text</td><td>Not required</td></tr>
-  <tr><td>reminder_at</td><td>DateTime</td><td>Not required</td></tr>
-  <tr><td>reminded_at</td><td>DateTime</td><td>Not required</td></tr>
-  <tr><td>paid_at</td><td>DateTime</td><td>Not required</td></tr>
+  <tr><td>reminder_at</td><td>Datetime</td><td>Not required</td></tr>
+  <tr><td>reminded_at</td><td>Datetime</td><td>Not required</td></tr>
+  <tr><td>paid_at</td><td>Datetime</td><td>Not required</td></tr>
   <tr><td>external_id</td><td>String</td><td>Not required</td></tr>
   <tr><td>google_order_number</td><td>String</td><td>Not required</td></tr>
   <tr><td>custom_data</td><td>Array</td><td>Not required</td></tr>
@@ -77,11 +77,11 @@ See query parameters for filtering the output beyond the default outputs.
 
 `GET /bookings/recent` will return all active bookings ordered based on updated_at.
 
-`GET /bookings/upcoming` will return all active bookings from and including `{date}`.
+`GET /bookings/upcoming` will return all future active bookings.
 
 `GET /bookings/unconfirmed` will return only unconfirmed bookings.
 
-`GET /bookings/all` will return all bookings of all states (including `declined`, `cancelled`, `deleted`, and `verification_expired`). This is a useful output for syncronisation when you need to keep a track of deleted bookings.
+`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.
 
@@ -120,9 +120,9 @@ 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</td></tr>
-  <tr><td>end</td><td>DateTime</td><td>booked_to before param</td></tr>
-  <tr><td>since</td><td>DateTime</td><td>updated_at after param</td></tr>
+  <tr><td>start</td><td>Datetime</td><td>booked_from after param</td></tr>
+  <tr><td>end</td><td>Datetime</td><td>booked_to before param</td></tr>
+  <tr><td>since</td><td>Datetime</td><td>updated_at after param</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>
   <tr><td>status</td><td>String or array of strings</td><td>See statuses</td></tr>
@@ -162,7 +162,7 @@ These parameters are part of booking: `booking[public_booking]`.
 
 ### Additional parameters
 
-These parameters are part not of `booking[]`: `confirm`.
+These parameters are not part of `booking[]`: `confirm`.
 
 Outgoing messages requires person_id and service_id.
 
@@ -171,7 +171,7 @@ Default action for outgoing messages is according to the settings for booking ve
 <table>
   <tr><th>Name</th><th>Type</th><th>Description</th></tr>
   <tr><td>confirm</td><td>Boolean</td><td>If set to false then the 'initiate verification' event is executed. If verification is required the state will be set to `awaiting_verification`. If no verification is required then the state will be set to `awaiting_confirmation` or `confirmed`.</td></tr>
-  <tr><td>ignore_capacity</td><td>Boolean</td><td>Will force save the booking even though other bookings exists within the same time on the specified resource_id (double booking). Not applicable when `public_booking` is set to false (no double bookings allowed). Default: false.</td></tr>
+  <tr><td>ignore_capacity</td><td>Boolean</td><td>Will force save the booking even though other bookings exists within the same time on the specified resource_id (double booking). Not applicable when `public_booking` is set to true (no double bookings allowed). Default: false.</td></tr>
   <tr><td>add_reminder_sms</td><td>Boolean</td><td>Automatically adds `reminder_at` based on setting from account attribute `sms_reminder_time`. Default: at 12PM the day before the appointment.</td></tr>
   <tr><td>add_messages</td><td>Boolean</td><td>Automatically generate messages based on message templates. (NOTE: Beta functionality available by invitation.)</td></tr>
   <tr><td>verification_send_email</td><td>Boolean</td><td>Send out verification email. Only applicable when `confirm` is set to false.</td></tr>

_endpoints/categories.md

@@ -19,7 +19,7 @@ Services can be listed in a category. Categories can be presented like a tree. R
 
 ## Listing
 
-`GET /categories/` will return all categories.
+`GET /categories` will return all categories.
 
 Response
 

_endpoints/coupons.md

@@ -30,7 +30,7 @@ nav_order: 10
 
 ## Listing
 
-`GET /coupons/` will return all coupons.
+`GET /coupons` will return all coupons.
 
 Response
 

_endpoints/events.md

@@ -3,7 +3,7 @@ title: Events
 nav_order: 5
 ---
 
-Unlike appointments made through a normal service events starts and ends at a specific time. An event is connected to a resource and a service. It could be either a one-off event (e.q. a concert) or something that occurs multiple times (e.q. spinning class). Event bookings have a strong relation to the event. That means that it is not possible to modify details such as `{booked_from}`, `{booked_to}`, `{resource_id}` and `{service_id}` for the `{booking}`. To make such changes it must be done to the event. All bookings connected to the event will then automatically me modified.
+Unlike appointments made through a normal service events starts and ends at a specific time. An event is connected to a resource and a service. It could be either a one-off event (e.g. a concert) or something that occurs multiple times (e.g. spinning class). Event bookings have a strong relation to the event. That means that it is not possible to modify details such as `{booked_from}`, `{booked_to}`, `{resource_id}` and `{service_id}` for the `{booking}`. To make such changes it must be done to the event. All bookings connected to the event will then automatically be modified.
 
 While events are connected to a resource bookings or capacity of an event are not restricted by the opening hours or availability of a resource.
 
@@ -21,12 +21,13 @@ While events are connected to a resource bookings or capacity of an event are no
   <tr><td>starts_at</td><td>Datetime</td><td>Required</td></tr>
   <tr><td>ends_at</td><td>Datetime</td><td>Required</td></tr>
   <tr><td>custom_data</td><td>Array</td><td>Not required</td></tr>
+  <tr><td>title</td><td>String</td><td></td></tr>
   <tr><td>description</td><td>Text</td><td></td></tr>
 </table>
 
 ## Listing
 
-`GET /events/` will return all events.
+`GET /events` will return all events.
 
 Response
 
@@ -57,9 +58,9 @@ Response
   <tr><th>Name</th><th>Type</th><th>Description</th></tr>
   <tr><td>service_id</td><td>Integer</td><td></td></tr>
   <tr><td>resource_id</td><td>Integer</td><td></td></tr>
-  <tr><td>start</td><td>DateTime</td><td>starts_at after param</td></tr>
-  <tr><td>end</td><td>DateTime</td><td>ends_at before param</td></tr>
-  <tr><td>since</td><td>DateTime</td><td>updated_at after param</td></tr>
+  <tr><td>start</td><td>Datetime</td><td>starts_at after param</td></tr>
+  <tr><td>end</td><td>Datetime</td><td>ends_at before param</td></tr>
+  <tr><td>since</td><td>Datetime</td><td>updated_at after param</td></tr>
 </table>
 
 ## Get event
@@ -72,7 +73,7 @@ Response
 
 ## Add recurring/multiple events
 
-`POST /events/recurring` will create a multiple events.
+`POST /events/recurring` will create multiple events.
 
 The recurrence format follows the [iCalendar specification](https://tools.ietf.org/html/rfc5545){:target="_blank"}. The attributes for recurrence are: `RRULE`, `RDATE`, `EXDATE`. For an introduction and examples of these parameters see [this section from the iCalendar specification](http://www.kanzaki.com/docs/ical/rrule.html){:target="_blank"}.
 
@@ -103,11 +104,11 @@ You should always specify COUNT or UNTIL with RRULE. The max number of occurrenc
 
 ## Update event
 
-`PUT /events/{event_id}` will update existing service with id `{event_id}`.
+`PUT /events/{event_id}` will update existing event with id `{event_id}`.
 
 ## Delete event
 
-`DELETE /events/{event_id}` will delete existing event with id `{event_id}`. Deleting a event will set it to active=false and will not be returned in any listings.
+`DELETE /events/{event_id}` will delete existing event with id `{event_id}`. Deleting an event will set it to active=false and will not be returned in any listings.
 
 ## List bookings
 

_endpoints/gift-cards.md

@@ -36,6 +36,8 @@ Response
       "value": 500,
       "valid_until": null,
       "active": true,
+      "person_id": null,
+      "purchased_by_person_id": 888,
       "custom_data": null,
       "created_at": "2026-03-26T10:00:00+02:00",
       "updated_at": "2026-03-26T10:00:00+02:00"

_endpoints/orders.md

@@ -46,7 +46,7 @@ The response includes nested `person` and `order_line_items`.
 
 ## Listing
 
-`GET /orders` will return all orders.
+`GET /orders` will return all orders. Orders are read-only via the API.
 
 Response
 

_endpoints/people.md

@@ -3,7 +3,7 @@ title: People
 nav_order: 3
 ---
 
-The primary key for a person is `id`. However the following fields are unique: `email`, `phonenumber`, `national_id_no` and `provider`+`uid`. There are no specific requirements for input but a person needs to have either name, email, national id number or phone number.
+The primary key for a person is `id`. However the following fields are unique: `email`, `phone_number`, `national_id_no` and `provider`+`uid`. There are no specific requirements for input but a person needs to have either name, email, national id number or phone number.
 
 It is possible to give a person ability to book on behalf of other people. This is linked through the `parent_id` attribute.
 
@@ -52,9 +52,16 @@ Response
       "name": "Espen Antonsen",
       "national_id_no": null,
       "notes": null,
-      "phonenumber": "",
-      "updated_at": "2012-09-20T15:34:16+02:00",
-      "phone_number_formatted": null
+      "phone_number": "",
+      "phone_number_formatted": null,
+      "date_of_birth": null,
+      "street": null,
+      "city": null,
+      "postal_code": null,
+      "state": null,
+      "country_code": null,
+      "parent_id": null,
+      "updated_at": "2012-09-20T15:34:16+02:00"
     }
   }
 ]

_endpoints/providers.md

@@ -28,7 +28,7 @@ Opening hours for a provider works in the same way as availability is defined on
 
 ## Listing
 
-`GET /providers/` will return all providers.
+`GET /providers` will return all providers.
 
 Response
 
@@ -40,6 +40,13 @@ Response
       "id": 1,
       "resource_id": 1,
       "service_id": 1,
+      "opening_hours_mon": null,
+      "opening_hours_tue": null,
+      "opening_hours_wed": null,
+      "opening_hours_thu": null,
+      "opening_hours_fri": null,
+      "opening_hours_sat": null,
+      "opening_hours_sun": null,
       "updated_at": "2012-09-20T15:34:16+02:00"
     }
   }
@@ -54,6 +61,10 @@ Response
 
 `POST /providers` will create a new provider.
 
+## Update provider
+
+`PUT /providers/{provider_id}` will update existing provider with id `{provider_id}`.
+
 ## Delete provider
 
 `DELETE /providers/{provider_id}` will delete existing provider with id `{provider_id}`.

_endpoints/resource-exception-dates.md

@@ -5,7 +5,7 @@ nav_order: 7
 
 Opening hours for a resource is what is used to generate available slots for a service.
 It is based on the default opening hours on the resource unless anything else is specified by a resource exception date.
-So ignore the poorly naming of the feature and treat it as opening hours on dates.
+So ignore the poor naming of the feature and treat it as opening hours on dates.
 If a resource should be closed for a week then you would add resource exception dates.
 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.