>>

Get Sphere

This route does not require a valid Authorization header, however it is preferred to provide it.

GET/spheres/<identifier>

Get a sphere’s data using a Sphere Identifier.

>>

Path Params

NameType
identifierSphereIdentifier
>>

Response

200Sphere

FieldTypeDescription
idNumberThe spheres’s ID.
owner_idNumberThe ID of the sphere’s owner.
name?StringThe name of the sphere.
slugStringThe slug of the sphere.
typeSphereTypeThe sphere’s type.
description?StringThe sphere’s description, can be between 1 and 4096 characters.
icon?NumberThe sphere’s icon. This field has to be a valid file ID in the “sphere-icons” bucket.
banner?NumberThe sphere’s banner. This field has to be a valid file ID in the “sphere-banners” bucket.
badgesNumberThe sphere’s badges as a bitfield.
categoriesArray of CategorysThe categories that this sphere contains.
membersArray of MembersThe members that are inside this sphere.
emojisArray of EmojisThe emojis that this sphere has.
>>

Example

curl \
  -H "Authorization: <token>" \
  https://api.eludris.gay/spheres/4204171493377

{
  "id": 4204171493377,
  "owner_id": 4203748065281,
  "slug": "horse",
  "type": "HYBRID",
  "badges": 0,
  "channels": [{
      "type": "TEXT",
      "id": 4204171493378,
      "sphere_id": 4204171493377,
      "name": "general",
      "position": 0
    }]
}