UX Forum | API

API calls

GET/apiPrints HTML documentation of the API.
All data used by UX Forum are available via open and free API. This documentation explains logic and nuances of using the API.
In case of any questions or requests contact us via Facebook.

Meetups

GET/api/meetupsLists all meetups.
Lists all meetups in JSON format – array with objects representing meetups. By default the JSON uses custom UX Forum template, this can be changed by using query parameters.
Successful request returns status code 200.
You can use query string parameters for aditional customization. First parameter must be preceeded by ? symbol, all others by & symbol.
Combining multiple parameters and values:
www.dev.uxforum.sk/api/meetups?status=finished&language=sk,cz&search=design&sort=+date&limit=5&offset=2&pretty=false&vocabulary=uxforum,schema
Some parameters can have only one value while others can have multiple values. Both OR and AND logic are available for parameters supporting multiple values. OR logic is implemented by separating the values with comma while AND logic is implemented by repeating the parameter with different values.
Lists all meetups from either 2018 or 2019 (comma separated values – OR logic) that have photos publicly available and have livestream recording publicly available (repeating the parameter with different values – AND logic):
www.dev.uxforum.sk/api/meetups?year=2018,2019&url=photos&url=livestream
Request with invalid or unknown query string parameter returns status code 400.
Filters
Filters enable you to remove all unwanted meetups based on multiple given criteria. Supporting multiple values, filters implement both OR and AND logic. You can use following filter parameters and their respective values:
- year
  2018
  2019
  2020
- difficulty
  0
  1
  2
  3
- status
  draft
  upcoming
  ongoing
  finished
- language
  sk
  cz
  en
- country
  sk
  hu
- city
  bratislava
  budapest
- venue
  sygic
  prezi
- url
  register
  photos
  feedback
  facebook
  slido
  livestream
- id
  13 possible values
  2018-02-20
  2018-04-17
  2018-06-19
  2018-09-11
  2018-10-23
  2018-11-20
  2018-12-20
  2019-03-05
  2019-06-14
  2019-06-18
  2019-10-08
  2019-12-03
  2020-02-04
Lists all upcoming meetups:
www.dev.uxforum.sk/api/meetups?status=upcoming
Lists all meetups that took place in Bratislava either in year 2018 or in 2019 that have photos publicly available:
www.dev.uxforum.sk/api/meetups?city=bratislava&status=finished&year=2018,2019&url=photos
Combining multipe values separated by comma into one parameter implements OR logic. Repeating the same parameter with different values implements AND logic.
Lists all meetups that had either livestream or slido available:
www.dev.uxforum.sk/api/meetups?url=livestream,slido
Lists all meetups that had both livestream and slido available:
www.dev.uxforum.sk/api/meetups?url=livestream&url=slido
Search
You can filter meetups by searching for a specific keyword or phrase using parameter search. Search supports multiple values, therefore you can use both OR and AND logic. Search is case insensitive.
Lists all meetups where speaker John Doe was involved in any way:
www.dev.uxforum.sk/api/meetups?search=John Doe
Lists all meetups where company Random Corporation was involved in any way:
www.dev.uxforum.sk/api/meetups?search=Random Corporation
Lists all meetups that mentioned or took place during summer:
www.dev.uxforum.sk/api/meetups?search=summer
Combining multipe values separated by comma into one parameter implements OR logic. Repeating the same parameter with different values implements AND logic.
Lists all meetups that mention either research or analytics:
www.dev.uxforum.sk/api/meetups?search=research,analytics
Lists all meetups that mention both research and analytics:
www.dev.uxforum.sk/api/meetups?search=research&search=analytics
Sort
By default, the listed meetups are sorted by date. You can change the order of meetups by using a different property:
- date
- title
- difficulty
- status
- language
- country
- city
- venue
Sorting requires prepending either + for ascending order or - for descending order before the property (default is -date).
Lists all meetups sorted by difficulty starting with the easiest ones:
www.dev.uxforum.sk/api/meetups?sort=+difficulty
Lists all meetups sorted aphabetically by title:
www.dev.uxforum.sk/api/meetups?sort=+title
Sorting by multiple properties is not allowed and will result in an error.
Throws an error as sorting by multiple properties is not allowed.
www.dev.uxforum.sk/api/meetups?sort=+date,-difficulty
Throws an error as sorting by multiple properties is not allowed.
www.dev.uxforum.sk/api/meetups?sort=+date&sort=-difficulty
Pagination
It is possible to limit the listed meetups to certain number starting from a specific position. This helps reduce the size of response in case only specific amount of meetups is required. Possible parameters are:
limit
limits the amount of listed meetups (default is 0 – do not limit).
offset
offsets (skips) the listed meetups from either the beginning or the end (default is 0)
Lists only first 5 meetups:
www.dev.uxforum.sk/api/meetups?limit=5
Lists all but the first 5 meetups:
www.dev.uxforum.sk/api/meetups?offset=5
Lists 3rd and 4th meetup:
www.dev.uxforum.sk/api/meetups?limit=2&offset=2
Order of the parameters does not change the output.
Lists 5 of the most difficult meetups:
www.dev.uxforum.sk/api/meetups?sort=-difficulty&limit=5
Lists 5 of the most difficult meetups:
www.dev.uxforum.sk/api/meetups?limit=5&sort=-difficulty
Using negative offset lists given amount of meetups from the end.
Lists last 2 meetups:
www.dev.uxforum.sk/api/meetups?offset=-2
Using negative offset can yield similar results to using combination of sort and limit parameters – difference being in the order of results.
Lists 2 newest meetups ordered in desceding order:
www.dev.uxforum.sk/api/meetups?sort=-date&limit=2
Lists 2 newest meetups ordered in ascending order:
www.dev.uxforum.sk/api/meetups?sort=+date&offset=-2
Limit and offset parameters do not support multiple values.
Throws an error as using multiple values of limit or offset parameter is not allowed.
www.dev.uxforum.sk/api/meetups?limit=5,2
Throws an error as using limit or offset parameter multiple times is not allowed.
www.dev.uxforum.sk/api/meetups?limit=3&limit=5
Format
Configuring the format of returned meetups alters the size of response and used vocabularies. Possible parameters are:
pretty
beautifies the JSON response by given amount of spaces increasing its size (default is 0)
vocabulary
lists meetups in specified sets of vocabularies (default is uxforum):
uxforum
returns meetup information in our custom JSON structure
schema
returns meetup information in standard JSON-LD schema
Lists all meetups in both available vocabularies with 2 spaces of indentation for more legible experience:
www.dev.uxforum.sk/api/meetups?pretty=2&vocabulary=uxforum,schema
Meetups can be listed using 2 different vocabularies.
UX Forum vocabulary
metadata {Object}
id {String}
ID of the entry.
dir {String}
Base directory of the entry. Prepend domain name and append file names from this entry to get absolute address to files unique to this entry (slides, photos, etc.). Example: www.dev.uxforum.sk/{dir}{file}
draft {Boolean}
Entry is still an unpublished draft. If set as true then overrides publish timestamp. Unpublished entries are not available in the API.
language {String}
Main language of the entry and its description. Individual blocks can have different languages.
difficulty {Number}
Value from 0 to 3 describing the difficulty of topic. Higher number represents more difficult topic: 0 means it is viable for public while 3 means it is tailored towards senior experts.
status {String}
Status of the entry related to its timestamp. Possible values: draft, upcoming, ongoing, finished.
full {Boolean}
Boolean flag indicating whether capacity of this event was reached. If so, no other registrations are possible right now. This state can change should someone relinquish their spot.
tags {Array}
String tags used for searching.
narrative {Object}
title {String}
Title of the meetup, usually representing the name of the topic.
subtitle {String}
Subtitle is used as an additional information used in conjuction with the title.
description {String}
Description of an entry summarizing the content.
freeform {String}
Custom field using HTML tags to enable more advanced control over description of the topic. Can be used as addition to the original description.
mcs {Array}

