Logo GenukaGenuka Pay
Guides

Manage API Keys

Manage your Genuka Pay application credentials safely from the dashboard and operational workflows.

Introduction

Genuka Pay is designed to be managed from the dashboard first, not by pasting raw credentials into ad hoc scripts.

Reveal Credentials

Inspect your current application keys from the protected dashboard flow.

Operational Review

Review recent rotations and application activity before changing live credentials.

Rotate Secrets

Rotate secrets intentionally when exposure, access, or deployment context changes.

Dashboard Entry Point

Open the API Keys page from the dashboard.

Use this page to:

  • viewing the public_key
  • revealing or hiding the secret_key
  • copying credentials safely
  • rotating the secret key
  • reviewing key history and recent activity
  1. copy the current secret_key
  2. store it in your backend environment variables or secrets manager
  3. keep the key server-side only
  4. rotate it when access changes or you suspect the key may have been exposed

Headers Used With the Key

Authenticated Request Headers
X-Public-Key: YOUR_PUBLIC_KEY
X-Timestamp: UNIX_TIMESTAMP
X-Signature: HMAC_SHA256_SIGNATURE

Accepted environment values are SANDBOX and LIVE.

Rotation

Rotating from the API Keys page generates a new secret_key and replaces the old one immediately: there is no grace period, and requests signed with the old secret fail with 401 from that moment. The public_key stays the same. Each environment (SANDBOX, LIVE) has its own key pair and is rotated separately.

Secret keys start with sk_test_ in sandbox and sk_live_ in live; public keys with pk_test_ and pk_live_.

No API Endpoint for Keys

The /api/v1/application endpoints used by the dashboard only accept the dashboard session: they cannot be called with an API key. Manage keys from the dashboard.

Environment Guidance

  • use SANDBOX for testing and staging
  • use LIVE only for production traffic
  • do not mix webhook receivers across environments
  • verify the selected environment before rotating or distributing a key

Security rule

Never place the secret key in browser code, static assets, mobile apps, screenshots, public repositories, or support tickets.

Operational Checklist

  • store secrets in a secure backend-only location
  • limit which services can read them
  • rotate when access changes
  • validate production traffic after every rotation
  • keep deployment runbooks in sync with key management procedures

How is this guide?

Last updated on