myWebLog API v5

Current version: 5.25.0, 2026-11-22. What changed in each version: Version history.

New framework

Version 5 is built on a new framework. Every function of v4 is here in a new form: token, organization, users (read, create, change, delete), memberships, user groups, objects, bookings, flight logs, flight types, transactions (read, create) and the login check.

New in v5, not in v4: the organization's expiry date types (read, create, change, delete), a user's expiry dates (read, set, remove), and every member's dates in one list; the organization's log (read); bookings made and changed for members (POST, PATCH), with the reminders by email and SMS.

The machine-readable description of the API is openapi.yaml (OpenAPI 3.0). The same endpoints are ready to try in Postman: import postman_collection.json and put your token in the collection's variable bearerToken, or set up OAuth 2.0 as described under Authentication.

Coming from v4? Moving from v4 to v5 lists every difference, with what to change.

Address

https://api.myweblog.se/main/v5/{resource}, for example https://api.myweblog.se/main/v5/token

One item is addressed by its id in the path, for example /users/5. An address does not end with a slash: /token works, /token/ gives 404. A query parameter the endpoint does not know gives 400, so a misspelled filter is never silently ignored.

Authentication

A token is created by an administrator on the myWebLog website (Integrations, API). It can be used in two ways.

OAuth 2.0 client credentials (recommended). Exchange the token for an access token at POST /oauth/token and send the access token with every call as Authorization: Bearer [access token]. The client id is the number shown as "Client ID" next to the token on the website; the client secret is the token itself. An access token is valid for 3600 seconds ("expires_in" says exactly). When it has expired the API answers 401 with WWW-Authenticate: Bearer error="invalid_token", and the program fetches a new one. A standard OAuth 2.0 client library does all of this by itself, given the token URL, the client id and the client secret.

The token sent directly, as in v4: Authorization: Bearer [your token]. Accepted until 2027-12-31. Every reply to such a call has a Sunset header with that date and a Link header to the migration guide. From 2028-01-01 these calls are answered with 401 (code 10015).

Both ways give the same rights, the same IP address limits and the same rate limit, and both stop working at once when the token is deleted on the website. Fetching an access token counts as one call of the token, so fetch one when you have none or it is about to expire, not before every call.

In Postman: Authorization type OAuth 2.0, grant type Client Credentials, access token URL https://api.myweblog.se/main/v5/oauth/token, client ID and client secret from the website, client authentication "Send as Basic Auth header".

Sending data

POST and PATCH take a JSON object as the request body. The one exception is POST /oauth/token, which takes form data as the OAuth 2.0 standard says. The id of the item is never in the body: it is in the address, for example PATCH /users/5.

A value in the body has the same type as in a reply. Text is text: a member number, a phone number and an account number are sent as "007", not as 7. An id is a number, yes or no is true or false, an amount is a number, and a date is written "2026-09-30". A value of another type gives 400.

A field the endpoint does not know gives 400, so a misspelled field is never silently ignored. A field inside an object is named with the object's name in front in an error reply, for example "address.city", and an item of a list by its place, counted from 0: "email[1]" is the second address.

Headers

Header In Description
Authorization Request Required: Bearer [access token] (OAuth 2.0, see Authentication), or Bearer [your token] until 2027-12-31. The word Bearer must be included. For POST /oauth/token: Basic [client_id:client_secret in base64].
WWW-Authenticate Reply With 401: Bearer, and error="invalid_token" when an access token has expired or is not accepted (fetch a new one).
Sunset
Link
Reply With a call where the token was sent directly: the date after which that stops working (2027-12-31), and a link to the migration guide.
Request-Id Request and reply Optional. Your own id for the request, at most 64 characters. It is returned with the reply, and in the body of an error reply. If you send none, one is made for you. Quote it when you contact support.
RateLimit-Limit
RateLimit-Remaining
RateLimit-Reset
Reply Calls allowed per minute for the token, calls left in the current minute, and seconds until the count starts over.
Retry-After Reply With 429: seconds to wait before the next call.
Allow Reply With 405: the methods the address accepts.
Location Reply With 201: the address of the item that was created.

Replies

A successful reply has the result under "data". When an item is created (201) or changed (200), the reply is the item, as GET gives it. When an item is deleted (204), the reply has no body.

{
  "data": {
    "description": "Postman",
    "owner": { "id": 17, "name": "Anna Berg" },
    "organization": { "id": 3, "name": "Svanshalls FK" },
    "rights": { "users": "rw", "transactions": "r" }
  }
}

An error reply follows the standard "Problem Details" (RFC 9457) and has the content type application/problem+json. "code" is the number in the error code table at the end of this page. "errors" is only present when the error is about named parameters or fields: the ones that are wrong (400), or the ones whose value is already in use (409). It names each of them, so everything can be corrected at once:

{
  "type": "https://api.myweblog.se/errors/validation",
  "title": "The request has invalid parameters",
  "status": 400,
  "code": 10005,
  "request_id": "b7e2c41a9d0f3e55",
  "errors": [
    { "field": "verbose", "code": 10007, "message": "Unknown parameter" }
  ]
}

Lists

A list has its items under "data", and says where the page is in the list:

{
  "data": [ { "id": 5, ... }, { "id": 6, ... } ],
  "meta": { "count": 2, "limit": 2, "offset": 0, "has_more": true },
  "links": { "next": "https://api.myweblog.se/main/v5/users?limit=2&offset=2" }
}
Parameter Description
limit (int)How many items to return, 1 to 500. Default 100.
offset (int)How many items to skip. Default 0. To read a whole list, follow "links.next" until it is null.
include_total (bool)true adds "meta.total", the number of all items that match the filters. It costs an extra database query, so ask for it on the first page only.
include (list)Optional blocks of each item, separated by commas, for example include=email,phone. Each block adds one key with the same name. Only the blocks asked for are fetched.
exclude (list)Fields to leave out of each item, separated by commas, for example exclude=comment,type_name. It makes the reply smaller. Only the fields an item always has can be named; a block is left out by not asking for it.

include and exclude also work where one item is returned, and on the reply to a POST or PATCH. exclude takes the names at the top level of an item: exclude=membership leaves out the whole membership of a user, and a field inside it cannot be left out on its own. A name the item does not have gives 400, and the reply lists the names that can be used. A field that is left out can still be used as a filter.

Filters: a yes/no filter (bool) takes true or false; leave it out for both. In a text search (search), * stands for any characters and is the only wildcard. A date is written YYYY-MM-DD. A value that is missing is null, and a list without items is [].

Types: an id is a number. A date is written "2026-10-03". A point in time is in UTC and written "2026-10-03T23:10:00Z"; its name ends with _at. The one exception is the clock times of a logged flight (blockoff_at, takeoff_at, landing_at, blockon_at): they are the logbook's own clock times written the same way, local time for most organizations, and the points in time are in the fields ending in _utc (see GET /flightlogs). What a person types, such as a member number, a phone number or an account number, is always text.

Status codes

Status Meaning
200OK.
201Created. The reply is the new item, and the Location header has its address.
204Deleted. The reply has no body.
400A parameter or the body is wrong: a value is missing or has the wrong form, a parameter or field is not known, or a PATCH has nothing to change. The body of a POST or PATCH must be a JSON object.
401The token or access token is missing or not accepted, or the access token has expired (then WWW-Authenticate has error="invalid_token": fetch a new one). 401 always and only concerns the token.
403The token is valid but lacks the right for this endpoint.
404The address or the item does not exist.
405The address exists but not with this method. See the Allow header.
409The request is right in its form but cannot be carried out as things are: a username or member number is already in use, the same transaction has been sent before, the date is before the transaction lock date, the user has a balance or is an administrator, the organization does not use the flight log, or other data depends on a setting that is being deleted (see below).
429Too many calls: more than 120 per minute with one token, or too many failed token checks from one IP address. See the Retry-After header.
500A fault on our side. It has been logged; quote the request id to support.

Deleting a setting that data depends on

Some of the organization's settings have members' data that depends on them. An expiry date type has the members' dates of it. Deleting such a setting deletes that data too, and it cannot be brought back, the same as on the website.

So the API asks first. DELETE of a setting that data depends on answers 409 with code 10106 and deletes nothing. "dependents" says what depends on it and how much. The same call with delete_dependents=true deletes the setting together with that data. A setting that nothing depends on is deleted at once (204).

{
  "type": "https://api.myweblog.se/errors/conflict",
  "title": "Other data depends on this",
  "status": 409,
  "code": 10106,
  "request_id": "b7e2c41a9d0f3e55",
  "detail": "Members have dates of this type. Send delete_dependents=true to delete them together with it.",
  "dependents": [
    { "name": "user_expiry_dates", "count": 37 }
  ]
}

A program can send the DELETE without the parameter first, to see what would be deleted. The parameter is called delete_dependents wherever it is used.

Endpoints

Click on an endpoint to see its details.

token

POST
/oauth/token Exchanges a token for an access token that is valid for one hour (OAuth 2.0 client credentials).
Information Body Response

Called without a Bearer token. The client id and secret are sent in a Basic Authorization header (client_id:client_secret in base64, which is what OAuth 2.0 libraries do), or as the form fields client_id and client_secret.

The client id is the token's "Client ID" on the website; the client secret is the token. The access token has the token's rights, is limited to the same IP addresses, counts against the same rate limit and stops working when the token is deleted. Fetching it counts as one call.

The reply follows the OAuth 2.0 standard: "access_token", "token_type" ("Bearer"), "expires_in" (3600) and, for information, "scope" (the rights, as "users:rw transactions:r"). An error is {"error": ..., "error_description": ...} with 400 (invalid_request, unsupported_grant_type) or 401 (invalid_client: wrong id or secret, deleted token, IP address not allowed, or the owner is no longer an administrator). 429 and 500 are the API's usual replies.

Form data (application/x-www-form-urlencoded), not JSON:

grant_type: must be client_credentials.
client_id, client_secret: only when they are not sent in the Basic Authorization header.

200 OK
GET
/token The token used for the request: its description, owner, organization and rights. Also the way to test that a token works.
Information Parameters Response

Any valid token can call this. It replaces /token/rights/ and /test/ in v4.

"rights" has one entry per module: "r" (read), "w" (write) or "rw". In v5 a module has the same name as its resource, so a token's rights for Economy, Logbook, Login check and Organisation are listed as transactions, flightlogs, login_checks and organization.

