DABBBLE API v1

Use the DABBBLE v1 APIs to retrieve current, published worktaster opportunities and events in JSON format.

Build your own listings, create custom interfaces or use the data in your applications. Both endpoints provide read-only access and support filtering by organisation.

Available APIs

Worktaster API

Retrieve current, published worktaster opportunities.

Available information includes:

• Opportunity titles and organisation names.
• Descriptions and images.
• Attendance days and times.
• Start dates, end dates and application deadlines.
• Hourly rates and daily expenses.
• Skills and other benefits.
• Links to opportunity pages.

curl "https://api.dabbble.app/v1/worktasters"

The guide includes response fields, example JSON, organisation filtering and PHP integration examples.

View the Worktaster API documentation

Events API

Retrieve current, published events, ordered by start date, earliest first.

Available information includes:

• Event titles and organisation names.
• Descriptions and images.
• Start and end dates.
• Event type values.
• Links to event pages.

curl "https://api.dabbble.app/v1/events"

The guide includes response fields, date formats, image fallbacks, organisation filtering and error responses.

View the Events API documentation

Authentication

These public endpoints do not require an API key or account.

They provide read-only access. They do not support creating, editing or deleting records.

Filter by Organisation

Add the optional org query parameter to retrieve content from one organisation.

Worktasters

curl --get \
    --data-urlencode "org=Adventures + Wisdom Institute" \
    "https://api.dabbble.app/v1/worktasters"

Events

curl --get \
    --data-urlencode "org=DABBBLE" \
    "https://api.dabbble.app/v1/events"

Use the full organisation name. Omit org, or leave it empty, to retrieve all matching current records.

URL-encode names containing spaces or special characters. For example:

https://api.dabbble.app/v1/events?org=Adventures%20%2B%20Wisdom%20Institute

Each endpoint guide explains its matching behaviour.

Response Structure

Successful responses use the same top-level structure:

{
    "count": 0,
    "records": []
}

The fields inside each record differ between endpoints. Check the relevant guide before building your integration.

No Matching Records

An empty result is a successful response, not an API error.

For example, the Events API returns:

{
    "count": 0,
    "records": [],
    "message": "No current live events"
}

PHP Quick Start

This example retrieves events and checks that the response contains a valid records array.

<?php

$apiUrl = 'https://api.dabbble.app/v1/events';

$contents = @file_get_contents($apiUrl);

$data = $contents !== false
    ? json_decode($contents, true)
    : null;

if (
    !is_array($data)
    || isset($data['error'])
    || !isset($data['records'])
    || !is_array($data['records'])
) {
    echo 'Unable to load events.';
    return;
}

$records = $data['records'];

if ($records === []) {
    echo htmlspecialchars(
        $data['message'] ?? 'No current live events',
        ENT_QUOTES | ENT_SUBSTITUTE,
        'UTF-8'
    );

    return;
}

foreach ($records as $record) {
    echo '<p>' . htmlspecialchars(
        $record['title'] ?? '',
        ENT_QUOTES | ENT_SUBSTITUTE,
        'UTF-8'
    ) . '</p>';
}
?>

Change the endpoint to /v1/worktasters to retrieve opportunities instead.

Working with the Data

Check each endpoint’s documentation for field types and missing-value handling.

• Some unavailable fields return null.
• Other unavailable fields return the string "None".
• Descriptions contain HTML-formatted text.
• Dates use day/month/year order.
• Date-time strings do not include a timezone or UTC offset.
• Parse formatted dates before applying your own chronological sorting.

Prefer a Ready-Made Display?

Use a website embed if you want DABBBLE cards without building your own interface.

• Worktaster Embed: responsive opportunity cards, sorted by application deadline.
• Events Embed: responsive event cards, sorted by start date.

Both support organisation filtering and include copy-ready iframe examples.

More APIs

Additional v1 endpoints will appear here as they become available.

Return to the documentation home