git.squeep.com Git - akkoma/blob - docs/api/differences_in_mastoapi_responses.md

   1 # Differences in Mastodon API responses from vanilla Mastodon
   2
   3 A Pleroma instance can be identified by "<Mastodon version> (compatible; Pleroma <version>)" present in `version` field in response from `/api/v1/instance`
   4
   5 ## Flake IDs
   6
   7 Pleroma uses 128-bit ids as opposed to Mastodon's 64 bits. However just like Mastodon's ids they are sortable strings
   8
   9 ## Attachment cap
  10
  11 Some apps operate under the assumption that no more than 4 attachments can be returned or uploaded. Pleroma however does not enforce any limits on attachment count neither when returning the status object nor when posting.
  12
  13 ## Timelines
  14
  15 Adding the parameter `with_muted=true` to the timeline queries will also return activities by muted (not by blocked!) users.
  16
  17 ## Statuses
  18
  19 - `visibility`: has an additional possible value `list`
  20
  21 Has these additional fields under the `pleroma` object:
  22
  23 - `local`: true if the post was made on the local instance
  24 - `conversation_id`: the ID of the conversation the status is associated with (if any)
  25 - `in_reply_to_account_acct`: the `acct` property of User entity for replied user (if any)
  26 - `content`: a map consisting of alternate representations of the `content` property with the key being it's mimetype. Currently the only alternate representation supported is `text/plain`
  27 - `spoiler_text`: a map consisting of alternate representations of the `spoiler_text` property with the key being it's mimetype. Currently the only alternate representation supported is `text/plain`
  28
  29 ## Attachments
  30
  31 Has these additional fields under the `pleroma` object:
  32
  33 - `mime_type`: mime type of the attachment.
  34
  35 ## Accounts
  36
  37 The `id` parameter can also be the `nickname` of the user. This only works in these endpoints, not the deeper nested ones for following etc.
  38
  39 - `/api/v1/accounts/:id`
  40 - `/api/v1/accounts/:id/statuses`
  41
  42 Has these additional fields under the `pleroma` object:
  43
  44 - `tags`: Lists an array of tags for the user
  45 - `relationship{}`: Includes fields as documented for Mastodon API https://docs.joinmastodon.org/api/entities/#relationship
  46 - `is_moderator`: boolean, nullable,  true if user is a moderator
  47 - `is_admin`: boolean, nullable, true if user is an admin
  48 - `confirmation_pending`: boolean, true if a new user account is waiting on email confirmation to be activated
  49 - `hide_followers`: boolean, true when the user has follower hiding enabled
  50 - `hide_follows`: boolean, true when the user has follow hiding enabled
  51 - `settings_store`: A generic map of settings for frontends. Opaque to the backend. Only returned in `verify_credentials` and `update_credentials`
  52 - `chat_token`: The token needed for Pleroma chat. Only returned in `verify_credentials`
  53
  54 ### Source
  55
  56 Has these additional fields under the `pleroma` object:
  57
  58 - `show_role`: boolean, nullable, true when the user wants his role (e.g admin, moderator) to be shown
  59 - `no_rich_text` - boolean, nullable, true when html tags are stripped from all statuses requested from the API
  60
  61 ## Account Search
  62
  63 Behavior has changed:
  64
  65 - `/api/v1/accounts/search`: Does not require authentication
  66
  67 ## Notifications
  68
  69 Has these additional fields under the `pleroma` object:
  70
  71 - `is_seen`: true if the notification was read by the user
  72
  73 ## POST `/api/v1/statuses`
  74
  75 Additional parameters can be added to the JSON body/Form data:
  76
  77 - `preview`: boolean, if set to `true` the post won't be actually posted, but the status entitiy would still be rendered back. This could be useful for previewing rich text/custom emoji, for example.
  78 - `content_type`: string, contain the MIME type of the status, it is transformed into HTML by the backend. You can get the list of the supported MIME types with the nodeinfo endpoint.
  79 - `to`: A list of nicknames (like `lain@soykaf.club` or `lain` on the local server) that will be used to determine who is going to be addressed by this post. Using this will disable the implicit addressing by mentioned names in the `status` body, only the people in the `to` list will be addressed. The normal rules for for post visibility are not affected by this and will still apply.
  80 - `visibility`: string, besides standard MastoAPI values (`direct`, `private`, `unlisted` or `public`) it can be used to address a List by setting it to `list:LIST_ID`.
  81
  82 ## PATCH `/api/v1/update_credentials`
  83
  84 Additional parameters can be added to the JSON body/Form data:
  85
  86 - `no_rich_text` - if true, html tags are stripped from all statuses requested from the API
  87 - `hide_followers` - if true, user's followers will be hidden
  88 - `hide_follows` - if true, user's follows will be hidden
  89 - `hide_favorites` - if true, user's favorites timeline will be hidden
  90 - `show_role` - if true, user's role (e.g admin, moderator) will be exposed to anyone in the API
  91 - `default_scope` - the scope returned under `privacy` key in Source subentity
  92 - `pleroma_settings_store` - Opaque user settings to be saved on the backend.
  93 - `skip_thread_containment` - if true, skip filtering out broken threads
  94 - `pleroma_background_image` - sets the background image of the user.
  95
  96 ### Pleroma Settings Store
  97 Pleroma has mechanism that allows frontends to save blobs of json for each user on the backend. This can be used to save frontend-specific settings for a user that the backend does not need to know about.
  98
  99 The parameter should have a form of `{frontend_name: {...}}`, with `frontend_name` identifying your type of client, e.g. `pleroma_fe`. It will overwrite everything under this property, but will not overwrite other frontend's settings.
 100
 101 This information is returned in the `verify_credentials` endpoint.
 102
 103 ## Authentication
 104
 105 *Pleroma supports refreshing tokens.
 106
 107 `POST /oauth/token`
 108 Post here request with grant_type=refresh_token to obtain new access token. Returns an access token.
 109
 110 ## Account Registration
 111 `POST /api/v1/accounts`
 112
 113 Has theses additionnal parameters (which are the same as in Pleroma-API):
 114     * `fullname`: optional
 115     * `bio`: optional
 116     * `captcha_solution`: optional, contains provider-specific captcha solution,
 117     * `captcha_token`: optional, contains provider-specific captcha token
 118     * `token`: invite token required when the registerations aren't public.