Skip to main content
Dock API Bearer Auth Discord ↔ Roblox
Dock gives you a secure way to map Discord and Roblox accounts, manage linked records, and run PID-based verification flows for your own applications.

​
Welcome to Dock API

Dock is built for developers who need reliable account linking between Discord and Roblox. You can use Dock to fetch mappings, update linked identities, reset custom datasets, and power your own verification flows. All protected endpoints require Bearer token authentication.

API Base URL

Use https://api.docksys.xyz as the base URL for all Dock API requests.

Authentication

Every authenticated request must include your API key in the Authorization header.

​
Start a verification flow

To begin linking a Discord account to a Roblox account, direct the user to: 
https://api.docksys.xyz/v1/api/verify/discord
This route starts Dock’s verification flow. Add a pid when you want Dock to also write the verified pair into your application’s private dataset.

​
Public Identifier (PID)

If your app needs its own user records, append a Public Identifier (pid) to the Discord verification URL. The PID ties the verification flow back to the API key that owns it, allowing Dock to write the verified Discord ↔ Roblox pair into your private collection in addition to the guild database.
Dock uses the pid to associate the verification flow with your API key and store the verified pair in your PID-scoped dataset.
Generate or locate your PID from the developer dashboard when managing an API key.
Dock stores the pid in a secure cookie during the verification flow, associates the session with your API key, and updates your PID-scoped dataset after the Roblox callback completes.
The user can still verify for guild usage, but your personal database will not receive the update.

​
PID example

https://api.docksys.xyz/v1/api/verify/discord
If you omit the PID, verification can still succeed for shared guild usage, but Dock will not update your application’s private PID dataset.

​
Key features

Account mapping

Retrieve and manage mappings between Roblox IDs and Discord IDs inside specific guilds or PID-scoped datasets.

Link management

Update Discord IDs or Roblox IDs associated with existing linked records.

Database operations

Reset custom application datasets securely through authenticated endpoints.

Secure access

Protected operations require Bearer authentication so only authorized developers can access sensitive actions.

​
Authentication example

Send your API key in the Authorization header as a Bearer token. 
curl --request GET \
  --url "https://api.docksys.xyz/api/v1/public/roblox-to-discord?robloxId=12345&guildId=67890" \
  --header "Authorization: Bearer YOUR_TOKEN"
For full authentication details, token usage, and common error responses, see our Authentication Guide.

​
Quick start

1

Get your API key

Sign in through the developer dashboard and generate your Bearer token.
2

Choose your flow

Use the standard API endpoints for mapping and management, or use the verification flow when you need users to link accounts interactively.
3

Add your PID if needed

Include pid in the verification URL when your application needs its own private verified-user dataset.
4

Make your first request

Start with a simple mapping request, then explore the rest of the API reference as your integration grows.

Authentication

Learn how to authenticate every Dock request correctly.

Rate Limits

Understand quotas, retry timing, and shared-IP protection.

Verification Sessions

Build session-based verification flows with long-polling or SSE.