Authentication & API Keys

Most DappScore API endpoints are public and require no credentials. You only need an API key for write operations (e.g. updating token sale progress) or managing webhooks programmatically.


Managing Keys via the Dashboard

The easiest way to create and manage API keys is through the web app — no code required:

  1. Click the API Keys tab

  2. Hit New Key, choose a name and permissions, and optionally scope it to a project

The full key is displayed once after creation (with a copy button). After that, only the prefix is shown. Use Rotate to replace a lost key or Revoke to permanently disable one.

For scripting, CI/CD pipelines, or bulk operations, use the API endpoints below.


How Authentication Works

All API key endpoints require your wallet address in the x-user-id header. This is how the API identifies you as the owner of the keys you're managing.

-H "x-user-id: 0xYourWalletAddress"

Once you have a key, authenticated endpoints use a standard Bearer token:

-H "Authorization: Bearer sk_test_..."

Creating an API Key

Request body:

Field
Required
Description

name

Yes

A label for this key (max 100 chars)

permissions

Yes

Array of permissions (see below)

projectId

No

Scope the key to a specific contract address

Response (key shown once only):

circle-exclamation

You can have up to 10 active keys per wallet.


Permissions

Permission
What it allows

sale:write

Create and update token sale progress for your project

webhooks:manage

Register, update, and delete webhooks via API

data:read

Read-only access to project and analytics data


Using a Key

Pass your key as a Bearer token:


Managing Your Keys

List all your keys (secret values are never returned, only the prefix):

Rename a key:

Rotate a key (atomically revokes the old one and issues a new key with the same settings):

Revoke a key (permanent):

Last updated