Skip to content

Latest commit

 

History

History
170 lines (121 loc) · 7.08 KB

api.md

File metadata and controls

170 lines (121 loc) · 7.08 KB
Raw

This is the API that is used by the Playdate console for things like fetching game updates, scoreboards, player details, etc. It is available under https://play.date/api/v2. All API endpoints require auth headers.

This list of endpoints was obtained by decompiling the Playdate Simulator app. Some haven't actually been seen in use, so they are only partially documented and there may be mistakes.

Endpoints

Method Path
POST /auth_echo/
GET /player/
GET /player/:playerId/
POST /player/avatar/
GET /games/scheduled/
GET /games/user/
GET /games/testing/
GET /games/system/
GET /games/purchased/
GET /games/catalog
GET /games/catalog/:idx
POST /games/:bundleId/purchase/
POST /games/:bundleId/purchase/confirm
GET /games/:bundleId/latest_build/
GET /games/:bundleId/boards/
GET /games/:bundleId/boards/:boardId/
POST /games/:bundleId/boards/:boardId/
GET /device/settings/

POST /auth_echo

Seems to just return whatever JSON body is sent to it.

GET /player

Returns the player profile for the user that owns the current access token.

GET /player/:playerId

Same as /player, but gets the player profile for another user, given their Player ID.

GET /games/scheduled

Returns an array of Schedule entries for any seasons that you have access to.

GET /games/user

Returns an array of Game entries for games that you have sideloaded.

GET /games/system

Returns an array of Game entries for additional system applications, such as Catalog.

GET /games/purchased

Returns an array of Game entries for games that you have purchased through Catalog.

GET /games/catalog

Returns an array of Catalog Game entries for games that are available through Catalog.

GET /games/catalog/:idx

Returns Catalog Game entry for a specific Catalog game.

POST /games/:bundleId/purchase/

Initiates the purchase flow for a game. Returns instructions for confirming the purchase on another device.

POST /games/:bundleId/purchase/confirm

Completes the purchase flor for a game.

GET /device/register/:serialNumber

If the device hasn't already been registered, returns a JSON containing its serial number and pin.

This endpoint requires an extra header:

Header Value
Idempotency-Key Random 16-character string. Allowed chars are 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz.

GET /device/register/:serialNumber/complete

Returns a JSON with the device's registered status, access token, and serial number. Access token will only be available on the first request to this endpoint after registering the device.

Schemas

Schedule

Key Type Detail
name string Schedule name (Season One is Season-001)
start_date string Schedule start datetime, formatted as E MMM d HH:mm:ss yyyy zzz (e.g. Mon Apr 18 00:00:00 2022 PDT)
start_date_timestamp number Schedule start as a UNIX timestamp
next_release_timestamp number Time of next scheduled release as a UNIX timestamp, can be null
ended boolean
games array Array of available Game entries

Game

Key Type Detail
name string Game name, will be displayed to the user
bundle_id string Reverse-domain formatted bundle ID (e.g com.jaames.playnote)
short_description string Few games currently have this (only seen on Flipper Lifter and Boogie Loops so far), often null
studio string Game's publisher/developer
has_newer_build boolean
decryption_key string Only present for purchased games, otherwise null. Unclear what this is actually used for - at the time of writing purchased games do not appear to be encrypted and the key changes on each request. Seems to be base64-encoded.
latest_build Build

Build

Key Type Detail
url string Web URL for the build's .zip file
is_beta boolean
version string Human-friendly version string, taken from the game's pdxinfo file
build_number number Incremental build number from the game's pdxinfo
filesize number .zip file size, in bytes
upzipped_filesize number Size of the .zip contents after decompression, in bytes

Catalog Game

Key Type Detail
name string Game name, will be displayed to the user
bundle_id string Reverse-domain formatted bundle ID (e.g com.jaames.playnote)
studio string Game's publisher/developer
description string Game's description
detail_url string Path for this game's /games/catalog/:idx endpoint
price number Price in USD
header_image string Path to .pdi image file
list_image_size string "small"
list_image string Path to .pdi image file
animation_frame_duration unknown Seen as null
animation_frame_timing unknown Seen as null
accessibility string Game accessibility information
rating string Game age rating
screenshots Catalog Screenshot[] Game screenshots
build_size string Download size, e.g. "22.8 MB"
published_date string
updated_date string
authorized boolean
purchasable boolean
short_description string
web_url string URL for this game on the Catalog web storefront
purchase_url string Path for this game's /games/:bundleId/purchase/

Catalog Screenshot

Key Type Detail
url string Path to .pdi image file
frame_timing number[]

Auth Headers

All routes require a basic authorization token sent via a HTTP header.

Header Value
Authorization Token followed by your authorization token

Simulator Tokens

If you have a developer account on play.date, you can generate a simulator-only access token by going to https://play.date/players/account/ and clicking 'register simulator'. It looks as though you're allowed to register up to 5 simulators at one time. Note that this will be relatively limited, as the simulator cannot.

Player ID

Player IDs seem to use the DCE 1.1, ISO/IEC 11578:1996 variant of UUID v4, with dashes separating each section, e.g XXXXXXXX-XXXX-4XXX-8XXX-XXXXXXXXXXXX.