{Object}
name {String}
Name of the master of ceremony / moderator / interviewer for this event.
role {String}
Role of the master of ceremony / moderator / interviewer in a company or organisation she represents.
company {String}
Copmany or organization the master of ceremony / moderator / interviewer represents or works at.
bio {String}
Biography of the master of ceremony / moderator / interviewer.
image {Object}
standalone {String}
Standalone photo of the master of ceremony / moderator / interviewer. Prepend base directory of the entry in path.
x {Number}
Offset of X coordinate of the photo in sprite image of all photos. First column has offset 0, second column has offset 1, etc. Multiply it by photo width to get pixel offset.
y {Number}
Offset of Y coordinate of the photo in sprite image of all photos. First row has offset 0, second row has offset 1, etc. Multiply it by photo height to get pixel offset.
w {Number}
Width of the photo in sprite image of all photos.
h {Number}
Height of the photo in sprite image of all photos.
sprite {String}
Sprite image containing this photo.
timestamps {Object}
publish {String}
The time when entry is published. Timestamp value encoded as a string in format YYYY-MM-DD HH:mm. Unpublished entries are not available in the API.
start {String}
Start of the entry. Timestamp value encoded as a string in format YYYY-MM-DD HH:mm.
end {String}
End of the entry. Timestamp value encoded as a string in format YYYY-MM-DD HH:mm.
venue {Object}
name {String}
Building or specific name of a venue where event takes place.
address {String}
Address of the venue where event takes place.
city {String}
City in which the venue is located.
country {String}
Code of a country in which the event will take place.
url {String}
URL to web-based map service with address to venue.
map {String}
Picture of a map used to find the venue. Prepend base directory of the entry in path.
branding {Object}
colors {Array}
{Object}
name {String}
Abstract name of the color used in conjuction with branding for the entry.
rgb {String}
RGB code of the color used in conjuction with branding for the entry.
bannerFB {String}
Banner with aspect ratio optimal for Facebook (1800x942). Prepend base directory of the entry in path.
bannerEB {String}
Banner with aspect ratio optimal for Eventbrite (2160x1080). Prepend base directory of the entry in path.
urls {Object}
register {String}
URL to ticket selling site for the entry.
livestream {String}
URL to site with livestream of the entry.
facebook {String}
URL to Facebook event for the entry.
slido {String}
URL to Slido event for the entry used for polls and questions during event.
feedback {String}
URL to feedback form for the entry.
photos {String}
URL to album with photos from the entry.
uxforum {String}
URL to specific uxforum entry page.
blocks {Array}
{Object}
narrative {Object}
title {String}
Title of the block.
description {String}
Description of the block.
freeform {String}
Custom field using HTML tags to enable more advanced control over description of the block. Can be used as addition to the original description.
speakers {Array}
{Object}
name {String}
Name of the speaker.
role {String}
Role of the speaker in a company or organisation they represents.
company {String}
Copmany or organization the speaker represents or works at.
bio {String}
Biography of the speaker.
image {Object}
standalone {String}
Standalone photo of the speaker. Prepend base directory of the entry in path.
x {Number}
Offset of X coordinate of the photo in sprite image of all photos. First column has offset 0, second column has offset 1, etc. Multiply it by photo width to get pixel offset.
y {Number}
Offset of Y coordinate of the photo in sprite image of all photos. First row has offset 0, second row has offset 1, etc. Multiply it by photo height to get pixel offset.
w {Number}
Width of the photo in sprite image of all photos.
h {Number}
Height of the photo in sprite image of all photos.
sprite {String}
Sprite image containing this photo.
urls {Object}
slides {String}
Slides for the block or a talk. Either a PDF file (use base directory of the entry in path) or URL to online presentation.
video {String}
URL to video recording of the block.
audio {String}
URL to audio recording of the block.
article {String}
URL to additional article which is related to or mentioned during the block.
metadata {Object}
language {String}
Language of the block and its content. Individual blocks can have different language from the main language of the meetup.
Schema.org vocabulary
@context {Context}
Vocabulary context according to Schema.org specification.
@type {Schema.org Type}
Type of Event according to Schema.org specification.
name {Text}
Combination of title and subtitle of the meetup. Usually representing the name of the topic and an additional information.
url {URL}
URL to specific uxforum entry page.
identifier {URL}
URL to specific uxforum entry page.
description {Text}
Description of an entry summarizing the content.
doorTime {DateTime}
The time admission will commence in ISO 8601 date format.
startDate {DateTime}
Start of the entry in ISO 8601 date format.
endDate {DateTime}
End of the entry in ISO 8601 date format.
duration {Duration}
The duration of the meetup in ISO 8601 date format.
isAccessibleForFree {Boolean}
A flag to signal that the event is accessible for free.
eventAttendanceMode {EventAttendanceModeEnumeration}
Indicates whether the meetup occurs online, offline, or a mix.
maximumAttendeeCapacity {Integer}
The total number of individuals that may attend the meetup.
maximumPhysicalAttendeeCapacity {Integer}
The total number of individuals that may physically attend the meetup.
maximumVirtualAttendeeCapacity {Integer}
The total number of individuals that may attend the meetup via livestream.
eventStatus {EventStatusType}
Scheduling status of the meetup.
educationalLevel {Text}
The level in terms of progression through an educational or training context. Examples of educational levels include 'beginner', 'junior', 'intermediate', or 'senior'.
image {URL}
Array of banners with aspect ratio optimal for Facebook (1800x942) and aspect ratio optimal for Eventbrite (2160x1080).
inLanguage {Language}
@type {Schema.org Type}
Type of Language according to Schema.org specification.
name {Text}
Main language of the entry and its description. Individual blocks can have different languages.
alternateName {Text}
Formal language code tag of main language of the meetup and its description expressed in BCP 47. Individual blocks can have different languages.
location {Place}
@type {Schema.org Type}
Type of Place according to Schema.org specification.
name {Text}
Building or specific name of a venue where event takes place.
hasMap {URL}
URL to web-based map service with address to venue.
address {PostalAddress}
@type {Schema.org Type}
Type of PostalAddress according to Schema.org specification.
streetAddress {Text}
Address of the venue where event takes place.
addressLocality {Text}
City in which the venue is located.
addressCountry {Text}
Two-letter ISO 3166-1 alpha-2 country code of a country in which the event will takes place.
organizer {Organization}
@type {Schema.org Type}
Type of Organization according to Schema.org specification.
name {Text}
Name of the organization.
image {URL}
Logo of the organization.
performer {Person}
@type {Schema.org Type}
Type of Person according to Schema.org specification.
givenName {Text}
Given (first) name of the speaker.
familyName {Text}
Family (last) name of the speaker.
name {Text}
Full name of the speaker.
description {Text}
Biography of the speaker.
image {URL}
Standalone photo of the speaker.
jobTitle {Text}
Job role of the speaker in a company or organisation they represent or work at.
worksFor {Organization}
Copmany or organization the speaker represents or works at.
@type {Schema.org Type}
Type of Organization according to Schema.org specification.
name {Text}
Name of the organization.
knowsLanguage {Language}
@type {Schema.org Type}
Type of Language according to Schema.org specification.
name {Text}
Language of the block and its content. Individual blocks can have different language from the main language of the meetup.
alternateName {Text}
Formal language code tag of language of the block and its content expressed in BCP 47. Individual blocks can have different language from the main language of the meetup.
offers {Offer}
@type {Schema.org Type}
Type of Offer according to Schema.org specification.
availability {ItemAvailability}
The availability of meetup ticket.
availabilityStars {DateTime}
The time when meetup is published in ISO 8601 date format.
availabilityStars {DateTime}
The time when meetup already started in ISO 8601 date format.
price {Number}
Price of the ticket.
priceCurrency {Text}
ISO 4217 currency format.
validFrom {DateTime}
The time when meetup starts in ISO 8601 date format.
validThrough {DateTime}
The time when meetup ended in ISO 8601 date format.
url {URL}
URL to ticket selling site for the entry.
recordedIn {CreativeWork}
@type {Schema.org Type}
Type of CreativeWork according to Schema.org specification.
url {URL}
URL to site with livestream of the entry.
GET/api/meetups/newestFinds the newest meetup.
Returns only the newest meetup in JSON format. Newest meetup can be upcoming, ongoing or already finished one.
This request is a shorthand for www.dev.uxforum.sk/api/meetups?sort=-date&limit:1 and www.dev.uxforum.sk/api/meetups?offset=-1.
Successful request returns status code 200.
You can use query string parameters for aditional customization. First parameter must be preceeded by ? symbol, all others by & symbol.
Combining multiple parameters and values:
www.dev.uxforum.sk/api/meetups/newest?pretty=true&vocabulary=uxforum
Request with invalid or unknown query string parameter returns status code 400.
Format
Configuring the format of returned meetups alters the size of response and used vocabularies. Possible parameters are:
pretty
beautifies the JSON response by given amount of spaces increasing its size (default is 0)
vocabulary
lists meetups in specified sets of vocabularies (default is uxforum):
uxforum
returns meetup information in our custom JSON structure
schema
returns meetup information in standard JSON-LD schema
Lists specific meetup in both available vocabularies with 2 spaces of indentation for more legible experience:
www.dev.uxforum.sk/api/meetups/newest?pretty=2&vocabulary=uxforum,schema
Meetups can be listed using 2 different vocabularies.
UX Forum vocabulary
metadata {Object}
id {String}
ID of the entry.
dir {String}
Base directory of the entry. Prepend domain name and append file names from this entry to get absolute address to files unique to this entry (slides, photos, etc.). Example: www.dev.uxforum.sk/{dir}{file}
draft {Boolean}
Entry is still an unpublished draft. If set as true then overrides publish timestamp. Unpublished entries are not available in the API.
language {String}
Main language of the entry and its description. Individual blocks can have different languages.
difficulty {Number}
Value from 0 to 3 describing the difficulty of topic. Higher number represents more difficult topic: 0 means it is viable for public while 3 means it is tailored towards senior experts.
status {String}
Status of the entry related to its timestamp. Possible values: draft, upcoming, ongoing, finished.
full {Boolean}
Boolean flag indicating whether capacity of this event was reached. If so, no other registrations are possible right now. This state can change should someone relinquish their spot.
tags {Array}
String tags used for searching.
narrative {Object}
title {String}
Title of the meetup, usually representing the name of the topic.
subtitle {String}
Subtitle is used as an additional information used in conjuction with the title.
description {String}
Description of an entry summarizing the content.
freeform {String}
Custom field using HTML tags to enable more advanced control over description of the topic. Can be used as addition to the original description.
mcs {Array}

