Skip to content
FloralityDocs
ChangelogGet an API key

Getting started

  • Quickstart
  • Authentication
  • Scopes
  • Privacy buckets
  • Rate limits
  • Errors
  • Versioning
  • Terminology
  • Webhooks PRO

Resources

  • Members
  • Groups
  • Entries
  • Front
  • Appearance
  • Custom fields
  • Trash
  • Search
  • Member statuses
  • Systems
  • Messaging
  • Privacy buckets
  • Terminology
  • Friends
  • Subscriptions
  • Billing
  • Import
  • Social
  • Guestbook & poll
  • Group layout
  • Activity
Docs/Privacy buckets
← PreviousScopesNext →Rate limits
Florality

Organise your system. One front at a time.

Get started

Product

  • Features
  • Pricing
  • Docs
  • Changelog
  • Security

Company

  • About
  • Our team
  • Blog
  • Contact

Resources

  • FAQ
  • Trust and Safety
  • Public REST API

Legal

  • Privacy Policy
  • Terms of Service
  • Refunds and cancellation

© 2026 Florality. All rights reserved.

Florality
DocsGetting startedPrivacy buckets

Privacy buckets

Understand what a friend’s API key can see.

QuickstartAuthenticationScopesPrivacy bucketsRate limitsErrorsVersioningTerminologyWebhooks

Identify the caller

API authentication identifies the key’s owner. Owner member requests return the owner’s data; the friend-profile redaction helper explicitly leaves owner views unchanged. Friend routes evaluate the viewing account’s friendship, blocks, bucket assignments and capability permissions.

Scopes and sharing are separate
The friends API scope permits calling friend routes. It does not make every member, note or profile field visible.

Filter member profile fields

Friend member lists first select visible members. Profile sections then use their own assigned buckets, falling back to the member’s buckets when no section buckets are assigned. Visibility requires overlap with the friend’s assigned buckets. Avatar access additionally requires an accepted, unblocked friendship and overlap with the member’s buckets.

Hidden sectionJSON result
Display namedisplayName is omitted.
Pronounspronouns is omitted.
Aboutabout is omitted; aboutTags is an empty array.
Avataravatar is omitted; avatarUrl is null.
Profile styleprofileStyle and backgroundUrl are null; background is omitted.

Compare an owner and friend response

These demo excerpts show the same visible member before and after all five profile sections are denied. Other response fields are omitted from the excerpts. The member remains visible, so its identifier and name remain.

JSON
{
  "_id": "11111111-1111-4111-8111-111111111111",
  "name": "River",
  "displayName": "River",
  "pronouns": "they/them",
  "about": "A demo profile.",
  "aboutTags": [
    "demo"
  ],
  "avatar": "demo-avatar",
  "avatarUrl": "https://example.com/demo-avatar.png",
  "profileStyle": null,
  "background": "demo-background",
  "backgroundUrl": "https://example.com/demo-background.png"
}
JSON
{
  "_id": "11111111-1111-4111-8111-111111111111",
  "name": "River",
  "aboutTags": [],
  "avatarUrl": null,
  "profileStyle": null,
  "backgroundUrl": null
}

Handle filtered collections

ResourceVerified friend-route behaviour
MembersMember visibility gates determine which members are returned; an inaccessible individual profile returns 404.
NotesUnreadable notes are filtered out. A denied memberId filter returns an empty array.
Custom fieldsA denied member-profile gate returns 404. Definitions without read access are omitted. An empty result distinguishes no_definitions from none_visible using emptyHint.
FrontCurrent front and history filter members through friend-front read checks; hidden sessions are excluded.
Member statusesMember-specific status reads require members.statuses.read, members.profile.read and member bucket overlap; status definitions are also bucket-filtered. Account-level friend statuses require an accepted, unblocked friendship and visible definition buckets. Denied results are empty arrays.
Groups and foldersThe tree route requires an accepted, unblocked friendship. Folders require groups.read and bucket overlap. Counts include only visible members; unreadable folders and empty branches are removed.

Social links and widgets use their own visibility settings rather than these member-profile buckets. The friend social route requires an accepted, unblocked friendship. Private items are hidden from friends; mutuals_only currently also permits accepted friends.

Do not treat a filtered collection as a complete copy of the owner’s resources. Consult the friend endpoint reference for each route’s precise shape and status codes.

← Previous guideScopesNext guide →Rate limits

On this page

  • Identify the caller
  • Filter member profile fields
  • Compare an owner and friend response
  • Handle filtered collections