Remove the stored age range
Changed onRemoves the stored age range with the time it was received, and deletes every App Attest key registered to the current user. After that, mature content is locked again in regions where a date of birth typed in is not enough for mature content. The date of birth and settings do not change. When no age range is stored, the request still succeeds. Returns the updated user.
Request
- Base URLhttps://web.fluxer.app/api/v1
- AuthAPI key in header Authorization
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Response
Success
The username of the user, not unique across the platform
The four-digit discriminator tag of the user
The display name of the user, if set
The hash of the user avatar image
Whether the user is a bot account
Whether the user is an official system user
The public flags on the user account
Reply mention preference
Whether the user has staff permissions
Access control list entries for the user
Special traits assigned to the user account
The email address associated with the account
Whether the current email address is marked as bounced by the mail provider
Deprecated. Always false.
The user biography text
The preferred pronouns of the user
The IANA timezone identifier saved by the user
Bitfield controlling who can see the profile timezone
The hash of the user profile banner image
Whether multi-factor authentication is enabled
The types of authenticators configured for MFA
Whether the email address has been verified
Whether the account is limited
Premium subscription type
ISO8601 timestamp of when premium was first activated
ISO8601 timestamp of when premium access ends, including stacked gift time
Whether premium is set to cancel at the end of the billing period
The billing cycle for the premium subscription
ISO8601 timestamp at which grace access ends after premium_until passes: after a failed renewal payment (7 days from the renewal for monthly plans, 14 for yearly), after a subscription ends (3 days), or during an App Store or Google Play grace period. Perks stay active and the original premium_since is kept on resubscribe until this timestamp passes. Null when no grace is recorded, in which case access lasts 3 days after premium_until.
Whether the user selected a premium-only discriminator that will be rerolled when non-lifetime premium access ends
Keys of the badges hidden from other people, as in the key field of a profile badge
Deprecated, use hidden_profile_badges. Whether the premium badge held is in that list
Whether the premium badge shows a masked appearance
Whether the premium start timestamp is hidden
Deprecated, use hidden_profile_badges. Whether visionary_number is in that list
Whether premium purchases are disabled for this account
Whether premium features are enabled via override
Whether premium perks are temporarily disabled for this account
Deprecated, use hidden_profile_badges. Whether operator_pass is in that list. Only present on the current user response. Older servers omit it
Whether the month and year the Operator Pass was first held are hidden from other people. Only present on the current user response. Older servers omit it
Whether the number of Operator Passes held is hidden from other people, on the badge and the Operators' wall. Only present on the current user response. Older servers omit it
ISO8601 timestamp of when the account got the Operator Pass, or null without one. Only present on the current user response.
ISO8601 timestamp of the last password change
ISO8601 timestamp of the last bulk voice-activity-sharing change. Drives the 24-hour cooldown for re-toggling the Active Now sharing default.
Deprecated. Always empty.
Whether the user is allowed to view NSFW content
Whether the user has dismissed the premium onboarding flow
Whether the user has ever made a purchase
Whether there are unread items in the gift inventory
Whether mature content is unlocked for the account in regions where a date of birth typed in is not enough for mature content. It is true when the iOS or Android app sent an age range of 18 or over, when staff set it, or when the account already had mature content unlocked before. Never true from an age range on a self-hosted instance
ISO8601 timestamp of when the user last agreed to the terms of service
ISO8601 timestamp of when the user was last shown the current privacy policy. People are informed of it, they do not agree to it
Whether the account can be signed in to again from another device: an email on instances that sign in with an email, a password otherwise
How far the account has got with setting up a way to sign in
What the account still has to do before it can use everything
Whether the account has a password
Whether the account still has to enter its date of birth, which clients ask for before anything else
Whether Fluxer keeps an age range for the account that the iOS or Android app sent from the Apple or Google account. The range itself is not included
Whether other people see only the username and tag of this account until it has a confirmed email address
Changes
- info
endpoint added
- info