Skip to main content

Authentication

FYATU API v3 uses JWT (JSON Web Tokens) for secure, stateless authentication. Exchange your app credentials for a short-lived access token, then use that token to authenticate all subsequent requests.

Overview

Getting Your Credentials

1

Login to FYATU

Go to FYATU Dashboard and login to your account
2

Open Business Console

Navigate to the Business Console from your dashboard
3

Select Your App

Click on your Collection App or Issuing App depending on which APIs you need
4

Get API Keys

Go to Settings tab, then click API Keys & Credentials

App Types & Scopes

Your access token’s scopes depend on the app type:

Token Lifecycle

Step 1: Obtain Access Token

Exchange your app credentials for a JWT access token:

Response

Step 2: Use Token in Requests

Include the access token in the Authorization header for all API requests:

Step 3: Refresh Token (Optional)

Before your token expires, you can refresh it to get a new token. Refresh is allowed up to 5 minutes after expiry.

Response

Error Responses

Invalid Credentials

Token Expired

Insufficient Scope

JWT Payload Structure

When decoded, the JWT token contains:

Best Practices

  • Store tokens securely in memory or encrypted storage
  • Never expose tokens in client-side code or logs
  • Implement automatic token refresh before expiry
  • Check token expiry before each request
  • Refresh when less than 5 minutes remain
  • Handle refresh failures by re-authenticating
  • Catch 401 errors and re-authenticate
  • Catch 403 errors and check required scopes
  • Log request IDs for debugging with FYATU support

Rate Limits

Authentication endpoints have the following rate limits:
Exceeding rate limits will result in a 429 Too Many Requests response. Implement exponential backoff in your retry logic.