None
200 OK

users

GET
/users The members of the organization, sorted by name.
Information Filters Blocks (include) Response

Requires read access in the "Users" module.

Always returned: id, username, member_number, ksak_member_number, nlf_member_number, name, first_name, last_name_particle, last_name, last_first_name, membership (id and name), active, locked, locked_login, has_invalid_email_address.

member_number, phone numbers and postal codes are always text, so 007 stays "007".

The last four blocks hold the most personal data and also require read access in the "Users, sensitive data" module (users_sensitive).

The block expiry_dates has the user's dates: id and name of the expiry date type (see expiry dates below), expiry_date, expired and image_missing (as for GET /users/{id}/expiry-dates below). "Never expires" is written as the date 2999-12-31. A date is set with PUT /users/{id}/expiry-dates/{type_id} and removed with DELETE.

New in 5.22: image_missing, and expired is true also when the type requires an image and the date has none.

The block address has street_address (a list), postal_code, city, country (the name in capitals, "SWEDEN") and, new in 5.24, country_code: the country as its ISO 3166-1 two-letter code ("SE"), null when the user has no country.

The block account has balance, annual_fee, external_customer_number and, new in 5.12, the OCR references of the member's bank payments: ocr_reference (a payment into the account) and annual_fee_ocr_reference (the annual fee), the numbers the website's bank payment page shows the member, for matching the bank's payments in an accounting system. Both are null when the organization does not use OCR.

Replaces GET /users/ in v4. "verbose" is replaced by the blocks.

name (search)
username (search)
member_number (search)
membership_id (int)
membership_name (search)
active (bool)
locked (bool)
locked_login (bool)
has_invalid_email_address (bool)

limit, offset, include_total, exclude
email
address
phone
user_groups
roles
expiry_dates
account
misc_info
personal_identification_number
internal_notes
emergency_contact
access_card
200 OK
GET
/users/{id} One user.
Information Parameters Response

Requires read access in the "Users" module. The same fields and blocks as in the list.

Returns the user as one object under "data", or 404 if the organization has no user with that id.

Replaces GET /users/?id= in v4.

include, exclude
200 OK
POST
/users Creates a user.
Information Body Response

Requires write access in the "Users" module.

Creates the login and the membership together. No password is set: the new user sets one with "Reset my password" on the login page.

The username must start with the organization's id and a dash, for example "3-nils" in organization 3. Without a member_number the user gets the highest member number in the organization plus one, or 10000 if no user in the organization has a number yet.

membership_id and user_groups are ids of the organization's memberships and user groups. email and street_address are lists with at most two items. The country code of the mobile number may be written 46, +46 or 0046.

New in 5.24: the mobile number as one field, phone.mobile.e164, best written in international form ("+46701234567"; spaces, dashes and brackets are allowed). Without "+" or "00" it is read as a national number of phone.mobile.country (an ISO code such as "SE"), else of the user's country, else the organization's: "070-123 45 67" with "SE" is saved as "+46701234567". phone.mobile.country also says which country a shared calling code belongs to (+1: "US" or "CA"). e164 wins over country_code, initial_number and number when both are sent; those three are deprecated and accepted until 2027-06-30, and when they are sent alone the international number is made from them. A value that is no phone number gives 400 with code 10006 at phone.mobile.e164. The same rules apply to PATCH /users/{id}, where an e164 of null or "" (and none of the deprecated fields) removes the mobile.

The reply is the new user, as GET /users/{id} gives it, and takes the same include and exclude parameters. The Location header has the user's address.

409 with code 10030 if the username, the member number or the KSAK member number is already in use; "errors" names the fields. 409 with code 10040 if a trial organization already has 5 active users.

Replaces POST /users/ in v4. The field names are the same. New: every value must have the type shown here, and email, street_address and user_groups must be lists.

{
  "username": text*,
  "member_number": text,
  "ksak_member_number": text (digits),
  "external_customer_number": text,
  "first_name": text*,
  "last_name_particle": text,
  "last_name": text*,
  "personal_identification_number": text,
  "membership_id": number*,
  "user_groups": [number, ...],
  "email": [text, text],
  "address": {
    "street_address": [text, text],
    "postal_code": text,
    "city": text,
    "country": text
  },
  "phone": {
    "home": text,
    "work": text,
    "mobile": {
      "e164": text,
      "country": text,
      "country_code": text (digits, deprecated),
      "initial_number": text (digits, deprecated),
      "number": text (digits, deprecated)
    }
  },
  "emergency_contact": {
    "name": text,
    "phone": text,
    "relation": text
  }
}

* required

Parameters: include, exclude
201 Created
PATCH
/users/{id} Changes a user.
Information Body Response

Requires write access in the "Users" module.

Only the fields that are sent are changed. To change only the access card number, send {"access_card": {"number": "987654321"}}.

A field sent as null or as an empty text is emptied. first_name and last_name cannot be emptied. A list replaces the whole list: to keep two email addresses, send both. An email address that changes is no longer marked as invalid.

"active": false makes the user inactive, true makes the user active again.

Name, address, email and phone belong to the user's login, and can only be changed for users whose login was created by this organization (the username starts with the organization's id). For other users they give 409 with code 10105.

The reply is the changed user, as GET /users/{id} gives it, and takes the same include and exclude parameters.

400 with code 10105 if the body has no fields. 404 if the organization has no user with that id. 409 with code 10040 if a user is made active in a trial organization that already has 5 active users.

Replaces PATCH /users/ in v4. Changed: the id is in the address and not in the body; "status": {"active"} is now "active"; email is a list of addresses, not of objects; a date is written YYYY-MM-DD.

{
  "first_name": text,
  "last_name_particle": text,
  "last_name": text,
  "active": true or false,
  "email": [text, text],
  "address": {
    "street_address": [text, text],
    "postal_code": text,
    "city": text
  },
  "phone": {
    "home": text,
    "work": text,
    "mobile": {
      "e164": text,
      "country": text,
      "country_code": text (digits, deprecated),
      "initial_number": text (digits, deprecated),
      "number": text (digits, deprecated)
    }
  },
  "misc_info": text,
  "internal_notes": text,
  "access_card": {
    "number": text (at most 50 characters),
    "code": text (at most 10 characters),
    "expiry_date": date
  }
}

Parameters: include, exclude
200 OK
DELETE
/users/{id} Deletes a user.
Information Parameters Response

Requires write access in the "Users" module.

WARNING: a deleted user cannot be restored. Consider making the user inactive instead: PATCH /users/{id} with {"active": false}.

An administrator cannot be deleted, and neither can a user whose account balance is not zero: 409 with code 10105.

The reply has no body. 404 if the organization has no user with that id.

Replaces DELETE /users/?id= in v4.

None
204 No Content

organization

GET
/organization The token's own organization.
Information Parameters Response

Any valid token can call this.

Returns id, name and location: reference_icao, latitude, longitude, country, country_code and timezone.

New in 5.24: location.country_code, the country as its ISO 3166-1 two-letter code ("SE"). country is still the name in capitals ("SWEDEN").

New in 5.23: logbook, how the organization logs the clock times of its flights, so that a client can mark its time fields "LCL" or "UTC" as the website does: clock_times ("local" = local time at each airport, or "utc"), home_time_zone (with "local", the zone used for a place without a time zone of its own; null with "utc") and answered (false while no administrator has confirmed the rule on the website; clock_times is what applies until then). logbook is left out for an organization that does not have the logbook's clock yet: until the website opens it to every organization, only its test organizations have it.

Replaces GET /organizations/location/ in v4.

None
200 OK

memberships

GET
/memberships The organization's membership types, sorted by name.
Information Filters Blocks (include) Response

Requires read access in the "Users" module.

Returns id and name. The block users adds the users who have the membership: id, name, member_number and active.

Replaces GET /users/memberships/ in v4.

name (search)

limit, offset, include_total, exclude
users
200 OK
GET
/memberships/{id} One membership.
Information Parameters Response

Requires read access in the "Users" module. The same fields and block as in the list.

404 if the organization has no membership with that id.

include, exclude
200 OK

user groups

GET
/user-groups The organization's own groups of users, sorted by name.
Information Filters Blocks (include) Response

Requires read access in the "Users" module.

Returns id and name. The block users adds the users in the group: id, name, member_number and active.

Replaces GET /users/groups/ in v4.

name (search)

limit, offset, include_total, exclude
users
200 OK
GET
/user-groups/{id} One user group.
Information Parameters Response

Requires read access in the "Users" module. The same fields and block as in the list.

404 if the organization has no user group with that id.

include, exclude
200 OK

expiry dates

GET
/expiry-date-types The organization's types of expiry date, sorted by name.
Information Filters Response

Requires read access in the "Organization settings" module (organization_settings).

An expiry date type is a date the organization keeps for its members, such as a medical or a licence. On the website they are set up under Settings, Expiry dates. A member's date of a type is in the block expiry_dates of a user, where id is the type's id.

Returns id, name, may_never_expire, members_can_change, image_required, members_can_upload, booking (required, warning_only, also_for_students, excluded_object_ids), reminders (at_login, days_before) and applies_to (only, except). See POST below for what each means.

New in 5.21: applies_to, which members the type applies to.

New in v5.

name (search)

limit, offset, include_total, exclude
200 OK
GET
/expiry-date-types/{id} One expiry date type.
Information Parameters Response

Requires read access in the "Organization settings" module. The same fields as in the list.

404 if the organization has no expiry date type with that id.

exclude
200 OK
POST
/expiry-date-types Creates an expiry date type.
Information Body Response

Requires write access in the "Organization settings" module.

Only name is required. Two types of the organization cannot have the same name, in any upper or lower case: 409 with code 10030. At most 30 characters of the name are stored.

A field that is left out gets what the website's empty form gives: false, no excluded objects, reminders 30 days before the date, and a type that applies to every member.

may_never_expire: a member's date may be "never expires", written as the date 2999-12-31. members_can_change: members may change their own date on the website. image_required: a date counts as expired until an administrator has added an image (scanned copy) of it on the member card, or approved one the member sent in. members_can_upload: members may send in the image themselves on the website (My settings), and an administrator approves it before it counts; it can only be true together with image_required (otherwise 400, code 10006), and turning image_required off turns it off too.

booking.required: the date is checked when a member books; warning_only: an expired date warns instead of stopping the booking; also_for_students: the student on a booking with an instructor is checked too; excluded_object_ids: the objects (ids from GET /objects) the date is not checked for, none for every object.

