Documentation Index
Fetch the complete documentation index at: https://docs.fype.dev/llms.txt
Use this file to discover all available pages before exploring further.
Authentication & API Keys
Fype uses API keys to authenticate requests. You can manage your API keys in the Fype Dashboard.Key Types
Fype provides two environments for every merchant account: Test and Live.| Key Prefix | Environment | Purpose |
|---|---|---|
fype_test_ | Test | Development and testing using the Fype Simulator. No real money is moved. |
fype_live_ | Live | Production use with real payment gateways and real money. |
Authenticating Requests
All API requests must include your secret API key in theAuthorization HTTP header as a Bearer token.
Warning: Your secret API keys carry significant privileges. Keep them secure! Do not share them in publicly accessible areas such as GitHub, client-side code, or browsers.
Obtaining API Keys
- Sign up or log in to the Fype Dashboard.
- Go to Developers > API Keys.
- Toggle between Test and Live modes in the dashboard sidebar.
- Click Create Key to generate a new key for the selected environment.
- Copy the key immediately. For security reasons, the full key is only shown once.
Key Rotation
If an API key is compromised, you should revoke it immediately:- Go to the API Keys section in the dashboard.
- Find the key you wish to revoke.
- Click the Delete (Trash) icon.
- Once revoked, the key can no longer be used to authenticate requests.
- Generate a new key and update your application settings.
Environment Isolation
- Data created in Test mode is completely isolated from Live mode.
- Payments created with a
fype_test_key will only be visible in the Test dashboard and will only trigger Test webhooks. - You must configure separate Webhook Endpoints for Test and Live environments.