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 - `expires_at`: a datetime (iso8601) that states when the post will expire (be deleted automatically), or empty if the post won't expire
  29 - `thread_muted`: true if the thread the post belongs to is muted
  30
  31 ## Attachments
  32
  33 Has these additional fields under the `pleroma` object:
  34
  35 - `mime_type`: mime type of the attachment.
  36
  37 ## Accounts
  38
  39 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.
  40
  41 - `/api/v1/accounts/:id`
  42 - `/api/v1/accounts/:id/statuses`
  43
  44 Has these additional fields under the `pleroma` object:
  45
  46 - `tags`: Lists an array of tags for the user
  47 - `relationship{}`: Includes fields as documented for Mastodon API https://docs.joinmastodon.org/api/entities/#relationship
  48 - `is_moderator`: boolean, nullable,  true if user is a moderator
  49 - `is_admin`: boolean, nullable, true if user is an admin
  50 - `confirmation_pending`: boolean, true if a new user account is waiting on email confirmation to be activated
  51 - `hide_followers`: boolean, true when the user has follower hiding enabled
  52 - `hide_follows`: boolean, true when the user has follow hiding enabled
  53 - `settings_store`: A generic map of settings for frontends. Opaque to the backend. Only returned in `verify_credentials` and `update_credentials`
  54 - `chat_token`: The token needed for Pleroma chat. Only returned in `verify_credentials`
  55 - `deactivated`: boolean, true when the user is deactivated
  56
  57 ### Source
  58
  59 Has these additional fields under the `pleroma` object:
  60
  61 - `show_role`: boolean, nullable, true when the user wants his role (e.g admin, moderator) to be shown
  62 - `no_rich_text` - boolean, nullable, true when html tags are stripped from all statuses requested from the API
  63
  64 ## Conversations
  65
  66 Has an additional field under the `pleroma` object:
  67
  68 - `recipients`: The list of the recipients of this Conversation. These will be addressed when replying to this conversation.
  69
  70 ## Account Search
  71
  72 Behavior has changed:
  73
  74 - `/api/v1/accounts/search`: Does not require authentication
  75
  76
  77 ## Notifications
  78
  79 Has these additional fields under the `pleroma` object:
  80
  81 - `is_seen`: true if the notification was read by the user
  82
  83 ## POST `/api/v1/statuses`
  84
  85 Additional parameters can be added to the JSON body/Form data:
  86
  87 - `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.
  88 - `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.
  89 - `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.
  90 - `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`.
  91 - `expires_in`: The number of seconds the posted activity should expire in. When a posted activity expires it will be deleted from the server, and a delete request for it will be federated. This needs to be longer than an hour.
  92 - `in_reply_to_conversation_id`: Will reply to a given conversation, addressing only the people who are part of the recipient set of that conversation. Sets the visibility to `direct`.
  93
  94 ## PATCH `/api/v1/update_credentials`
  95
  96 Additional parameters can be added to the JSON body/Form data:
  97
  98 - `no_rich_text` - if true, html tags are stripped from all statuses requested from the API
  99 - `hide_followers` - if true, user's followers will be hidden
 100 - `hide_follows` - if true, user's follows will be hidden
 101 - `hide_favorites` - if true, user's favorites timeline will be hidden
 102 - `show_role` - if true, user's role (e.g admin, moderator) will be exposed to anyone in the API
 103 - `default_scope` - the scope returned under `privacy` key in Source subentity
 104 - `pleroma_settings_store` - Opaque user settings to be saved on the backend.
 105 - `skip_thread_containment` - if true, skip filtering out broken threads
 106 - `pleroma_background_image` - sets the background image of the user.
 107
 108 ### Pleroma Settings Store
 109 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.
 110
 111 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.
 112
 113 This information is returned in the `verify_credentials` endpoint.
 114
 115 ## Authentication
 116
 117 *Pleroma supports refreshing tokens.
 118
 119 `POST /oauth/token`
 120 Post here request with grant_type=refresh_token to obtain new access token. Returns an access token.
 121
 122 ## Account Registration
 123 `POST /api/v1/accounts`
 124
 125 Has theses additionnal parameters (which are the same as in Pleroma-API):
 126     * `fullname`: optional
 127     * `bio`: optional
 128     * `captcha_solution`: optional, contains provider-specific captcha solution,
 129     * `captcha_token`: optional, contains provider-specific captcha token
 130     * `token`: invite token required when the registerations aren't public.