{Object}
name {String}
Name of the master of ceremony / moderator / interviewer for this event.
role {String}
Role of the master of ceremony / moderator / interviewer in a company or organisation she represents.
company {String}
Copmany or organization the master of ceremony / moderator / interviewer represents or works at.
bio {String}
Biography of the master of ceremony / moderator / interviewer.
image {Object}
standalone {String}
Standalone photo of the master of ceremony / moderator / interviewer. Prepend base directory of the entry in path.
x {Number}
Offset of X coordinate of the photo in sprite image of all photos. First column has offset 0, second column has offset 1, etc. Multiply it by photo width to get pixel offset.
y {Number}
Offset of Y coordinate of the photo in sprite image of all photos. First row has offset 0, second row has offset 1, etc. Multiply it by photo height to get pixel offset.
w {Number}
Width of the photo in sprite image of all photos.
h {Number}
Height of the photo in sprite image of all photos.
sprite {String}
Sprite image containing this photo.
timestamps {Object}
publish {String}
The time when entry is published. Timestamp value encoded as a string in format YYYY-MM-DD HH:mm. Unpublished entries are not available in the API.
start {String}
Start of the entry. Timestamp value encoded as a string in format YYYY-MM-DD HH:mm.
end {String}
End of the entry. Timestamp value encoded as a string in format YYYY-MM-DD HH:mm.
venue {Object}
name {String}
Building or specific name of a venue where event takes place.
address {String}
Address of the venue where event takes place.
city {String}
City in which the venue is located.
country {String}
Code of a country in which the event will take place.
url {String}
URL to web-based map service with address to venue.
map {String}
Picture of a map used to find the venue. Prepend base directory of the entry in path.
branding {Object}
colors {Array}
{Object}
name {String}
Abstract name of the color used in conjuction with branding for the entry.
rgb {String}
RGB code of the color used in conjuction with branding for the entry.
bannerFB {String}
Banner with aspect ratio optimal for Facebook (1800x942). Prepend base directory of the entry in path.
bannerEB {String}
Banner with aspect ratio optimal for Eventbrite (2160x1080). Prepend base directory of the entry in path.
urls {Object}
register {String}
URL to ticket selling site for the entry.
livestream {String}
URL to site with livestream of the entry.
facebook {String}
URL to Facebook event for the entry.
slido {String}
URL to Slido event for the entry used for polls and questions during event.
feedback {String}
URL to feedback form for the entry.
photos {String}
URL to album with photos from the entry.
uxforum {String}
URL to specific uxforum entry page.
blocks {Array}
{Object}
narrative {Object}
title {String}
Title of the block.
description {String}
Description of the block.
freeform {String}
Custom field using HTML tags to enable more advanced control over description of the block. Can be used as addition to the original description.
speakers {Array}
{Object}
name {String}
Name of the speaker.
role {String}
Role of the speaker in a company or organisation they represents.
company {String}
Copmany or organization the speaker represents or works at.
bio {String}
Biography of the speaker.
image {Object}
standalone {String}
Standalone photo of the speaker. Prepend base directory of the entry in path.
x {Number}
Offset of X coordinate of the photo in sprite image of all photos. First column has offset 0, second column has offset 1, etc. Multiply it by photo width to get pixel offset.
y {Number}
Offset of Y coordinate of the photo in sprite image of all photos. First row has offset 0, second row has offset 1, etc. Multiply it by photo height to get pixel offset.
w {Number}
Width of the photo in sprite image of all photos.
h {Number}
Height of the photo in sprite image of all photos.
sprite {String}
Sprite image containing this photo.
urls {Object}
slides {String}
Slides for the block or a talk. Either a PDF file (use base directory of the entry in path) or URL to online presentation.
video {String}
URL to video recording of the block.
audio {String}
URL to audio recording of the block.
article {String}
URL to additional article which is related to or mentioned during the block.
metadata {Object}
language {String}
Language of the block and its content. Individual blocks can have different language from the main language of the meetup.
Schema.org vocabulary
@context {Context}
Vocabulary context according to Schema.org specification.
@type {Schema.org Type}
Type of Event according to Schema.org specification.
name {Text}
Combination of title and subtitle of the meetup. Usually representing the name of the topic and an additional information.
url {URL}
URL to specific uxforum entry page.
identifier {URL}
URL to specific uxforum entry page.
description {Text}
Description of an entry summarizing the content.
doorTime {DateTime}
The time admission will commence in ISO 8601 date format.
startDate {DateTime}
Start of the entry in ISO 8601 date format.
endDate {DateTime}
End of the entry in ISO 8601 date format.
duration {Duration}
The duration of the meetup in ISO 8601 date format.
isAccessibleForFree {Boolean}
A flag to signal that the event is accessible for free.
eventAttendanceMode {EventAttendanceModeEnumeration}
Indicates whether the meetup occurs online, offline, or a mix.
maximumAttendeeCapacity {Integer}
The total number of individuals that may attend the meetup.
maximumPhysicalAttendeeCapacity {Integer}
The total number of individuals that may physically attend the meetup.
maximumVirtualAttendeeCapacity {Integer}
The total number of individuals that may attend the meetup via livestream.
eventStatus {EventStatusType}
Scheduling status of the meetup.
educationalLevel {Text}
The level in terms of progression through an educational or training context. Examples of educational levels include 'beginner', 'junior', 'intermediate', or 'senior'.
image {URL}
Array of banners with aspect ratio optimal for Facebook (1800x942) and aspect ratio optimal for Eventbrite (2160x1080).
inLanguage {Language}
@type {Schema.org Type}
Type of Language according to Schema.org specification.
name {Text}
Main language of the entry and its description. Individual blocks can have different languages.
alternateName {Text}
Formal language code tag of main language of the meetup and its description expressed in BCP 47. Individual blocks can have different languages.
location {Place}
@type {Schema.org Type}
Type of Place according to Schema.org specification.
name {Text}
Building or specific name of a venue where event takes place.
hasMap {URL}
URL to web-based map service with address to venue.
address {PostalAddress}
@type {Schema.org Type}
Type of PostalAddress according to Schema.org specification.
streetAddress {Text}
Address of the venue where event takes place.
addressLocality {Text}
City in which the venue is located.
addressCountry {Text}
Two-letter ISO 3166-1 alpha-2 country code of a country in which the event will takes place.
organizer {Organization}
@type {Schema.org Type}
Type of Organization according to Schema.org specification.
name {Text}
Name of the organization.
image {URL}
Logo of the organization.
performer {Person}
@type {Schema.org Type}
Type of Person according to Schema.org specification.
givenName {Text}
Given (first) name of the speaker.
familyName {Text}
Family (last) name of the speaker.
name {Text}
Full name of the speaker.
description {Text}
Biography of the speaker.
image {URL}
Standalone photo of the speaker.
jobTitle {Text}
Job role of the speaker in a company or organisation they represent or work at.
worksFor {Organization}
Copmany or organization the speaker represents or works at.
@type {Schema.org Type}
Type of Organization according to Schema.org specification.
name {Text}
Name of the organization.
knowsLanguage {Language}
@type {Schema.org Type}
Type of Language according to Schema.org specification.
name {Text}
Language of the block and its content. Individual blocks can have different language from the main language of the meetup.
alternateName {Text}
Formal language code tag of language of the block and its content expressed in BCP 47. Individual blocks can have different language from the main language of the meetup.
offers {Offer}
@type {Schema.org Type}
Type of Offer according to Schema.org specification.
availability {ItemAvailability}
The availability of meetup ticket.
availabilityStars {DateTime}
The time when meetup is published in ISO 8601 date format.
availabilityStars {DateTime}
The time when meetup already started in ISO 8601 date format.
price {Number}
Price of the ticket.
priceCurrency {Text}
ISO 4217 currency format.
validFrom {DateTime}
The time when meetup starts in ISO 8601 date format.
validThrough {DateTime}
The time when meetup ended in ISO 8601 date format.
url {URL}
URL to ticket selling site for the entry.
recordedIn {CreativeWork}
@type {Schema.org Type}
Type of CreativeWork according to Schema.org specification.
url {URL}
URL to site with livestream of the entry.
GET/api/meetups/{id}Finds meetup by ID.
Returns only a specific meetup in JSON format. Provided ID will determine which meetup is returned. ID of each meetup is generated based on the start date of the meetup in format YYYY-MM-DD.
This request is a shorthand for www.dev.uxforum.sk/api/meetups?id={id}.
Successful request returns status code 200. Request with invalid or unknown ID returns status code 404.
You can use query string parameters for aditional customization. First parameter must be preceeded by ? symbol, all others by & symbol.
Combining multiple parameters and values:
www.dev.uxforum.sk/api/meetups/2018-02-20?pretty=true&vocabulary=uxforum
Request with invalid or unknown query string parameter returns status code 400.
Format
Configuring the format of returned meetups alters the size of response and used vocabularies. Possible parameters are:
pretty
beautifies the JSON response by given amount of spaces increasing its size (default is 0)
vocabulary
lists meetups in specified sets of vocabularies (default is uxforum):
uxforum
returns meetup information in our custom JSON structure
schema
returns meetup information in standard JSON-LD schema
Lists specific meetup in both available vocabularies with 2 spaces of indentation for more legible experience:
www.dev.uxforum.sk/api/meetups/2018-02-20?pretty=2&vocabulary=uxforum,schema
Meetups can be listed using 2 different vocabularies.
UX Forum vocabulary
metadata {Object}
id {String}
ID of the entry.
dir {String}
Base directory of the entry. Prepend domain name and append file names from this entry to get absolute address to files unique to this entry (slides, photos, etc.). Example: www.dev.uxforum.sk/{dir}{file}
draft {Boolean}
Entry is still an unpublished draft. If set as true then overrides publish timestamp. Unpublished entries are not available in the API.
language {String}
Main language of the entry and its description. Individual blocks can have different languages.
difficulty {Number}
Value from 0 to 3 describing the difficulty of topic. Higher number represents more difficult topic: 0 means it is viable for public while 3 means it is tailored towards senior experts.
status {String}
Status of the entry related to its timestamp. Possible values: draft, upcoming, ongoing, finished.
full {Boolean}
Boolean flag indicating whether capacity of this event was reached. If so, no other registrations are possible right now. This state can change should someone relinquish their spot.
tags {Array}
String tags used for searching.
narrative {Object}
title {String}
Title of the meetup, usually representing the name of the topic.
subtitle {String}
Subtitle is used as an additional information used in conjuction with the title.
description {String}
Description of an entry summarizing the content.
freeform {String}
Custom field using HTML tags to enable more advanced control over description of the topic. Can be used as addition to the original description.
mcs {Array}

