Authentication

API key (server integrations)

Almost all /v1/* endpoints use:

Authorization: Bearer <API_KEY>

API keys are secrets — store them in environment variables, never commit them to git, and rotate from the dashboard if leaked.

JWT (dashboard)

Email/password login returns a JWT for the dashboard UI. Your backend integrations should use an API key, not a user JWT.

Related endpoints

• POST /auth/register — register
• POST /auth/login — dashboard login
• POST /v1/api-key/rotate — rotate API key (auth required)
• GET /v1/me — tenant info

Example

export WAPEDIA_API_KEY="wapedia_..."

curl "https://api.wapedia.id/v1/wallet/pricing" \
  -H "Authorization: Bearer $WAPEDIA_API_KEY"

OpenAPI: openapi.json (GET /v1/openapi.json on the API).