Speakers

Resource description

The speaker resource contains the following public fields:

Field

Type

Description

code

string

A unique, alphanumeric identifier, also used in URLs

name

string

The speaker’s public name

biography

string

The speaker’s self-submitted biography, markdown-formatted text.

submissions

list

A list of submission codes, e.g. ["ABCDEF", "GHIJKL"]

avatar

string

The speaker avatar URL

email

string

The speaker’s email address. Available if the requesting user has organiser privileges.

availabilities

list

A list of availability objects, containing the fields id, start, end, and allDay for each availability object. Available if the requesting user has organiser privileges.

New in version 1.1.0: The availabilities field for organisers was added in pretalx v1.1.0.

Endpoints

GET /api/events/{event}/speakers/

Returns a list of all speakers the authenticated user/token has access to, or all confirmed, publicly scheduled speakers for unauthenticated users.

Example request:

GET /api/events/sampleconf/speakers/ HTTP/1.1
Accept: application/json, text/javascript

Example response:

HTTP/1.1 200 OK
Vary: Accept
Content-Type: application/json

{
  "count": 1,
  "next": null,
  "previous": null,
  "results": [
    {
      "code": "ABCDE",
      "name": "Jane",
      "biography": "A good speaker",
      "submissions": ["DEFAB"],
      "avatar": "https://example.org/media/avatar.png",
      "availabilities": [
        {
          "id": 1,
          "start": "2019-07-24T04:00:00Z",
          "end": "2019-07-25T04:00:00Z",
          "allDay": false
        }
      ]
    }
  ]
}
Parameters

  • event – The slug field of the event to fetch

Query Parameters

  • page – The page number in case of a multi-page result set, default is 1

  • q – Search through speakers by name

GET /api/events/(event)/speakers/{code}/

Returns information on one speaker, identified by their slug.

Example request:

GET /api/events/sampleconf/speakers/ABCDE HTTP/1.1
Accept: application/json, text/javascript

Example response:

HTTP/1.1 200 OK
Vary: Accept
Content-Type: application/json

{
  "code": "ABCDE",
  "name": "Jane",
  "biography": "A good speaker",
  "submissions": ["DEFAB"],
  "avatar": "https://example.org/media/avatar.png",
  {
    "id": 1,
    "start": "2019-07-24T04:00:00Z",
    "end": "2019-07-25T04:00:00Z",
    "allDay": false
  }
}
Parameters

  • event – The slug field of the event to fetch

  • code – The code field of the speaker to fetch

Status Codes