{Object}
name {String}
Name of the master of ceremony / moderator / interviewer for this event.
role {String}
Role of the master of ceremony / moderator / interviewer in a company or organisation she represents.
company {String}
Copmany or organization the master of ceremony / moderator / interviewer represents or works at.
bio {String}
Biography of the master of ceremony / moderator / interviewer.
image {Object}
standalone {String}
Standalone photo of the master of ceremony / moderator / interviewer. Prepend base directory of the entry in path.
x {Number}
Offset of X coordinate of the photo in sprite image of all photos. First column has offset 0, second column has offset 1, etc. Multiply it by photo width to get pixel offset.
y {Number}
Offset of Y coordinate of the photo in sprite image of all photos. First row has offset 0, second row has offset 1, etc. Multiply it by photo height to get pixel offset.
w {Number}
Width of the photo in sprite image of all photos.
h {Number}
Height of the photo in sprite image of all photos.
sprite {String}
Sprite image containing this photo.
timestamps {Object}
publish {String}
The time when entry is published. Timestamp value encoded as a string in format YYYY-MM-DD HH:mm. Unpublished entries are not available in the API.
start {String}
Start of the entry. Timestamp value encoded as a string in format YYYY-MM-DD HH:mm.
end {String}
End of the entry. Timestamp value encoded as a string in format YYYY-MM-DD HH:mm.
venue {Object}
name {String}
Building or specific name of a venue where event takes place.
address {String}
Address of the venue where event takes place.
city {String}
City in which the venue is located.
country {String}
Code of a country in which the event will take place.
url {String}
URL to web-based map service with address to venue.
map {String}
Picture of a map used to find the venue. Prepend base directory of the entry in path.
branding {Object}
colors {Array}
{Object}
name {String}
Abstract name of the color used in conjuction with branding for the entry.
rgb {String}
RGB code of the color used in conjuction with branding for the entry.
bannerFB {String}
Banner with aspect ratio optimal for Facebook (1800x942). Prepend base directory of the entry in path.
bannerEB {String}
Banner with aspect ratio optimal for Eventbrite (2160x1080). Prepend base directory of the entry in path.
urls {Object}
register {String}
URL to ticket selling site for the entry.
livestream {String}
URL to site with livestream of the entry.
facebook {String}
URL to Facebook event for the entry.
slido {String}
URL to Slido event for the entry used for polls and questions during event.
feedback {String}
URL to feedback form for the entry.
photos {String}
URL to album with photos from the entry.
uxforum {String}
URL to specific uxforum entry page.
blocks {Array}
{Object}
narrative {Object}
title {String}
Title of the block.
description {String}
Description of the block.
freeform {String}
Custom field using HTML tags to enable more advanced control over description of the block. Can be used as addition to the original description.
speakers {Array}
{Object}
name {String}
Name of the speaker.
role {String}
Role of the speaker in a company or organisation they represents.
company {String}
Copmany or organization the speaker represents or works at.
bio {String}
Biography of the speaker.
image {Object}
standalone {String}
Standalone photo of the speaker. Prepend base directory of the entry in path.
x {Number}
Offset of X coordinate of the photo in sprite image of all photos. First column has offset 0, second column has offset 1, etc. Multiply it by photo width to get pixel offset.
y {Number}
Offset of Y coordinate of the photo in sprite image of all photos. First row has offset 0, second row has offset 1, etc. Multiply it by photo height to get pixel offset.
w {Number}
Width of the photo in sprite image of all photos.
h {Number}
Height of the photo in sprite image of all photos.
sprite {String}
Sprite image containing this photo.
urls {Object}
slides {String}
Slides for the block or a talk. Either a PDF file (use base directory of the entry in path) or URL to online presentation.
video {String}
URL to video recording of the block.
audio {String}
URL to audio recording of the block.
article {String}
URL to additional article which is related to or mentioned during the block.
metadata {Object}
language {String}
Language of the block and its content. Individual blocks can have different language from the main language of the meetup.
Schema.org vocabulary
@context {Context}
Vocabulary context according to Schema.org specification.
@type {Schema.org Type}
Type of Event according to Schema.org specification.
name {Text}
Combination of title and subtitle of the meetup. Usually representing the name of the topic and an additional information.
url {URL}
URL to specific uxforum entry page.
identifier {URL}
URL to specific uxforum entry page.
description {Text}
Description of an entry summarizing the content.
doorTime {DateTime}
The time admission will commence in ISO 8601 date format.
startDate {DateTime}
Start of the entry in ISO 8601 date format.
endDate {DateTime}
End of the entry in ISO 8601 date format.
duration {Duration}
The duration of the meetup in ISO 8601 date format.
isAccessibleForFree {Boolean}
A flag to signal that the event is accessible for free.
eventAttendanceMode {EventAttendanceModeEnumeration}
Indicates whether the meetup occurs online, offline, or a mix.
maximumAttendeeCapacity {Integer}
The total number of individuals that may attend the meetup.
maximumPhysicalAttendeeCapacity {Integer}
The total number of individuals that may physically attend the meetup.
maximumVirtualAttendeeCapacity {Integer}
The total number of individuals that may attend the meetup via livestream.
eventStatus {EventStatusType}
Scheduling status of the meetup.
educationalLevel {Text}
The level in terms of progression through an educational or training context. Examples of educational levels include 'beginner', 'junior', 'intermediate', or 'senior'.
image {URL}
Array of banners with aspect ratio optimal for Facebook (1800x942) and aspect ratio optimal for Eventbrite (2160x1080).
inLanguage {Language}
@type {Schema.org Type}
Type of Language according to Schema.org specification.
name {Text}
Main language of the entry and its description. Individual blocks can have different languages.
alternateName {Text}
Formal language code tag of main language of the meetup and its description expressed in BCP 47. Individual blocks can have different languages.
location {Place}
@type {Schema.org Type}
Type of Place according to Schema.org specification.
name {Text}
Building or specific name of a venue where event takes place.
hasMap {URL}
URL to web-based map service with address to venue.
address {PostalAddress}
@type {Schema.org Type}
Type of PostalAddress according to Schema.org specification.
streetAddress {Text}
Address of the venue where event takes place.
addressLocality {Text}
City in which the venue is located.
addressCountry {Text}
Two-letter ISO 3166-1 alpha-2 country code of a country in which the event will takes place.
organizer {Organization}
@type {Schema.org Type}
Type of Organization according to Schema.org specification.
name {Text}
Name of the organization.
image {URL}
Logo of the organization.
performer {Person}
@type {Schema.org Type}
Type of Person according to Schema.org specification.
givenName {Text}
Given (first) name of the speaker.
familyName {Text}
Family (last) name of the speaker.
name {Text}
Full name of the speaker.
description {Text}
Biography of the speaker.
image {URL}
Standalone photo of the speaker.
jobTitle {Text}
Job role of the speaker in a company or organisation they represent or work at.
worksFor {Organization}
Copmany or organization the speaker represents or works at.
@type {Schema.org Type}
Type of Organization according to Schema.org specification.
name {Text}
Name of the organization.
knowsLanguage {Language}
@type {Schema.org Type}
Type of Language according to Schema.org specification.
name {Text}
Language of the block and its content. Individual blocks can have different language from the main language of the meetup.
alternateName {Text}
Formal language code tag of language of the block and its content expressed in BCP 47. Individual blocks can have different language from the main language of the meetup.
offers {Offer}
@type {Schema.org Type}
Type of Offer according to Schema.org specification.
availability {ItemAvailability}
The availability of meetup ticket.
availabilityStars {DateTime}
The time when meetup is published in ISO 8601 date format.
availabilityStars {DateTime}
The time when meetup already started in ISO 8601 date format.
price {Number}
Price of the ticket.
priceCurrency {Text}
ISO 4217 currency format.
validFrom {DateTime}
The time when meetup starts in ISO 8601 date format.
validThrough {DateTime}
The time when meetup ended in ISO 8601 date format.
url {URL}
URL to ticket selling site for the entry.
recordedIn {CreativeWork}
@type {Schema.org Type}
Type of CreativeWork according to Schema.org specification.
url {URL}
URL to site with livestream of the entry.
GET/api/partnersLists all partners.
Lists all partners in JSON format – array with objects representing partners. By default the JSON uses custom UX Forum template, this can be changed by using query parameters.
Successful request returns status code 200.
You can use query string parameters for aditional customization. First parameter must be preceeded by ? symbol, all others by & symbol.
Combining multiple parameters and values:
www.dev.uxforum.sk/api/partners?pretty=false&vocabulary=uxforum,schema
Request with invalid or unknown query string parameter returns status code 400.
Search
You can filter partners by searching for a specific keyword or phrase using parameter search. Search supports multiple values, therefore you can use both OR and AND logic. Search is case insensitive.
Lists all information about Random Corporation:
www.dev.uxforum.sk/api/partners?search=Random Corporation
Combining multipe values separated by comma into one parameter implements OR logic. Repeating the same parameter with different values implements AND logic.
Format
Configuring the format of returned partners alters the size of response and used vocabularies. Possible parameters are:
pretty
beautifies the JSON response by given amount of spaces increasing its size (default is 0)
vocabulary
lists partners in specified sets of vocabularies (default is uxforum):
uxforum
returns job offer information in our custom JSON structure
schema
returns job offer information in standard JSON-LD schema
Lists all partners in both available vocabularies with 2 spaces of indentation for more legible experience:
www.dev.uxforum.sk/api/partners?pretty=2&vocabulary=uxforum,schema
Partners can be listed using 2 different vocabularies.
UX Forum vocabulary
name {String}
Name of the partner.
image {String}
Partner's logo in SVG format using only one color. It is recommended that you use logo provided by the partner.
url {String}
URL to partner's website.
Schema.org vocabulary
@context {Context}
Vocabulary context according to Schema.org specification.
@type {Schema.org Type}
Type of Organization according to Schema.org specification.
name {Text}
Name of the partner.
logo {URL}
Partner's logo in SVG format using only one color. It is recommended that you use logo provided by the partner.
url {URL}
URL to partner's website.
GET/api/teamLists all team members.
Lists all team members in JSON format – array with objects representing team member. By default the JSON uses custom UX Forum template, this can be changed by using query parameters.
Successful request returns status code 200.
You can use query string parameters for aditional customization. First parameter must be preceeded by ? symbol, all others by & symbol.
Combining multiple parameters and values:
www.dev.uxforum.sk/api/team?search=ux research&pretty=false&vocabulary=uxforum,schema
Request with invalid or unknown query string parameter returns status code 400.
Search
You can filter UX Forum team members by searching for a specific keyword or phrase using parameter search. Search supports multiple values, therefore you can use both OR and AND logic. Search is case insensitive.
Lists all information about John Doe:
www.dev.uxforum.sk/api/team?search=John Doe
Combining multipe values separated by comma into one parameter implements OR logic. Repeating the same parameter with different values implements AND logic.
Lists all UX Forum team members who are either UX Designers or UX Researchers (comma separated values – OR logic):
www.dev.uxforum.sk/api/team?search=ux designer,ux researcher
Format
Configuring the format of returned UX Forum team members alters the size of response and used vocabularies. Possible parameters are:
pretty
beautifies the JSON response by given amount of spaces increasing its size (default is 0)
vocabulary
lists UX Forum team members in specified sets of vocabularies (default is uxforum):
uxforum
returns UX Forum team members information in our custom JSON structure
schema
returns UX Forum team members information in standard JSON-LD schema
Lists all uxforum team members in both available vocabularies with 2 spaces of indentation for more legible experience:
www.dev.uxforum.sk/api/team?pretty=2&vocabulary=uxforum,schema
Team members can be listed using 2 different vocabularies.
UX Forum vocabulary
name {String}
Name of the team member.
role {String}
Role of the team member at the company where they work.
company {String}
Copmany or organization the team member represents or works at.
url {String}
URL to social media profile of the team member.
image {Object}
standalone {String}
Standalone photo of the team member.
x {Number}
Offset of X coordinate of the photo in sprite image of all photos. First column has offset 0, second column has offset 1, etc. Multiply it by photo width to get pixel offset.
y {Number}
Offset of Y coordinate of the photo in sprite image of all photos. First row has offset 0, second row has offset 1, etc. Multiply it by photo height to get pixel offset.
w {Number}
Width of the photo in sprite image of all photos.
h {Number}
Height of the photo in sprite image of all photos.
sprite {String}
Sprite image containing this photo.
Schema.org vocabulary
@context {Context}
Vocabulary context according to Schema.org specification.
@type {Schema.org Type}
Type of Person according to Schema.org specification.
givenName {Text}
Given (first) name of the team member.
familyName {Text}
Family (last) name of the team member.
name {Text}
Full name of the team member.
jobTitle {Text}
Job role of the team member in a company or organisation they represent or work at.
worksFor {Organization}
Copmany or organization the speaker represents or works at.
@type {Schema.org Type}
Type of Organization according to Schema.org specification.
name {Text}
Name of the organization.
url {URL}
URL to social media profile of the team member.
image {URL}
Standalone photo of the team member.

