Reorder friend front
Updates reorder friend front for the authorised account.
PATCH
/api/v1/friends/{friendUserId}/front/orderfriends: read_write1,000 requests/minute/key · all plansActive API keys: Free 1, Pro 5, Pro+ 5. The request rate is the same on every plan.
Friend access checks
A missing accepted friendship or a block in either direction returns 404. Missing permission to change a friend’s front returns 403; a member that is not visible can also return 403.
Parameters
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
friendUserId | string (uuid) | Required | Identifier of the friend user. |
Request body
application/json · required
Unknown properties are rejected.
| Name | Type | Required | Description |
|---|---|---|---|
memberIds | array<string (uuid)> | Required | Associated member identifiers. |
Response schema
204
Successful operation. No response body.
Errors
400· JSON errorMissing friend user id.
401· JSON errorMissing or invalid API key. Use Authorization: Bearer <token>.
403· JSON errorRequires friends: read_write; ownership or feature restrictions may also deny access.
404· JSON errorRequest failed (NOT_FOUND).
409· JSON errorRequest failed (CONFLICT).
429· JSON errorAPI rate limit exceeded (1000 requests per minute). Retry shortly.
Request example
Set FLORALITY_KEY in your environment. These examples use demo identifiers.
curl --request PATCH 'https://floralitys.com/api/v1/friends/11111111-1111-4111-8111-111111111111/front/order' \
--header "Authorization: Bearer $FLORALITY_KEY" \
--header "Content-Type: application/json" \
--data '{
"memberIds": [
"11111111-1111-4111-8111-111111111111"
]
}'Responses
Successful operation. No response body.
No response body.
Example values are illustrative demo data.