AI Audio Detection API

1. Obtain a Pre-signed Upload URL

Begin by requesting a pre-signed URL from the API. This URL allows you to securely upload your audio file to the storage server.

GET https://detect-audio.truthscan.com/get-presigned-url?file_name=example.mp3

Example Request

curl -X GET 'https://detect-audio.truthscan.com/get-presigned-url?file_name=example.mp3' \
--header 'apikey: YOUR API KEY GOES HERE'

Example Response

{
  "status": "success",
  "presigned_url": "https://audio-presigned-upload.ai-assets-cdn.com?file_name=581d47c7-3ef4-42af-88d9-6dab6bf69389_20250611-121955_example.mp3...",
  "file_path": "/uploads/581d47c7-3ef4-42af-88d9-6dab6bf69389_20250901-090201_example.mp3"
}

2. Upload the Audio

Use the provided 'presigned_url' to upload your audio via a PUT request. Ensure the correct content type is set according to your audio format.

Example Request

curl -X PUT 'https://audio-presigned-upload.ai-assets-cdn.com?file_name=581d47c7-3ef4-42af-88d9-6dab6bf69389_20250611-121955_example.mp3...' \
  --header 'Content-Type: audio/<FILE_FORMAT - mp3, wav, m4a, flac, ogg, mp4>' \
  --header 'x-amz-acl: private' \
  --data-binary '@example.mp3' # Attachment

Ensure that the file format remains consistent during the upload process. A successful upload will return a status code of 200.

3. Submit Audio for AI Detection

After uploading, submit the audio for AI detection by referencing the 'file_path' from the previous step.

POST https://detect-audio.truthscan.com/detect

Example Request

curl -X 'POST' \
  'https://detect-audio.truthscan.com/detect' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "key": "YOUR-API-KEY-GOES-HERE",
  "url": "<FILE_PATH>",
  "document_type": "Audio",
  "analyzeUpToSeconds": 60
}'

The 'FILE_PATH' refers to the path obtained from the response in the initial step, 'Obtain a Pre-signed Upload URL'.

Example Response

{
    "id": "77565038-9e3d-4e6a-8c80-e20785be5ee9",
    "status": "pending"
}

The response includes a unique ID for tracking the detection status.

"User verification failed" (403)

Cause: Invalid or expired API key

Solution:

1. Verify your API key is correct
2. Check if your API key is active in your account
3. Try regenerating your API key

"Not enough credits" (403)

Cause: Insufficient credits for audio processing

Solution:

1. Check your remaining credits using /check-user-credits
2. Purchase additional credits if needed
3. Use analyzeUpToSeconds to analyze less audio and consume fewer credits

"Unsupported file format" (400)

Cause: Unsupported or invalid audio format submitted

Solution:

1. Verify audio format is supported (MP3, WAV, M4A, FLAC, OGG, MP4)
2. Ensure the file is not corrupted
3. Check Content-Type header when uploading

"File too large" (400)

Cause: File size exceeds 100MB limit

Solution:

1. Compress or convert the audio to under 100MB
2. Check file size before uploading
3. Use more efficient formats like MP3 when possible

"Audio processing took too long"

Cause: Audio processing took too long or timeout occurred

Solution:

1. Try with a smaller audio file or shorter duration
2. Use analyzeUpToSeconds to analyze only the first seconds
3. Check if the service is experiencing high load
4. Retry the request after a few minutes

Status "failed" in /query response

Cause: Processing failed for various reasons

Solution:

1. Check if audio meets minimum requirements (1KB - 100MB)
2. Verify audio is in a supported format
3. Verify upload completed successfully before submitting for detection
4. Contact support if issue persists

"Audio upload failed" (403/400)

Cause: Invalid or expired pre-signed URL, or issues with storage server

Solution:

1. Ensure you use the pre-signed URL immediately after receiving it (may expire)
2. Verify Content-Type header is correct for audio format
3. Remove spaces from filename before uploading
4. Try generating a new pre-signed URL if the current one expired

"Invalid pre-signed URL" (400)

Cause: Filename with spaces or expired/corrupted pre-signed URL

Solution:

1. Remove all spaces from filename before requesting pre-signed URL
2. Use only alphanumeric characters, hyphens and underscores in filename
3. Generate a new pre-signed URL if needed