Skip to main content

Overview

The Fentu FSM API uses token-based authentication. All API requests must include a valid authentication token in the request header.
Keep your API credentials secure. Never expose tokens in client-side code or public repositories.

Authentication Methods

API Key Authentication

For server-to-server integrations:

OAuth 2.0

For user-authorized applications:
  1. Redirect user to authorization endpoint
  2. User grants permission
  3. Receive authorization code
  4. Exchange code for access token
  5. Use access token for API requests

Obtaining Credentials

API Keys

1

Navigate to Settings

Go to Administration > Integrations > API
2

Create API Key

Click “Create API Key”
3

Set Permissions

Configure what the key can access
4

Copy Key

Save the generated key securely
API keys are shown only once when created. Store them securely immediately. If lost, you must create a new key.

OAuth Credentials

For OAuth applications:
  1. Register your application
  2. Receive client ID and secret
  3. Configure redirect URIs
  4. Implement OAuth flow

Making Authenticated Requests

Request Headers

Include the authentication header in all requests:

Example Request


Token Management

Token Expiration

Refreshing Tokens

For OAuth access tokens:

Revoking Tokens

To invalidate a token:

Permissions & Scopes

Available Scopes

Requesting Scopes

Include scopes in authorization request:

Error Handling

Authentication Errors

Error Response Format


Rate Limiting

Limits

Rate Limit Headers

Responses include rate limit information:

Handling Rate Limits

When rate limited:
  1. Check X-RateLimit-Reset header
  2. Wait until reset time
  3. Retry request
  4. Consider caching responses

Security Best Practices

Store credentials in secure vaults or environment variables. Never hardcode in source code.
Always use HTTPS for API requests. Never send credentials over unencrypted connections.
Request only the scopes you need. Don’t request admin access for read-only operations.
Periodically rotate API keys. Immediately revoke any compromised credentials.
Monitor API usage for unusual patterns. Investigate unexpected spikes.
Where possible, restrict API access to known IP addresses.

API Introduction

API overview

Work Orders API

Work order endpoints

Customers API

Customer endpoints

Integrations

Integration setup