reminders.at_login: the member is reminded after logging in when the date is near or has passed; days_before: how many days before the date the reminders start, 0 to 365.

New in 5.21: applies_to, which members the type applies to, by user group and membership ("Applies to" on the website). only.user_group_ids and only.membership_ids (ids from GET /user-groups and GET /memberships): the type applies only to members in one of these user groups or with one of these memberships; with only.all_must_match true the member must be in every one of the user groups and have every one of the memberships (a member has one membership, so two listed memberships match no one). except.user_group_ids and except.membership_ids: the type never applies to these members, whatever "only" says. Every list empty: the type applies to every member.

A type that does not apply to a member is not shown to the member and is not checked when the member books. A date the member has of it stays, and GET /expiry-dates, GET /users/{id}/expiry-dates and the block expiry_dates of a user list it as before.

400 with code 10006 for a user group or membership the organization does not have, and for the same one under both only and except. all_must_match is saved as false when nothing is listed under only.

The reply is the new type, with its address in the Location header.

{
  "name": text (required),
  "may_never_expire": true or false,
  "members_can_change": true or false,
  "image_required": true or false,
  "members_can_upload": true or false,
  "booking": {
    "required": true or false,
    "warning_only": true or false,
    "also_for_students": true or false,
    "excluded_object_ids": [int, int]
  },
  "reminders": {
    "at_login": true or false,
    "days_before": int (0 to 365)
  },
  "applies_to": {
    "only": {
      "user_group_ids": [int, int],
      "membership_ids": [int, int],
      "all_must_match": true or false
    },
    "except": {
      "user_group_ids": [int, int],
      "membership_ids": [int, int]
    }
  }
}

Parameters: exclude
201 Created
PATCH
/expiry-date-types/{id} Changes an expiry date type.
Information Body Response

Requires write access in the "Organization settings" module.

Only the fields that are sent are changed. None of them can be null. excluded_object_ids replaces the whole list. The name cannot be changed, as on the website.

New in 5.21: applies_to. Each of its lists that is sent replaces that whole list, and one that is not sent stays as it is; the same user group or membership under both only and except is checked with the lists as they will be stored.

Turning image_required on makes every member who has a date of the type but no image count as expired at once, as on the website. A member's 2999-12-31 date stays when may_never_expire is turned off.

The reply is the changed type. 400 with code 10105 if the body has no fields. 404 if the organization has no expiry date type with that id.

The fields of POST, without name.

Parameters: exclude
200 OK
DELETE
/expiry-date-types/{id} Deletes an expiry date type.
Information Parameters Response

Requires write access in the "Organization settings" module.

WARNING: the members' dates of the type, and their images, are deleted with it and cannot be restored.

While members have dates of the type, it is only deleted with delete_dependents=true. Without it the reply is 409 with code 10106, which says how many dates there are, and nothing is deleted. See Deleting a setting that data depends on.

The reply has no body. 404 if the organization has no expiry date type with that id.

delete_dependents (bool)
204 No Content
GET
/expiry-dates Every member's expiry dates, the earliest first.
Information Filters Response

Requires read access in the "Users" module.

The dates of the organization's members in one list, one item per date, for reports and reminders. Sorted by the date, the earliest first, then by the member's name. Only dates that exist are listed: a member who has no date of a type is not (GET /users?include=expiry_dates shows that).

