Organizers API

Organizers represent the companies or collectives that run festivals. A festival is linked to one organizer via organizer_id. Organizers can have multiple managers (users).

List Organizers

Endpoint: GET /organizers

Headers: None required (public endpoint)

Response:

[
  {
    "id": "some-organizer",
    "name": "Some Organizer",
    "description": "Europe's leading outdoor festival collective.",
    "photo": "https://storage.festivalism.com/organizers/some-organizer/photo.jpg",
    "managers": [
      {
        "id": "user-uuid",
        "firstName": "Jane",
        "lastName": "Doe",
        "email": "jane@example.com"
      }
    ]
  }
]

Create Organizer

Endpoint: POST /organizers

Headers:

• X-F-Authorization: Client token (required)
• X-F-Authentication: User token (required)
• Content-Type: multipart/form-data or application/json

Request Body:

{
  "id": "my-organizer",
  "name": "My Organizer",
  "description": "Festival collective based in Berlin.",
  "photo": "base64-encoded-image-or-url"
}

id must be a URL-safe slug (lowercase letters, digits, hyphens). It is permanent and cannot be changed after creation.

Response: Returns the created organizer object.

Update Organizer

Endpoint: PUT /organizers/:id

Headers:

• X-F-Authorization: Client token (required)
• X-F-Authentication: User token (required)

Request Body: Any subset of name, description, photo.

Response: Returns the updated organizer object.

Delete Organizer

Endpoint: DELETE /organizers/:id

Headers:

• X-F-Authorization: Client token (required)
• X-F-Authentication: User token (required)

Response:

{ "message": "Organizer deleted successfully" }