DocumentationExecution NetworkDeveloper Platform
AUTHENTICATION

Keep account sessions and application credentials separate.

Wallet-authenticated product actions and developer API requests use different credential contexts. That separation should remain explicit in both implementation and documentation.

CREDENTIALS

Use the credential that matches the surface.

Wallet session

Account-owned product actions tied to the connected wallet.

API Key

Programmatic developer access for external applications.

SECURITY

Treat API Keys as server-side secrets.

01

Create purpose-specific keys

Separate applications or environments when useful.

02

Use minimum scopes

Grant only permissions required by the integration.

03

Store server-side

Use backend environment variables or a secret manager.

04

Never expose privileged keys in browser code

Public frontend variables are not a secret store.

05

Rotate or revoke when needed

Replace credentials after exposure or when access changes.

ACCOUNT API

Current developer-account routes.

Developer profile
POST /api/developers
GET  /api/developers/me
API keys
POST   /api/developers/keys
GET    /api/developers/keys
DELETE /api/developers/keys/:keyId
POST   /api/developers/keys/:keyId/rotate