Community

GET/api/community/eventsLists all community meetups.
Returns JSON with all external meetups.
GET/api/community/events/{id}Finds community meetup by id.
Returns JSON of a specific external meetup based on an provided ID. If the ID is invalid then returns status code 404.
GET/api/community/groupsLists all groups.
Returns JSON with all groups.
GET/api/community/jobsLists all job offers.
Lists all job offers in JSON format – array with objects representing job offers. By default the JSON uses custom UX Forum template, this can be changed by using query parameters.
Successful request returns status code 200.
You can use query string parameters for aditional customization. First parameter must be preceeded by ? symbol, all others by & symbol.
Combining multiple parameters and values:
www.dev.uxforum.sk/api/community/jobs?search=ux design, ux researchlimit=5&offset=2&pretty=false&vocabulary=uxforum,schema
Some parameters can have only one value while others can have multiple values. Both OR and AND logic are available for parameters supporting multiple values. OR logic is implemented by separating the values with comma while AND logic is implemented by repeating the parameter with different values.
Lists all job offers for either UX Designer or UX Researcher (comma separated values – OR logic) located in Bratislava that offer full time employment (repeating the parameter with different values – AND logic):
www.dev.uxforum.sk/api/community/jobs?search=ux designer,ux researcher&search=bratislava&search=full-time
Request with invalid or unknown query string parameter returns status code 400.
Search
You can filter job offers by searching for a specific keyword or phrase using parameter search. Search supports multiple values, therefore you can use both OR and AND logic. Search is case insensitive.
Lists all job offers located in Bratislava:
www.dev.uxforum.sk/api/community/jobs?search=bratislava
Lists all job offers posted by Random Corporation:
www.dev.uxforum.sk/api/community/jobs?search=Random Corporation
Combining multipe values separated by comma into one parameter implements OR logic. Repeating the same parameter with different values implements AND logic.
Lists all job offers that are located in either Bratislava or Kosice :
www.dev.uxforum.sk/api/community/jobs?search=Bratislava,Kosice
Lists all job offers that offer both full time and part time employment:
www.dev.uxforum.sk/api/community/jobs?search=full-time&search=part-time
Pagination
It is possible to limit the listed job offers to certain number starting from a specific position. This helps reduce the size of response in case only specific amount of job offers is required. Possible parameters are:
limit
limits the amount of listed job offers (default is 0 – do not limit).
offset
offsets (skips) the listed job offers from either the beginning or the end (default is 0)
Lists only first 5 job offers:
www.dev.uxforum.sk/api/community/jobs?limit=5
Lists all but the first 5 job offers:
www.dev.uxforum.sk/api/community/jobs?offset=5
Lists 3rd and 4th job offer:
www.dev.uxforum.sk/api/community/jobs?limit=2&offset=2
Order of the parameters does not change the output.
Lists first 5 job offers located in Bratislava:
www.dev.uxforum.sk/api/community/jobs?search=bratislava&limit=5
Lists first 5 job offers located in Bratislava:
www.dev.uxforum.sk/api/community/jobs?limit=5&search=bratislava
Using negative offset lists given amount of job offers from the end.
Lists last 2 job offers:
www.dev.uxforum.sk/api/community/jobs?offset=-2
Limit and offset parameters do not support multiple values.
Throws an error as using multiple values of limit or offset parameter is not allowed.
www.dev.uxforum.sk/api/community/jobs?limit=5,2
Throws an error as using limit or offset parameter multiple times is not allowed.
www.dev.uxforum.sk/api/community/jobs?limit=3&limit=5
Format
Configuring the format of returned job offers alters the size of response and used vocabularies. Possible parameters are:
pretty
beautifies the JSON response by given amount of spaces increasing its size (default is 0)
vocabulary
lists job offers in specified sets of vocabularies (default is uxforum):
uxforum
returns job offer information in our custom JSON structure
schema
returns job offer information in standard JSON-LD schema
Lists all job offers in both available vocabularies with 2 spaces of indentation for more legible experience:
www.dev.uxforum.sk/api/community/jobs?pretty=2&vocabulary=uxforum,schema
Job offers can be listed using 2 different vocabularies.
UX Forum vocabulary
role {String}
Offered job role.
company {String}
Copmany or organization offering the job.
url {String}
URL to the posted job offer.
location {String}
Location of the offered job.
employment {String}
Type of employment.
compensation {String}
Compensation for the offered job.
Schema.org vocabulary
@context {Context}
Vocabulary context according to Schema.org specification.
@type {Schema.org Type}
Type of JobPosting according to Schema.org specification.
title {Text}
Offered job role.
hiringOrganization {Organization}

