Skip to main content
GET
/
firehose
Test firehose's ability to write to AWS S3 or Azure Blob Storage
curl --request GET \
  --url https://app.leadconduit.com/firehose \
  --header 'Authorization: Basic <encoded-value>'
{
  "validated": true,
  "verification_file": true
}

Documentation Index

Fetch the complete documentation index at: https://developers.activeprospect.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

Authorization
string
header
required

LeadConduit uses HTTP Basic Authentication with the username API and your API key as the password.

For example: API:1f1b96c9150d8050e858c043d543bb4eadae0e6f'

Query Parameters

service
enum<string>
default:aws

Cloud service provider. Defaults to 'aws' if not specified.

Available options:
aws,
azure
access_key_id
string

AWS Access Key ID for S3 authentication. Required when service is 'aws' or not specified.

secret_access_key
string

AWS Secret Access Key for S3 authentication. Required when service is 'aws' or not specified.

connection_string
string

Azure Storage account connection string for Blob Storage authentication. Required when service is 'azure'.

bucket
string
required

Storage container name. For AWS: S3 bucket name. For Azure: Blob Storage container name.

Required string length: 3 - 63
Pattern: ^[a-z0-9]([a-z0-9\-]*[a-z0-9])?$
prefix
string

Optional path prefix for stored files.

  • For AWS: Files will be stored as <prefix>/leadconduit_verification_[flow_id_]YYYYMMDDHHMMSSMS.txt
  • For Azure: Currently not used in validation but stored for future use
flow_id
string

Optional flow identifier to include in verification filename. When provided, filename becomes: leadconduit_verification_{flow_id}_{timestamp}.txt When omitted, filename becomes: leadconduit_verification_{timestamp}.txt

verification_file
enum<string>
default:true

Whether to create the verification file during validation.

  • true (default): Creates verification file and validates credentials
  • false: Only validates credentials/permissions without creating file For AWS: uses headBucket operation instead of putObject when false For Azure: skips file upload step when false
Available options:
true,
false

Response

Credentials validation successful

Standardized response for both AWS S3 and Azure Blob Storage validation

validated
boolean
required

Indicates successful credential validation

Example:

true

verification_file
boolean
required

Indicates whether a verification file was created during validation