Returns user (id and name), type (id and name of the expiry date type), expiry_date (2999-12-31 means "never expires"), expired (the date is before today in the organization's time zone, or the type requires an image and the date has none), image_missing (the type requires an image and the date has none), image_required, has_image (the date has an approved image) and pending_approval (the member has sent in an image that waits for an administrator to approve it).

Example: the dates that run out in November 2026: ?expiry_date_from=2026-11-01&expiry_date_to=2026-11-30. The medicals that are expired: ?type_id=12&expired=true.

New in 5.22: image_missing, and expired (also the filter) is true also when the type requires an image and the date has none, as the website judges the date at booking.

type_id (int)
user_id (int)
active (bool)
expired (bool)
expiry_date_from (date)
expiry_date_to (date)

limit, offset, include_total, exclude
200 OK
GET
/users/{id}/expiry-dates A user's expiry dates.
Information Parameters Response

Requires read access in the "Users" module.

Every expiry date type of the organization, with the user's date of it, as the member card shows them. Sorted by the name of the type.

Returns id and name of the type, expiry_date (null when the user has no date of it; 2999-12-31 means "never expires"), expired (the date is before today in the organization's time zone, or the type requires an image and the date has none; null without a date), image_missing (the type requires an image and the date has none; null without a date), image_required, has_image (the date has an approved image) and pending_approval (the member has sent in an image that waits for an administrator to approve it; it can be true without a date). expired is the date as the website judges it, for example at booking.

New in 5.22: image_missing, and expired is true also when the type requires an image and the date has none (before, expired was the date alone).

404 if the organization has no user with that id.

limit, offset, include_total, exclude
200 OK
PUT
/users/{id}/expiry-dates/{type_id} Sets a user's expiry date.
Information Body Response

Requires write access in the "Users" module.

Creates the user's date of the type, or changes it. The same as saving the date on the member card: a changed date gets its reminder emails again, and its image (scanned copy) is removed, since it proved the old date. The same date again saves nothing.

2999-12-31 means "never expires" and is only accepted when the type has may_never_expire. A date that has passed is accepted. Whether members may change the date themselves (members_can_change) does not apply here.

The reply is the user's date of the type, as GET gives it: 200 also when the date is new. To remove a date, use DELETE; null gives 400.

404 if the organization has no user or no expiry date type with that id.

{
  "expiry_date": date (required)
}

Parameters: exclude
200 OK
DELETE
/users/{id}/expiry-dates/{type_id} Removes a user's expiry date.
Information Parameters Response

Requires write access in the "Users" module.

Removes the user's date of the type, and its image, as emptying the date on the member card does.

The reply has no body. 404 if the organization has no user or no expiry date type with that id, or the user has no date of the type.

None
204 No Content

objects

GET
/objects What can be booked: the organization's own objects and the ones shared with it.
Information Filters Blocks (include) Response

Requires read access in the "Objects" module. Sorted by category, then registration.

Always returned: id, registration, category (id and name: 0 = Aircraft, 1 = Equipment, 2 = Premises, 3 = Simulator), type_designator and type_name (an aircraft's type, or the type a simulator simulates; otherwise null; both null when no type is set, which the website stores as "x"), simulator_class, comment, organization (id and name of the owner) and active.

New in 5.18: simulators, category 3, as an organization sets them up on the website. simulator_class is the simulator's class (BITD, FNPT I, FNPT II, FNPT III, FTD, FFS or Other), null when not set and for every other object. A simulator has no settings block (null, as equipment and premises): a session is logged by its start and end only.

status: total_id, maintenance_id and remarks_id (0 = OK, 1 = yellow, 2 = red) and remaining_time: what is left until maintenance on each counter (airborne, days, tachometer, tach, hobbsmeter, landings and, new in 5.17, cycles: the engine cycles of an aircraft that logs them), "soft" until it is due and "hard" until the object is grounded, null without a limit and negative when passed. settings: aircraft only, otherwise null; show_engine_cycles and force_engine_cycles (new in 5.17) say whether the aircraft logs engine cycles and whether they must be stated. maintenance_items: each item's due and hard limits, since 5.17 also due_cycles and hard_limit_cycles. time_summary.total.engine_cycles (new in 5.17): the engine's total cycles, null for an aircraft that does not log them.

status, active_remarks and time_summary are worked out the same way as on the website and take the longest to fetch, so ask only for the blocks you need.

Replaces GET /objects/ and GET /objects/status/ in v4 (use include=status for the latter).

registration (search)
type_designator (search)
category_id (int)
organization_id (int)
organization_name (search)
active (bool)

limit, offset, include_total, exclude
status
active_remarks
maintenance_items
settings
time_summary
200 OK
GET
/objects/{id} One object.
Information Parameters Response

Requires read access in the "Objects" module. The same fields and blocks as in the list.

404 if the organization neither has nor is shared an object with that id.

include, exclude
200 OK

remarks

GET
/remarks/{id} One remark on an aircraft, with everything that has happened to it.
Information Parameters Response

Requires read access in the "Objects" module. A remark on one of the organization's own objects, or on an object another organization shares with it. The webhook events remark.create and remark.update give the id (see Webhooks).

Returned: id, object (id, registration, organization), category (id, name: yellow or red, blocks_flying), ata (chapter and section, two digits each, or null), flight_id (the flight it was written with, or null), status (open, acknowledged, closed or rejected), created_at (UTC), created_by and description (from when it was written), and items: everything that has happened, oldest first, each with type (created, acknowledged, commented, closed, rejected), at (UTC), by (the member's name, null for an automatic acknowledgement) and text.

New in 5.19: images, the remark's own images (up to two, showing the fault), each with id, width and height; and on each item its id and image, the picture a comment or the closing can have (what was found or done; id, width and height, or null). The bytes of an image are GET /remarks/{id}/images/{image_id}.

404 if there is no such remark on the organization's objects.

exclude
200 OK
POST
/remarks Write a remark on one of the organization's objects.
Information Body Response

New in 5.14. Requires write access in the "Objects" module. For an integration that reports faults, such as a maintenance system or a tracker. The token's owner writes the remark, as on the website's Technical status page, through the website's own remark class, so what follows is the website's: the mail and SMS to the organization's recipients for remarks, the webhook remark.create, and the organization's automatic acknowledgement (then already in "items").

The object must be one the website's page lists for the token's owner (not hidden from maintenance): 404 otherwise. 403 with code 10331 when the organization has switched the remark function off.

201 with the remark, as GET /remarks/{id} gives it, and its address in Location.

object_id (int, required)
category_id (int, required): 1 yellow, 2 red (stops the aircraft from flying)
text (text, required)

201 Created
POST
/remarks/{id}/acknowledge Acknowledge a remark.
Information Body Response

New in 5.14. Requires write access in the "Objects" module. The token's owner acknowledges the remark, as on the website: only a mechanic or an administrator may (403 with code 10332), and only an open remark that is not yet acknowledged (409 with code 10333). The webhook remark.update follows.

200 with the remark as it is afterwards; 404 if there is no such remark on the organization's objects.

None
200 OK
POST
/remarks/{id}/comment Comment on a remark.
Information Body Response

New in 5.14. Requires write access in the "Objects" module. As on the website: a mechanic, an administrator or the member who wrote the remark may (403 with code 10332), once the remark is acknowledged and until it is closed (409 with code 10333). The webhook remark.update follows.

200 with the remark as it is afterwards.

text (text, required)
200 OK
POST
/remarks/{id}/close Close a remark.
Information Body Response

New in 5.14. Requires write access in the "Objects" module. As on the website: only a mechanic or an administrator may (403 with code 10332), once the remark is acknowledged and only once (409 with code 10333). The organization's recipients for remarks get the website's mail, and the webhook remark.update follows.

200 with the remark as it is afterwards.

text (text, optional): a closing text. The body may be left out.
200 OK
POST
/remarks/{id}/images Add an image to a remark, or to one of its comments.
Information Body Response

New in 5.19. Right: objects:w. One more image on the remark, as the website's Technical status page keeps them: the body is multipart/form-data with the part file (a JPEG, PNG, GIF or WebP of at most 20 MB and 25 million pixels), which the server scales to 1600 pixels on the long side and keeps as a JPEG.

Without item_id the image is one of the remark's own, up to two, showing the fault: the member who wrote the remark, a mechanic or an administrator may add it (403 with code 10337), until the remark is closed (409 with code 10338). With item_id, the id of a comment or of the closing in the remark's items, the image is that item's, one each, showing what was found or done: the one who wrote the item, a mechanic or an administrator may add it (403 with code 10337). A comment's image can be added only until the remark is closed; the closing text's image for 24 hours after the closing. Otherwise 409 with code 10338.

Returned: 201 with the remark as it is afterwards (the new image in images, or in image of the item), a Location header with the image's address and "meta.image_id". 409 with code 10339 when the remark has two images or the item has one, 409 with code 10340 for the same picture again on the remark, 400 with code 10341 for a file that is no image. The webhook remark.update with change "images" follows.

multipart/form-data: the part file (required); the field item_id (int, optional): the comment or the closing the image is for
201 Created
GET
/remarks/{id}/images/{image_id} An image of a remark.
Information Parameters Response

New in 5.19. Right: objects:r. The image, a JPEG (the large copy, at most 1600 pixels on the long side), with an ETag: one of the remark's own images or the image of one of its items, by the id the remark gives. 404 for a remark you do not see or an image that is not on this remark.

None
200 OK
DELETE
/remarks/{id}/images/{image_id} Remove an image of a remark.
Information Body Response

New in 5.19. Right: objects:w. Removes the image from the remark; the website keeps it, marked deleted, as part of the aircraft's technical record, so it no longer appears in the remark and GET of it answers 404. Who may is the same as for adding it: 403 with code 10337, and 409 with code 10338 once the remark is closed, except for the closing text's image within 24 hours after the closing. The webhook remark.update with change "images" follows.

204, also when the image is gone already or is not on this remark.

None
204 No Content

bookings

GET
/bookings Bookings of the organization's own objects and of the objects shared with it, sorted by start time.
Information Filters Response

Requires read access in the "Bookings" module.

Returned: id, start_at and end_at (UTC), start_local and end_local (the time at the object's organization, with its offset from UTC), timezone, object (id, registration, type_designator (null when no type is set, which the website stores as "x"), category, organization), user (the booker: id, name, email, mobile), student (the same, or null), type, booking_type (new in 5.16, see below), is_primary, expected_airborne, comment and reminders (email, sms: the booking page's two boxes, a reminder by email and by SMS the day before).

"booking_type" (new in 5.16) is the organization's booking type the booking is shown with: id, name, description, is_standard, color, color_light and color_dark. An organization names its own booking types on the website ("Fire watch", "Glider tow"), each built on one of the types in "type", which keeps its rules; every organization starts with one standard type of each. A standard type the organization has not renamed gets the website's name and description in the language of Accept-Language. "color" is the palette colour the organization chose (teal, sky, indigo, lavender, pink, coral, amber, lime, olive, brown, slate, cyan, blue, green, red, orange or purple), with its hex value for a light and for a dark background in color_light and color_dark, dark enough for white text; null when the type has the standard colours of its type, which a client then draws as before. The colour is the same for the booker and for other members: mark the member's own bookings as today. null for a booking without one.

The email and mobile number follow each member's own settings, the same as in the booking calendar. A value the member has chosen not to show is null.

date_from and date_to are local dates: a booking is returned if it ends on or after date_from and starts on or before date_to.

Replaces GET /bookings/ in v4.

date_from (date)
date_to (date)
object_id (int)
object_registration (search)
object_organization_id (int)
object_category_id (int)
user_id (int)
user_name (search)
student_id (int)
student_name (search)
is_primary (bool)

limit, offset, include_total, exclude
200 OK
GET
/bookings/{id} One booking.
Information Parameters Response

Requires read access in the "Bookings" module. The same fields as in the list.

404 if there is no such booking of the organization's objects.

exclude
200 OK
POST
/bookings Books an object for a member, by the website's booking rules.
Information Body Response

Requires write access in the "Bookings" module. New in v5.

Made through the website's booking class, as the token's owner (an administrator) books on the booking page: the same rules (types, overlaps, the queue, lengths, the member's balance and expiry dates) and the same mails to the members. Service bookings and instructor duties are made on the website.

The reply is 201 with the booking as GET gives it, a Location header with its address, and "meta": { "messages": [...] }: what the website would show after the booking, each as { "kind": "info", "text": "..." }, in the language of the Accept-Language header (sv, en, nb or da; English when left out).

When a booking rule stops it, the reply is 409 with code 10300 and the rule's text in "errors". 403 with code 10301 when the organization has switched booking off.

object_id (int), start_at, end_at, owner_id (int, the member the booking is for, from GET /users): required. The times are points in time with their offset or Z; the booking is made in the organization's time zone.

comment (text), expected_airborne (hours, where the organization uses it) and seats_left (int, free seats offered to others): optional.

type (text): PRIV (the default), SCHOOL (owner_id is the instructor; student_id is required: a member's id, or -1 for a student who is not a member) or SCHOOL_L (owner_id is the student; instructor_id is required).

booking_type_id (int, new in 5.16): one of the organization's booking types built on the type, as GET /bookings gives them in booking_type. Left out, the booking gets the organization's standard type of its type. One that is not built on the type, is not offered to the token's owner or belongs to another organization gives 409 with the rule's text; 0 or null gives 400.

reminders: optional, { "email": true, "sms": false }. A box that is left out is ticked as the owner has it in My settings, as the booking page does (SMS only when the organization offers SMS reminders). "sms": true when the organization does not offer them gives 400. When the owner has SMS reminders off in My settings, the box is stored but no SMS is sent until they switch them on; "meta.messages" then says so.

201 Created
PATCH
/bookings/{id} Changes the times, the object, the comment or the reminders of a booking.
Information Body Response

Requires write access in the "Bookings" module. New in v5.

Changed through the website's booking class, with the same rules as when an administrator changes the booking on the booking page, and the members get the website's "booking changed" mail. A field that is not sent keeps its value. The type and the people of a booking cannot be changed, but its booking type can (booking_type_id, new in 5.16).

Only private and school bookings can be changed here: 409 with code 10320 for a service booking or an instructor duty. 403 with code 10309 when the website does not let the token's owner change the booking.

A change that puts the booking last in a queue behind another booking gives 409 with code 10303, with the bookings ahead in "errors". Send the same change again with "queue_confirmed": true to go ahead, as the booking page asks for a confirmation. The booking then moves to a new row, last in the queue, and gets a new id: use "data.id" of the reply, as the old id is gone.

200 with the booking as it is afterwards and "meta.messages"; 409 with code 10300 when a rule stops it; 404 when there is no such booking of the organization's objects; 400 with code 10105 for an empty body.

object_id (int), start_at, end_at: as in POST.

comment (text), expected_airborne (hours), seats_left (int): null empties them.

reminders: { "email": true, "sms": true }; a box that is left out keeps its value. "sms" follows the same rules as in POST.

booking_type_id (int, new in 5.16): one of the organization's booking types built on the booking's type; left out, the booking keeps its own.

queue_confirmed (bool): agree to the booking being placed last in the queue.

200 OK
POST
/bookings/{id}/cut Ends a booking that is going on, now.
Information Body Response

Requires write access in the "Bookings" module. New in v5.

Ended through the website's booking class, as "End now" on the booking page. The token's owner is an administrator and may end any booking of the organization's objects; 403 with code 10308 when the website does not allow it. A booking that is not going on gives 409 with code 10300 and the class's text.

200 with the booking as it is afterwards and "meta.messages"; 409 with code 10300 when a rule stops it; 404 when there is no such booking of the organization's objects.

No body.

200 OK
POST
/bookings/{id}/cancel Cancels a booking.
Information Body Response

Requires write access in the "Bookings" module. New in v5.

Cancelled through the website's booking class, with the same rules as when an administrator cancels the booking on the booking page, and the members get the website's cancellation mail.

200 with the booking as it was, since it is gone afterwards, and "meta.messages"; 409 with code 10300 when a rule stops it (also when the organization requires a reason and none was sent); 404 when there is no such booking of the organization's objects.

reason (text): why the booking is cancelled. Required when the organization requires a reason. The body may be left out.

200 OK

flightlogs

GET
/flightlogs The flights logged on the organization's own objects and on the objects shared with it, oldest first (order=desc for newest first).
Information Filters Response

Requires read access in the "Logbook" module (flightlogs).

Returned: id, date, object, flight_type, departure (airport, blockoff_at, takeoff_at, tachometer, hobbs), via_route, arrival (airport, landing_at, blockon_at, tachometer, hobbs), crew_hidden, pilot, instructor and scout (each with id, name, member_number and organization, or null), is_solo_instruction, uplift (fuel, oil), fuel_onboard (litres on board before the flight, or null), totals (block, airborne, tach and hobbs, each in hours and in minutes), number_of_flights, engine_cycles (new in 5.17: the engine cycles of the flight, for an aircraft that logs them, or null), daily_check, comment, transaction_id, remark_id and created_at.

New in 5.18: object.category (id and name, as in GET /objects) and is_simulator, true for a session on a simulator. A session has its start, end and session time in departure.blockoff_at, arrival.blockon_at and totals.block, and no airports, take-off, landing, meter readings or uplift. The filter simulator=true gives only the sessions, simulator=false only the other flights. remark_id is the flight's first remark; since 5.18 a flight with several remarks is given once (before, once per remark).

Clock times: date, blockoff_at, takeoff_at, landing_at and blockon_at are the logbook's own clock times written with a Z. For most organizations that is local time at each airport, not UTC; the Z is only part of the format. A clock time that is earlier than the one before it is on the day after the date. Earlier versions of this page said "All times are UTC": the text was wrong and is corrected in 5.23. The values are as they have always been.

New in 5.23: clock_times, the rule of the logbook the flight is in ("local" = local time at each airport, or "utc"; the logbook is that of the organization that owns the object). In departure and in arrival: time_zone (a logbook in local time: the IANA zone the end's clock times are in, the airport's, else the organization's home zone; a logbook in UTC: the airport's own zone, null when it is not known) and utc_offset (that zone's minutes east of UTC at the end's first clock time, 120 for UTC+2; null without a clock time or a zone). The true points in time in UTC are departure.blockoff_utc, departure.takeoff_utc, arrival.landing_utc and arrival.blockon_utc, null where the flight has no such time (also for a stored 00:00 that is not a time: off block and on block both 00:00, or take-off and landing both 00:00).

Example: a flight logged 14:00 at Stockholm Bromma and 16:30 at Mariehamn on 2026-07-01, in a logbook in local time, has blockoff_at "2026-07-01T14:00:00Z" with time_zone "Europe/Stockholm", utc_offset 120 and blockoff_utc "2026-07-01T12:00:00Z", and blockon_at "2026-07-01T16:30:00Z" with time_zone "Europe/Mariehamn", utc_offset 180 and blockon_utc "2026-07-01T13:30:00Z". The block time is 1:30. In a logbook in UTC the same flight has clock_times "utc", the ..._at fields equal to the ..._utc fields, and the same zones and offsets.

The four ..._at fields are deprecated in favour of the ..._utc fields with time_zone. They keep their meaning for all of version 5. Until the website opens the logbook's clock to every organization, only its test organizations have the new fields; the flights of every other organization are given exactly as before. clock_times cannot be named in exclude.

is_solo_instruction is true for a student's solo flight, false for a flight that is not one, and null when it was not filled in. (v4 gave the stored codes "EK" and "DK" in instruction.is_solo.)

Which flights: every flight on the organization's own objects and on the objects other organizations share with it, whoever logged it, as the website's journey log shows them. The shared objects are new in 5.15 (before, and in v4, only the own objects). object.organization is the object's owner, so the filters object_organization_id and object_organization_name pick the own or the shared objects. When a share hides the object's log from the organization it is shared with, that object's flights are left out. The journey log's empty rows (blank lines in an object's log, kept for the running row numbers) are not flights and are not given (since 5.15.1; GET /flightlogs/{id} gives 404 for one).

When the organization hides the pilot in the log (integrity setting), crew_hidden is true and pilot, instructor and scout are null, also on the shared objects (since 5.15), as on the website. On a shared object the crew is also hidden when the object's owner hides it. The pilot, instructor and scout filters never match such flights, and has_instructor treats them as flights without an instructor.

The order is by date, then block off, takeoff and id: oldest first, or, with order=desc (new in 5.13), newest first. Any other value of order gives 400 (code 10005).

Replaces GET /flightlogs/ in v4.

date_from (date)
date_to (date)
object_id (int)
object_registration (search)
object_organization_id (int)
object_organization_name (search)
departure_icao (search)
arrival_icao (search)
pilot_id (int)
pilot_name (search)
pilot_member_number (search)
instructor_id (int)
instructor_name (search)
instructor_member_number (search)
has_instructor (bool)
scout_id (int)
scout_name (search)
scout_member_number (search)
has_remark (bool)
remark_id (int)
order (asc or desc)

limit, offset, include_total, exclude
200 OK
GET
/flightlogs/{id} One logged flight.
Information Parameters Response

Requires read access in the "Logbook" module (flightlogs). The same fields as in the list.

404 if there is no such flight on the organization's own objects or the objects shared with it (the shared ones since 5.15).

exclude
200 OK
GET
/flightlog-options For logging a flight: who the token owner may log for, the objects they may log on, and the flight types the pilot may use.
Information Parameters Response

Requires read access in the "Logbook" module (flightlogs). New in v5: the four endpoints below log a flight through the website's own engine, so the rules, the checks and the price are those of the Log flight page.

Returned: pilot (id, name, member_number), may_log_for_others (always true for a token, since its owner is an administrator), pilots (the members the token owner may log for), objects (id, registration, model (null when no type is set, which the website stores as "x"), shared, organization, and flight_types: the types the pilot may use on it, each with id, name and admin_only), instructors and scouts (the members that can be given as instructor_id and scout_id). The two choices that are not members, "no scout" (999999999) and "not in the list" (999999998), have "special" set and no name.

New in 5.23.1 (Main) and 5.42.1 (Mobile): each object has clock_times, "local" or "utc": the clock rule of the organization that owns the object, which is the rule a flight on it is stored in (for a shared object the owner's, not the caller's). null when the owner does not have the clock feature yet. Read it before the flight is logged to mark the time fields "LCL" or "UTC" and to know whether a total is to be calculated across zones; see clock_times in POST /flightlogs.

admin_only is true for a flight type the pilot may not use themselves; an administrator may still log it on the pilot's behalf.

403 (code 11005) if the organization has switched the flight log off. 400 (code 11003 at pilot_id) if the pilot is not a member.

pilot_id (int, required)
200 OK
GET
/flightlog-form Which fields of the POST /flightlogs body are used and required for one object, flight type and pilot.
Information Parameters Response

Requires read access in the "Logbook" module (flightlogs).

Returned: object (id, registration, model (null when no type is set, which the website stores as "x")), flight_type (id, name), flight_types (the types the pilot may use on the object), fields, required_one_of, charge_visible and instructions (the organization's own text on the Log flight page).

"fields" has one entry for every field the POST /flightlogs body takes, by its name, always with "used" and "required". A field with used=false is ignored if sent. Where it applies there is also: type ("decimal" with "decimals" 1 or 2, "hh:mm", or "hours" for a typed total), unit, suggested (a value to fill in; with locked=true the value must be the suggested one, e.g. tach out = the object's last tach in), max (number_of_flights: the organization's maximum, null when it has set none), max_items (via), max_length (comment), choices (tow_object_id, tow_height_id), categories and blocking_allowed (remark; the names in the language of Accept-Language), and booking (cut_booking_id: the booking of the object that is going on, which must be kept or ended).

"required_one_of" lists the rules where one of several groups of fields must be complete, each with the code POST /flightlogs answers when none is: the block or airborne time as two clock times or a typed total (11030), and towing by time or by height (11044).

"No tow": where the object's tow price list offers it, the choices of tow_object_id end with one that has none = true (registration null), for a glider that launches by itself. Sent as tow_object_id, no tow time or tow height is needed and no towing is charged. The towing rule is then left out of required_one_of.

What the form cannot tell: rules that depend on the values (a reading lower than the last, the lock dates, a flight logged already, the price) are only found by POST /flightlogs/preview. The usual flow is: read the form, fill it in, preview, save.

404 if the organization does not log flights on the object. 400 with code 11002 for a flight type the organization does not have, and 11003 for a pilot who is not a member.

object_id (int, required)
flight_type_id (int, required)
pilot_id (int, required)

Header Accept-Language: sv, en, nb or da (English when left out)
200 OK
POST
/flightlogs/preview Checks a flight and gives its price, without saving it.
Information Body Response

Requires write access in the "Logbook" module (flightlogs). The same body and the same checks as POST /flightlogs; nothing is saved.

Returned: object, flight_type, pilot, charged_member (the member who pays: the pilot, or the member the flight type is charged to), date, totals (block, airborne, tach, hobbs and tow in hours, as the engine worked them out), charge_visible and charge. "charge" is the receipt: currency, charged_member, transaction_date, rows (kind: time, tow, correction, rounding or floor; text, quantity, unit, unit_price, percent, amount), subtotal, rounding, zero_floor, total and vat. It is null when the organization hides the amounts from the member. "meta.warnings" has the rules an administrator may break that this flight breaks (see POST /flightlogs).

Show the member the total and send it as confirmed_total with POST /flightlogs: the flight is then only saved when the price is still the same.

The errors are those of POST /flightlogs: 400 (code 11000) with every problem, 409 (code 11050) for a flight that is logged already, when that is the only problem.

See POST /flightlogs.
200 OK
POST
/flightlogs Logs a flight on one of the organization's objects and charges the member.
Information Body Response

Requires write access in the "Logbook" module (flightlogs). The flight is logged by the token owner, an administrator, for any member: the same rules, checks and price as when the administrator logs it on the Log flight page, the same transaction and the same mail. The rules an administrator may break (more flights than the organization's maximum, an unreasonable ratio between the times, a flight that looks logged already, an amount above the limit) do not stop the entry; they are reported in "meta.warnings".

Which fields are used and required depends on the object, the flight type and the pilot: ask GET /flightlog-form first. The clock times are written as points in time with Z, on the flight's date (or the day after, for a flight that passes midnight); they are the logbook's own clock times unless clock_times says otherwise (see below). The block and airborne times can be given as two clock times or as a typed total in hours. A meter reading (tach, hobbs) is a number with the object's decimals, or hours and minutes as text ("1234:30") for an object that counts them so. "remark" makes a remark on the object with the flight, "remarks" (new in 5.18) several, at most the form's fields.remark.max_count; "cut_booking_id" ends the booking that is going on (0 keeps it); "pfly" is for organizations in Norway. Accept-Language picks the language of the transaction's rows and the mail.

New in 5.18: a simulator (object category 3; is_simulator in GET /flightlog-options and in the form's object) is logged here too, as a session. Its form uses only date, the crew (no solo, no scout), blockoff_at (the session's start), blockon_at (its end) or total_block (the session time, with "label" in the form), comment, remark or remarks and cut_booking_id; the airport, flight, meter, uplift, towing and PFLY fields are not used.

Clock times: without clock_times, date and the clock times are the logbook's own clock times, local time at each airport unless the organization logs in UTC (GET /organization, logbook.clock_times). They are stored as sent: the hour and the minute count, the Z is only part of the format. Earlier versions of this page said "in UTC": the text is corrected in 5.23, and nothing in how a body is read or stored has changed.

New in 5.23: clock_times says how date and the clock times of the body are to be read. "local": local time at each airport, and date is the local date of the block off; stored as sent in a logbook in local time, converted to UTC in a logbook in UTC (the Z is ignored). "utc": true points in time in UTC, and date is the UTC date; stored as sent in a logbook in UTC, converted to the local time at each airport, on the local date of the block off, in a logbook in local time (the Z is meant). The rule is that of the organization that owns the object. clock_times is never saved with the flight. Any other value gives 400 (code 10006, "Must be utc or local"). A local time that has to be converted and does not exist on that date at its airport (the hour skipped when summer time starts) gives 400 with code 11000 and the error 11090 at the field; a time the clock shows twice is the first of the two. Until the website opens the logbook's clock to every organization, only its test organizations can send clock_times: 400 (code 10006, "Not open to this organization yet") for an object of another organization.

In an organization that has the logbook's clock, a total that is not sent is worked out as the time that passed, also between two time zones (before, it was the difference between the two clock times), and "A flight can not be logged in the future" (11013) compares the landing and the block on as points in time in the logbook's rule, with two hours of slack.

Returned: 201 with the flight as GET /flightlogs/{id} gives it, a Location header, and "meta": transaction_id, balance_after (the charged member's balance; null when the amounts are hidden), charge (as the preview gives it), warnings and remark_ids.

New in 5.20: remark_ids, the id of each remark sent with the flight (remarks, or remark), in the order sent; null for a remark that could not be saved, which also gives the warning 11064; empty when no remark was sent. To add photos to a remark written with the flight, log the flight first, then call POST /remarks/{id}/images once per photo with these ids.

400 with code 11000 when the engine finds problems: "errors" has every problem with its field, its own code (11001-11049) and a message, and "warnings" the rules an administrator may break that are also broken, so everything can be corrected in one round. 409 with code 11051 when the price has changed since confirmed_total was shown (the new price in "charge"). A 409 is only given when that is the only problem; with other problems the code is one of the errors of a 400. 403 with code 11005 when the organization has switched the flight log off. 500 with code 11060 when the flight could not be saved; nothing is saved then.

object_id (int, required)
flight_type_id (int, required)
pilot_id (int, required)
instructor_id (int), is_solo_instruction (bool), scout_id (int)
date (YYYY-MM-DD, required)
clock_times ("utc" or "local", new in 5.23)
departure_icao, arrival_icao (text), via (list of text, at most 5)
number_of_flights (int), distance (number)
blockoff_at, blockon_at (datetime), total_block (hours)
takeoff_at, landing_at (datetime), total_airborne (hours)
tach_out, tach_in, hobbs_out, hobbs_in (reading)
tow_object_id (int), tow_landing_at (datetime), total_tow (hours), tow_height_id (int), tow_height_value (number)
fuel_uplift, oil_uplift, fuel_onboard (number), engine_cycles (int, 0-99, new in 5.17; for an aircraft that logs engine cycles, required when the form says so), daily_check (bool)
comment (text, at most 200)
remark {text, category_id, ata_main_code_id, ata_sub_code_id}
remarks [{text, category_id, ata_main_code_id, ata_sub_code_id}, ...] (new in 5.18; used instead of remark when both are sent)
cut_booking_id (int)
pfly {used, blind_transmission, overfly, closed_flight_plan}
confirmed_total (decimal)

Header Accept-Language: sv, en, nb or da
201 Created
GET
/flight-types The organization's flight types, sorted by name.
Information Parameters Response

Requires read access in the "Logbook" module (flightlogs).

Returns id and name.

409 (code 10200) if the organization does not use the flight log.

Replaces GET /flightlogs/flighttypes/ in v4.

limit, offset, include_total, exclude
200 OK
GET
/users/{id}/approved-flight-types The flight types a user may log, per object.
Information Parameters Response

Requires read access in the "Logbook" module (flightlogs).

Returns the objects the user may log flights on. Each item has object (id, registration) and flight_types (a list of id and name). The rules are the same as when the member logs a flight on the website.

404 if the organization has no user with that id. 409 (code 10200) if the organization does not use the flight log.

Replaces GET /flightlogs/flighttypes/approved/?user_id= in v4.

limit, offset, include_total, exclude
200 OK

transactions

GET
/transactions What has been charged to and paid into the members' accounts, newest first.
Information Filters Blocks (include) Response

Requires read access in the "Economy" module (transactions).

Returned: id, date, user (id, name, external_customer_number), flightlog_id, amount, comment and created_at (UTC). A negative amount is a charge, a positive amount a payment.

The block details shows the transaction as the website's transaction details do: first the transaction itself (its comment up to a "#", and what is left of its amount after the parts), then each part, such as towing, a landing fee or rounding, each with description and amount. The amounts have the transaction's sign, so a charge's rows are negative, and they add up to the transaction's amount. An empty list when the transaction has no parts.

account_rows and account_summary show how the transaction is booked. account_rows has one row per part of the transaction: account, description, debit, credit, cost_center, project. account_summary has one sum per account, cost center and project. An account number is always text.

Replaces GET /transactions/ in v4. include_account_rows and include_account_summary are replaced by the blocks.

user_id (int)
user_name (search)
date (date)
date_from (date)
date_to (date)
amount (decimal)
comment (search)
external_customer_number (search)

limit, offset, include_total, exclude
details
account_rows
account_summary
200 OK
GET
/transactions/{id} One transaction.
Information Parameters Response

Requires read access in the "Economy" module (transactions). The same fields and blocks as in the list.

404 if the organization has no transaction with that id.

include, exclude
200 OK
POST
/transactions Creates a transaction on a member's account.
Information Body Response

Requires write access in the "Economy" module (transactions).

"amount" is the change of the member's account: negative for a charge, positive for a payment. It is a number with at most two decimals, not 0, from -100000 to 100000.

"date" must not be in the future, and not before the organization's transaction lock date.

"accounting" is optional and books the transaction on one debit account and one credit account, with a cost center and a project. They must be among the organization's own. An account number is text. "accounting.amount" can repeat the amount without its sign, as a check.

The reply is the new transaction, as GET /transactions/{id} gives it, and takes the same include and exclude parameters. The Location header has its address.

409 with code 10150 if the date is before the lock date. 409 with code 10130 if the user already has a transaction with the same date, amount and comment: it is taken for the same transaction sent twice.

Replaces POST /transactions/ in v4. Changed: "accounting.debit" and "accounting.credit" are now "debit_account" and "credit_account", and are text; the amount must be a number; a date is written YYYY-MM-DD; the reply is 201 with one transaction.

{
  "user_id": number*,
  "date": date*,
  "amount": number*,
  "comment": text*,
  "accounting": {
    "amount": number,
    "debit_account": text (digits),
    "credit_account": text (digits),
    "cost_center": text,
    "project": text
  }
}

* required

Parameters: include, exclude
201 Created

log

GET
/logs The organization's log, newest first.
Information Filters Response

Requires read access in the "Log" module.

What happened in the organization, the same rows as the Log page on the website: bookings, members, economy, objects, the aircraft logbook, files, messages, the calendar, settings, integrations and the member sync. Without date_from, date_to and since_id the list covers the last 30 days.

Returns id, created_at (UTC), category, action (a code such as booking.changed, member.rights_changed or economy.transaction_reversed), description (the English text of the action), important, object (id and registration, or null), member (id and name, or null: the member the row is about), item_id (the booking, flight, transaction or file the row is about; its kind follows the action), summary, details and done_by (user_id, name, source and integration: the name of the API token when source is api). The IP address is never returned.

details holds what only some actions have. changes gives each changed field as [before, after]; fields names changed personal fields whose values are not logged; reason, count, start, end and type are common. Times in details are the organization's local times ("2026-10-14 10:00"), as on the website. An empty object when the action has no details. Leave it out with ?exclude=details when only the list matters.

category is one or more of booking, member, economy, object, logbook, files, messages, calendar, settings, integration, sync and other, separated by commas. action takes one or more action codes the same way; an unknown name gives 400. source is web, app, api or system. important=true gives only the rows marked important: deletions, reversals, rights, payment settings and API tokens.

To follow the log, ask with since_id set to the largest id seen so far: each row then comes once, oldest first, with no 30-day limit. The dates are the organization's local dates, both days included.

Example: what one booking has been through: ?item_id=812334&category=booking. Everything an integration did this month: ?source=api&date_from=2026-10-01.

New in v5, not in v4.

date_from (date)
date_to (date)
category (text)
action (text)
object_id (int)
user_id (int)
actor_id (int)
item_id (int)
source (text)
important (bool)
since_id (int)

limit, offset, include_total, exclude
200 OK
GET
/logs/{id} One log row.
Information Parameters Response

Requires read access in the "Log" module. The same fields as in the list.

404 if the organization has no log row with that id.

exclude
200 OK

login checks

POST
/login-checks Checks a member's username and password.
Information Body Response

Requires read access in the "Login check" module (login_checks).

A simple login check for an organization's own website. It tells whether the username and the password are the login of an active member of the organization.

The reply is 200 both when the login is right and when it is wrong. "valid" says which: {"valid": true, "user": {...}} with the member's id, username, name, first_name, last_name_particle and last_name, or {"valid": false, "user": null}. 401 only ever concerns the token.

The check counts in the website's own limit on failed logins. After too many wrong passwords for a username the reply is 429 with code 10012, and the Retry-After header says how many seconds to wait.

Replaces POST /logincheck/ in v4, which answered 401 for a wrong login.

{
  "username": text*,
  "password": text*
}

* required
200 OK

Examples

GET objects request

https://api.myweblog.se/main/v5/objects?registration=SE-ABC&include=status

GET objects reply

{
  "data": [
    {
      "id": 24,
      "registration": "SE-ABC",
      "category": { "id": 0, "name": "Aircraft" },
      "type_designator": "C172",
      "type_name": "CESSNA 172",
      "comment": "Årsmodell 2002",
      "organization": { "id": 3, "name": "Svanshalls FK" },
      "active": true,
      "status": {
        "total_id": 1,
        "maintenance_id": 1,
        "remarks_id": 0,
        "remaining_time": {
          "soft_airborne": 12.5,
          "soft_airborne_formatted": "12:30",
          "hard_airborne": 22.5,
          "hard_airborne_formatted": "22:30",
          "soft_days": 45,
          "hard_days": 60,
          "soft_tachometer": null,
          "soft_tachometer_formatted": null,
          "hard_tachometer": null,
          "hard_tachometer_formatted": null,
          "soft_tach": null,
          "soft_tach_formatted": null,
          "hard_tach": null,
          "hard_tach_formatted": null,
          "soft_hobbsmeter": null,
          "soft_hobbsmeter_formatted": null,
          "hard_hobbsmeter": null,
          "hard_hobbsmeter_formatted": null,
          "soft_landings": null,
          "hard_landings": null,
          "soft_cycles": null,
          "hard_cycles": null
        }
      }
    }
  ],
  "meta": { "count": 1, "limit": 100, "offset": 0, "has_more": false },
  "links": { "next": null }
}

Linux/Mac cURL Requests

## Fetch an access token (OAuth 2.0). {client_id} is the token's Client ID on the website, {my_auth_token} is the token.
curl -u "{client_id}:{my_auth_token}" \
  -d "grant_type=client_credentials" \
  "https://api.myweblog.se/main/v5/oauth/token"
## {"access_token":"mwlat_...","token_type":"Bearer","expires_in":3600,"scope":"users:rw transactions:r"}

## Check that the access token works. Until 2027-12-31 the token itself can be sent instead.
curl "https://api.myweblog.se/main/v5/token" \
  -H "Authorization: Bearer {access_token}"

## Fetch the active users, with their email addresses and phone numbers
curl "https://api.myweblog.se/main/v5/users?active=true&include=email,phone" \
  -H "Authorization: Bearer {access_token}" \
  -H "Request-Id: {my_request_id}"

## Fetch the transactions of January 2026, with how they are booked. Follow "links.next" for the next page.
curl "https://api.myweblog.se/main/v5/transactions?date_from=2026-01-01&date_to=2026-01-31&include=account_rows" \
  -H "Authorization: Bearer {access_token}" \
  -H "Request-Id: {my_request_id}"

## Fetch the flights of January 2026, without the uplift and the totals
curl "https://api.myweblog.se/main/v5/flightlogs?date_from=2026-01-01&date_to=2026-01-31&exclude=uplift,totals" \
  -H "Authorization: Bearer {access_token}" \
  -H "Request-Id: {my_request_id}"

## Charge a member's account with 500.00, booked on two accounts. The reply is 201 with the new transaction.
curl -X POST "https://api.myweblog.se/main/v5/transactions" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer {access_token}" \
  -H "Request-Id: {my_request_id}" \
  -d '{
    "user_id": 987654321,
    "date": "2026-01-29",
    "amount": -500.00,
    "comment": "Test transaction via cURL",
    "accounting": {
      "amount": 500.00,
      "debit_account": "3011",
      "credit_account": "1910"
    }
  }'

## Make a user inactive and change the access card number
curl -X PATCH "https://api.myweblog.se/main/v5/users/987654321" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer {access_token}" \
  -d '{"active": false, "access_card": {"number": "987654321"}}'

Reply when a transaction is sent twice

{
  "type": "https://api.myweblog.se/errors/conflict",
  "title": "Duplicate transaction: the user already has one with this date, amount and comment",
  "status": 409,
  "code": 10130,
  "request_id": "b7e2c41a9d0f3e55"
}

Reply when fields of a body are wrong

{
  "type": "https://api.myweblog.se/errors/validation",
  "title": "The request has invalid fields",
  "status": 400,
  "code": 10006,
  "request_id": "b7e2c41a9d0f3e55",
  "errors": [
    { "field": "membership_id", "code": 10006, "message": "Unknown membership" },
    { "field": "email[1]", "code": 10006, "message": "Not a valid email address" },
    { "field": "phone.mobile.number", "code": 10006, "message": "Must be text with digits only" }
  ]
}

GET logs reply (one row)

{
  "id": 1045332,
  "created_at": "2026-10-13T12:22:04Z",
  "category": "booking",
  "action": "booking.changed",
  "description": "Booking changed",
  "important": false,
  "object": { "id": 24, "registration": "SE-KXA" },
  "member": { "id": 3311, "name": "Anna Berg (112)" },
  "item_id": 812334,
  "summary": null,
  "details": {
    "start": "2026-10-14 10:00",
    "end": "2026-10-14 13:00",
    "type": "PRIV",
    "changes": { "end": ["2026-10-14 12:00", "2026-10-14 13:00"] }
  },
  "done_by": { "user_id": 17, "name": "Carl Lind", "source": "api", "integration": "Club calendar sync" }
}

PHP cURL Request

// The bookings of one object in October 2026
$address = 'https://api.myweblog.se/main/v5/bookings?object_id=24&date_from=2026-10-01&date_to=2026-10-31';

$headers = [
  'Authorization: Bearer {access_token}',
  'Request-Id: {my_request_id}'
];

$curl = curl_init();
curl_setopt($curl, CURLOPT_URL, $address);
curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
curl_setopt($curl, CURLOPT_HTTPHEADER, $headers);

$response = curl_exec($curl);
$response_code = curl_getinfo($curl, CURLINFO_HTTP_CODE);

// 200: the bookings are in "data". Anything else: the reason is in "title".
$reply = json_decode($response, true);
var_dump($response_code);
var_dump($reply);

Log a flight (cURL): the form, the preview, the entry

## 1. Which fields the body uses and requires for this object, flight type and pilot
curl "https://api.myweblog.se/main/v5/flightlog-form?object_id=412&flight_type_id=7&pilot_id=22583" -H "Authorization: Bearer {access_token}"

## 2. The price, without saving
curl -X POST "https://api.myweblog.se/main/v5/flightlogs/preview" -H "Content-Type: application/json" -H "Authorization: Bearer {access_token}" -H "Accept-Language: sv" \
  -d '{ "object_id": 412, "flight_type_id": 7, "pilot_id": 22583, "date": "2026-10-08",
      "departure_icao": "ESSB", "arrival_icao": "ESKN",
      "blockoff_at": "2026-10-08T10:05:00Z", "blockon_at": "2026-10-08T11:20:00Z",
      "tach_out": 1234.5, "tach_in": 1235.7, "number_of_flights": 1,
      "fuel_uplift": 42, "oil_uplift": 0, "daily_check": true, "comment": "Touch and go x3" }'

## 3. The entry, with the total the member saw. 201 with the flight; 409 (11051) if the price has changed since.
curl -X POST "https://api.myweblog.se/main/v5/flightlogs" -H "Content-Type: application/json" -H "Authorization: Bearer {access_token}" -H "Accept-Language: sv" \
  -d '{ ...the same body..., "confirmed_total": 1488.00 }'

GET flightlog-form reply (shortened)

{
  "data": {
    "object": { "id": 412, "registration": "SE-ABC", "model": "C172" }, "flight_type": { "id": 7, "name": "PRIVAT" },
    "flight_types": [ { "id": 7, "name": "PRIVAT", "admin_only": false }, { "id": 8, "name": "SKOLA", "admin_only": false } ],
    "fields": {
      "object_id": { "used": true, "required": true }, "flight_type_id": { "used": true, "required": true }, "pilot_id": { "used": true, "required": true },
      "instructor_id": { "used": false, "required": false }, "is_solo_instruction": { "used": false, "required": false }, "scout_id": { "used": false, "required": false },
      "date": { "used": true, "required": true },
      "departure_icao": { "used": true, "required": true, "suggested": "ESSB" }, "arrival_icao": { "used": true, "required": true }, "via": { "used": true, "required": false, "max_items": 5 },
      "number_of_flights": { "used": true, "required": true, "max": null, "suggested": 1 }, "distance": { "used": false, "required": false, "unit": "NM" },
      "blockoff_at": { "used": true, "required": false }, "blockon_at": { "used": true, "required": false }, "total_block": { "used": true, "required": false, "type": "hours" },
      "takeoff_at": { "used": true, "required": false }, "landing_at": { "used": true, "required": false }, "total_airborne": { "used": true, "required": false, "type": "hours" },
      "tach_out": { "used": true, "required": true, "type": "decimal", "decimals": 2, "suggested": "1234.50", "locked": true }, "tach_in": { "used": true, "required": true, "type": "decimal", "decimals": 2 },
      "hobbs_out": { "used": false, "required": false, "type": "decimal", "decimals": 1 }, "hobbs_in": { "used": false, "required": false, "type": "decimal", "decimals": 1 },
      "tow_object_id": { "used": false, "required": false, "choices": [] }, "tow_landing_at": { "used": false, "required": false }, "total_tow": { "used": false, "required": false, "type": "hours" },
      "tow_height_id": { "used": false, "required": false, "choices": [] }, "tow_height_value": { "used": false, "required": false },
      "fuel_uplift": { "used": true, "required": true, "unit": "l" }, "oil_uplift": { "used": true, "required": false, "unit": "l" }, "daily_check": { "used": true, "required": true, "suggested": false },
      "comment": { "used": true, "required": false, "max_length": 200 },
      "remark": { "used": true, "required": false, "categories": [ { "id": 1, "name": "Anmärkning", "blocks_object": false }, { "id": 2, "name": "Röd anmärkning", "blocks_object": true } ], "blocking_allowed": true },
      "cut_booking_id": { "used": true, "required": true, "booking": { "id": 99812, "registration": "SE-ABC", "starts_at": "2026-10-08T08:00:00Z", "ends_at": "2026-10-08T10:00:00Z" } },
      "pfly": { "used": false, "required": false }, "confirmed_total": { "used": true, "required": false }
    },
    "required_one_of": [ { "code": 11030, "message": "State the block time: both clock times, or the total", "one_of": [ ["blockoff_at", "blockon_at"], ["total_block"] ] } ],
    "charge_visible": true, "instructions": "Remember the daily check before the first flight of the day."
  }
}

POST flightlogs/preview reply

{
  "data": {
    "object": { "id": 412, "registration": "SE-ABC" }, "flight_type": { "id": 7, "name": "PRIVAT" },
    "pilot": { "id": 22583, "name": "Anna Andersson" }, "charged_member": { "id": 22583, "name": "Anna Andersson" }, "date": "2026-10-08",
    "totals": { "block": 1.25, "airborne": null, "tach": 1.2, "hobbs": null, "tow": null },
    "charge_visible": true,
    "charge": {
      "currency": "SEK", "charged_member": { "id": 22583, "name": "Anna Andersson" }, "transaction_date": "2026-10-08",
      "rows": [
        { "kind": "time", "text": "Tach (1234.5 - 1235.7)", "quantity": 1.2, "unit": "h", "unit_price": 1200, "percent": false, "amount": 1440 },
        { "kind": "correction", "text": "Member discount", "quantity": 1.2, "unit": "h", "unit_price": -60, "percent": false, "amount": -72 },
        { "kind": "correction", "text": "Landing fee ESSB", "quantity": 1, "unit": null, "unit_price": 120, "percent": false, "amount": 120 }
      ],
      "subtotal": 1488, "rounding": 0, "zero_floor": 0, "total": 1488, "vat": { "percent": 25, "amount": 297.6, "registration_number": "SE556000000001" }
    }
  },
  "meta": { "warnings": [ { "field": "number_of_flights", "code": 11025, "message": "Unreasonable number of flights" } ] }
}

Reply when the engine finds problems (400)

{
  "type": "https://api.myweblog.se/errors/validation", "title": "The flight can not be logged as it was sent", "status": 400, "code": 11000, "request_id": "b7e2c41a9d0f3e55",
  "errors": [
    { "field": "total_tach", "code": 11030, "message": "State the tach time" },
    { "field": "fuel_uplift", "code": 11043, "message": "State the fuel uplift (0 if none)" }
  ],
  "warnings": [ { "field": "number_of_flights", "code": 11025, "message": "Unreasonable number of flights" } ]
}

Error Codes

"code" in an error reply is one of these numbers. They are the same numbers as in v4 wherever v4 had the error. When "errors" names parameters or fields, each of them has a code of its own.

Code Name Comment Response
10000 HTTPS is required A call over plain HTTP is normally redirected to HTTPS by the server before it reaches the API.
403 Forbidden
10001 Unauthorized Check that your token or access token is correct and valid, and that it is sent as "Authorization: Bearer [token]". An access token that has expired gives this too, with error="invalid_token" in the WWW-Authenticate header: fetch a new one.
401 Unauthorized
10002 No access to the module The token lacks the read or write access the endpoint needs. Check the module access settings of the token.
403 Forbidden
10004 The request body must be a JSON object The body of a POST or PATCH could not be read as JSON.
400 Bad Request
10005 Invalid parameter A query parameter has the wrong form. "errors" names it.
400 Bad Request
10006 Invalid field A field of the body is missing, has the wrong type or form, or refers to something the organization does not have (a membership, a user group). "errors" names each field.
400 Bad Request
10007 Unknown parameter or field The endpoint does not have the named query parameter or body field. Check the spelling.
400 Bad Request
10010 Internal error A database error on our side. It has been logged. Nothing was saved.
500 Internal Server Error
10012 Too many failed login attempts Login check: the username has had too many wrong passwords. Wait the number of seconds in the Retry-After header.
429 Too Many Requests
10013 Too many requests More than 120 calls in a minute with the same token. Wait the number of seconds in the Retry-After header.
429 Too Many Requests
10014 Too many failed authorization attempts Too many calls with a token that was not accepted have come from your IP address. Wait the number of seconds in the Retry-After header.
429 Too Many Requests
10015 The token must be exchanged for an access token From 2028-01-01 a token can no longer be sent directly. Fetch an access token at POST /oauth/token (see Authentication).
401 Unauthorized
10020 Internal error A fault on our side. It has been logged; quote the request id to support if it persists.
500 Internal Server Error
10030 Duplicate detected A username, member number or KSAK member number, or the name of an expiry date type, is already in use. "errors" names the fields. Usernames and the names of expiry date types are compared without regard to upper and lower case.
409 Conflict
10040 User limit reached A trial organization can have at most 5 active users. Contact support to activate the organization.
409 Conflict
10050 Method not allowed The address exists, but not with this method. The Allow header lists the methods it has.
405 Method Not Allowed
10100 Not found The address does not exist, or the organization has no item with that id (404). As the code of a field in "errors": the user the body refers to does not exist (400).
404 Not Found
10105 Not modified The change or the deletion cannot be made. 400: the body of a PATCH has no fields. 409: an administrator or a user with a balance cannot be deleted; name, address, email and phone cannot be changed for a user whose login was created elsewhere.
400 Bad Request
409 Conflict
10106 Other data depends on this A setting that members' data depends on was not deleted. "dependents" says what and how much. Send the same DELETE with delete_dependents=true to delete it together with that data. See "Deleting a setting that data depends on".
409 Conflict
10110 Invalid date A date must be written YYYY-MM-DD and exist. "errors" names the parameter or field.
400 Bad Request
10121 Invalid amount The amount of a transaction must not be 0 and must be from -100000 to 100000. "accounting.amount" must be the same amount without its sign.
400 Bad Request
10130 Duplicate transaction The user already has a transaction with the same date, amount and comment.
409 Conflict
10150 Before the transaction lock date A transaction cannot be created with a date before the organization's transaction lock date.
409 Conflict
10151 Date in the future A transaction cannot have a date in the future.
400 Bad Request
10162 Debit account not found The account is not among the organization's accounts.
400 Bad Request
10163 Credit account not found The account is not among the organization's accounts.
400 Bad Request
10164 Cost center not found The cost center is not among the organization's cost centers.
400 Bad Request
10165 Project not found The project is not among the organization's projects.
400 Bad Request
10190 Unable to save the transaction Contact support.
500 Internal Server Error
10200 The organization does not use the flight log Flight types were asked for, but the flight log is switched off for the organization.
409 Conflict
10300 A booking rule stopped the action POST /bookings, PATCH /bookings/{id}, POST /bookings/{id}/cut and /cancel: the website's booking rules do not allow it. "errors" has each rule's text, in the language of Accept-Language.
409 Conflict
10301 Booking is switched off for the organization POST /bookings, PATCH /bookings/{id}, POST /bookings/{id}/cut and /cancel: the organization has switched booking off on the website.
403 Forbidden
10303 The change puts the booking last in a queue PATCH /bookings/{id}: the new time collides with another booking. "errors" names the bookings ahead. Send the change again with "queue_confirmed": true to go ahead.
409 Conflict
10308 You may not end this booking POST /bookings/{id}/cut: the booking is going on, and the website does not let the token's owner end it.
403 Forbidden
10309 You may not change this booking PATCH /bookings/{id}: the website does not let the token's owner change the booking.
403 Forbidden
10320 A booking of this type cannot be changed through the API PATCH /bookings/{id} on a service booking or an instructor duty. They are changed on the website.
409 Conflict
10331 The organization has switched the remark function off POST /remarks in an organization that does not use remarks. New in 5.14.
403 Forbidden
10332 The token's owner may not do this to a remark POST /remarks/{id}/acknowledge, /comment or /close: only a mechanic or an administrator acknowledges and closes; the member who wrote the remark may also comment. New in 5.14.
403 Forbidden
10333 The remark's state does not allow this now POST /remarks/{id}/acknowledge on a remark that is already acknowledged or closed; /comment or /close before the acknowledgement, or after the close. GET /remarks/{id} gives the status. New in 5.14.
409 Conflict
10337 You may not change the images of this remark POST /remarks/{id}/images and DELETE /remarks/{id}/images/{image_id}: the remark's own images are changed by the member who wrote the remark, a mechanic or an administrator; the image of a comment or of the closing by the one who wrote it, a mechanic or an administrator. New in 5.19.
403 Forbidden
10338 The remark is closed POST or DELETE /remarks/{id}/images on a closed remark: the remark's own images and the images of comments. The closing text's image can still be added and removed for 24 hours after the closing. New in 5.19.
409 Conflict
10339 No room for one more image POST /remarks/{id}/images: the remark has two images already, or the comment or closing has one. Remove one first. New in 5.19.
409 Conflict
10340 The remark has this picture already POST /remarks/{id}/images with a picture that is already one of the remark's own images. New in 5.19.
409 Conflict
10341 The file is not an image that can be saved POST /remarks/{id}/images: in "errors" on the field file. A JPEG, PNG, GIF or WebP of at most 20 MB and 25 million pixels. New in 5.19.
400 Bad Request
11000 The flight can not be logged as it was sent POST /flightlogs and /flightlogs/preview: the engine found problems. "errors" has each one with its field and its own code, 11001-11049: 11001 object, 11002 flight type, 11003 pilot, 11004 pilot locked, 11006 no debit model, 11007 no member to charge; 11010-11013 the date (invalid, the logbook lock date, the transaction lock date, in the future); 11020-11025 the route (airports, too few flights for the via airports, number of flights, distance, more flights than the maximum); 11030-11036 the times (a time required, the order, the ratio, above the maximum, a reading lower than the last, tach out not the last tach in, invalid time); 11040-11049 the other fields (instructor, scout, daily check, fuel/oil, towing, the remark's text and category, a blocking remark not allowed, the booking choice, PFLY).
400 Bad Request
11005 The flight log is not open for you The organization has switched the flight log off, or locked it for members who are not administrators.
403 Forbidden
11050 The flight is logged already A flight with the same object, date and times exists. For an administrator (every token) this is a warning, not an error: the flight is logged and the warning is in "meta.warnings". With other problems in the same body it is one of the errors of a 400 (code 11000).
409 Conflict
11051 The price has changed The price is not the confirmed_total that was sent. "charge" has the new price; show it and send the new total. With other problems in the same body it is one of the errors of a 400 (code 11000).
409 Conflict
11052 The amount is above the organization's limit A rule an administrator may break: a warning in "meta.warnings".
400 Bad Request
11060 The flight could not be saved A fault while saving; nothing is saved. Try again, and contact support if it happens again. 11064-11066 are warnings after a successful save: the remark could not be made, the booking could not be ended, the mail could not be sent.
500 Internal Server Error
11090 This time does not exist on that date POST /flightlogs and /flightlogs/preview with clock_times "local" (new in 5.23): a clock time in the hour that is skipped when summer time starts, at its airport. One of the errors of a 400 with code 11000.
400 Bad Request
10342 The organization is temporarily closed Every endpoint: an administrator has closed the organization temporarily on the website. "detail" is the organization's message to its members. Try again later; the organization opens it again on the website. A token sent directly (mwla1_...) is refused with 401 instead, as for an organization that is not active. New in version 5.25.
403 Forbidden

Codes of v4 that are no longer sent: 10003; 10120 (amount format), 10140 (comment empty) and 10160 (account format), which are now 10006 with the field named in "errors".