@type {Schema.org Type}
Type of Organization according to Schema.org specification.
name {Text}
Company or organization offering the job.
url {URL}
URL to the posted job offer.
jobLocation {Place}
@type {Schema.org Type}
Type of Place according to Schema.org specification.
address {Text}
Location of the offered job.
employmentType {Text}
Type of employment.
incentiveCompensation {Text}
Compensation for the offered jab.

Resources

GET/resources/logoLogo of UX Forum in SVG format.
Returns SVG image of UX Forum logo:
GET/resources/previewSocial media preview thumbnail of UX Forum page.
Returns PNG image preview thumbnail used on social media pages of UX Forum:
GET/resources/favicons/{size}Favicons of various sizes with ratio 1:1.
Returns a favicon used by UX Forum of specified size. Possible sizes:
- 16
- 32
- 48
GET/resources/icons/{size}Icons of various sizes with ratio 1:1.
Returns an icon used by UX Forum of specified size. Possible sizes:
- 72
- 76
- 96
- 120
- 128
- 144
- 152
- 180
- 192
- 384
- 512

Redirects

GET/{social}Redirects to social platforms used by UX Forum.
GET/{service}Redirects to sites used by the latest meetup.
GET/meetup/newest|{id}/{service}Redirects to sites used by the specific meetup.

API calls

Meetups

Filters

Search

Sort

Pagination

Format

UX Forum vocabulary

Schema.org vocabulary

Format

UX Forum vocabulary

Schema.org vocabulary

Format

UX Forum vocabulary

Schema.org vocabulary

Search

Format

UX Forum vocabulary

Schema.org vocabulary

Search

Format

UX Forum vocabulary

Schema.org vocabulary

Community

Search

Pagination

Format

UX Forum vocabulary

Schema.org vocabulary

Resources

Redirects