Florality
FeaturesPricingSecurityFAQAbout
Sign upSign in
Public REST APIv1

REST reference & guides

Public REST APIv1

REST reference & guides

Get started

  • Overview
  • Authentication
  • Scopes
  • Errors

API reference

  • Members
  • Groups
  • Entries
  • Front
  • Appearance
  • Custom fields
  • Trash
  • Search
    • GETSearch catalog
    • GETUnified search
    • GETSearch members
    • GETSearch notes
    • GETSearch groups (folders)
  • Member statuses
  • Systems
  • Messaging
  • Privacy buckets
  • Terminology
  • Friends
  • Subscriptions
  • Billing
  • Import
  • Social
  • Guestbook & poll
  • Group layout
  • Activity
  1. Documentation
  2. Search
API keys
Florality

Organise your system. One front at a time.

Get startedSign in

Product

  • Features
  • Pricing
  • Public REST API
  • Security

Company

  • About
  • Our team
  • Changelog
  • Contact

Resources

  • FAQ
  • Trust & Safety
  • Privacy Policy
  • Terms of Service
  • Refunds and cancellation

© 2026 Florality. All rights reserved.

Privacy·Terms·

Search

Base path: /api/v1/search. Server-side ILIKE search over members, notes (entries), and directories. Result rows include type (member | note | directory), id, label, optional subtitle, and dashboard href paths for deep links.

Authentication: search: read.

See Scopes and Errors.

Search catalog (all items)

GET/api/v1/search/catalog

Returns every active member (non-archived), directory, and note for fuzzy matching on the client. Response can be large for big accounts: prefer scoped search endpoints when possible.

No query parameters allowed.

cURL

Shell
curl -sS \
  -H "Authorization: Bearer YOUR_TOKEN" \
  "https://api.floralitys.com/api/v1/search/catalog"

Status codes

  • 200: JSON array of search result objects
  • 400: unknown query parameters
  • 401 / 403: auth / scope
  • 503: PRECONDITION_FAILED when Postgres is not configured

Unified search

GET/api/v1/search

Query q (optional; default empty string returns empty array). Optional limitPerType integer 1–50 per category (members, directories, notes). Unknown query keys return 400.

JSON
{
  "type": "member",
  "id": "uuid",
  "label": "Display or legal name",
  "subtitle": "Optional legal name when label is display",
  "href": "/dashboard/members/{id}"
}

cURL

Shell
curl -sS \
  -H "Authorization: Bearer YOUR_TOKEN" \
  "https://api.floralitys.com/api/v1/search?q=alex&limitPerType=10"

Status codes

  • 200: JSON array (members + directories + notes)
  • 400: invalid parameters
  • 401 / 403: auth / scope
  • 503: database not configured

Search members

GET/api/v1/search/members: q, optional limit (1–50).

cURL

Shell
curl -sS \
  -H "Authorization: Bearer YOUR_TOKEN" \
  "https://api.floralitys.com/api/v1/search/members?q=tea&limit=20"

Search notes

GET/api/v1/search/notes: same query shape as members.


Search groups (folders)

GET/api/v1/search/groups: same query shape as members. Result rows use type: "directory" for folder nodes (stable JSON after the groups merge).