Copy page

Floqast

Audit Logs

Ingests audit trail events from FloQast for monitoring API key activity and security events.

Sync Type: Incremental

Requirements

Before connecting Monad to FloQast, you need:

1. FloQast Account with API Access

   • Log in to your FloQast application
   • Navigate to Settings > API Keys

2. FloQast API Key

   • Must be generated by a user with permission to manage API keys in your FloQast organization
   • Instructions: FloQast API Keys

3. Data Residency Region

   • Know the region where your FloQast organization is hosted (US, EU, or AU)
   • Each region has a separate endpoint; data from one region is not accessible via another region's endpoint

Creating a FloQast API Key

1. Log in to your FloQast application
2. Navigate to Settings > API Keys
3. Click Create API Key (or equivalent button)
4. Provide a descriptive name (e.g., "Monad Audit Logs")
5. Copy the generated API key and store it securely

Configuration

The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.

Settings

Setting	Type	Required	Default	Description
Region	string	Yes	-	FloQast data residency region. Select the region where your FloQast organization is hosted (us, eu, or au). Data is region-specific and cannot be accessed across regions.
Backfill Start Time	string	No	Current time	The date to start fetching data from in RFC3339 format (e.g., 2024-01-01T00:00:00Z). If not specified, no past records will be fetched.
API Rate Limit	object	No	-	Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See API Rate Limiting for the field format, limits, and how to choose a value.

Secrets

Secret	Type	Required	Description
API Key	string	Yes	FloQast API key. Generate it in the FloQast application under Settings > API Keys. Sent as the x-api-key request header.

Rate Limits

FloQast does not publish rate limits in their public API documentation. The connector implements a conservative rate limit of 10 requests per second to avoid throttling.

If rate limits are encountered:

• The connector will log rate limit errors
• Automatic retry with exponential backoff may occur depending on HTTP status codes
• Contact FloQast support for clarification on your account's rate limits

Source: FloQast API Documentation — Rate limits not specified

Troubleshooting

Authentication Failures (401 Unauthorized)

Symptoms: Error message indicating unauthorized access

Causes:

• Invalid or expired API key
• API key has been revoked

Solutions:

• Verify the API key is correct and properly copied without leading/trailing whitespace
• Check that the API key has not been revoked in FloQast
• Generate a new API key if necessary

Wrong Region Selected

Symptoms: Empty results or connection errors despite valid credentials

Causes:

• The selected region does not match the region where your FloQast organization is hosted

Solutions:

• Confirm your FloQast organization's data residency region with your FloQast administrator
• Update the Region setting to the correct value (us, eu, or au)
• Note that FloQast data is strictly region-specific; US data is only available from the US endpoint

No Data Appearing

Symptoms: Connector runs successfully but no events are collected

Causes:

• No API key activity occurred during the specified timeframe
• Backfill Start Time is set to a time with no audit events

Solutions:

• Verify that API key activity exists in FloQast for the target time range
• Check that Backfill Start Time is not set further in the past than FloQast's data retention period
• Contact FloQast support to confirm audit trail availability for your account

Invalid Backfill Start Time

Symptoms: Validation error about backfill time format

Causes:

• Backfill time is not in RFC3339 format

Solutions:

• Use RFC3339 format: 2024-01-01T00:00:00Z
• Include a timezone designator (Z for UTC or an offset such as +05:00)

Related Articles

• FloQast Help Center
• FloQast Authentication

Sample Record

Code
{
  "_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "uri": "/api/v1/reconciliations",
  "method": "GET",
  "sourceIp": "203.0.113.42",
  "meta": {
    "status": "200",
    "service": "Reconciliations"
  },
  "userApiKey": {
    "_id": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
    "name": "Production Key"
  },
  "createdAt": "2026-05-05T12:34:56.000Z"
}