Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Help understanding error 400 on RecordingAPI

  • 1.  Help understanding error 400 on RecordingAPI

    Posted 06-05-2025 18:29

    marcoflps | 2024-01-12 19:06:57 UTC | #1

    Hi,

    I`m trying to run a scheduled job to export recordings to an external s3 bucket. When i execute method receive a bad request error but the log doesnt help me understand what the problem is

    can you help me?

    ERROR: Fri Jan 12 16:00:36 BRT 2024 === REQUEST === URL: https://api.mypurecloud.com/api/v2/recording/jobs Method: POST Headers: Authorization: [REDACTED] User-Agent: PureCloud SDK/java Accept: application/json purecloud-sdk: 198.1.0 Content-Type: application/json Body: {"action":"EXPORT","actionDate":"2024-01-12T19:00:35.375Z","integrationId":"88e100fd-edc1-4fc4-bdab-00d0989bf642","includeRecordingsWithSensitiveData":true,"includeScreenRecordings":true,"conversationQuery":{"conversationFilters":[],"segmentFilters":[],"evaluationFilters":[],"surveyFilters":[],"resolutionFilters":[],"order":"desc","orderBy":"conversationStart","interval":"2023-12-31T19:00:31.504Z/2023-12-01T19:00:31.504Z"}} === RESPONSE === Status: 400 Headers: X-Cache: Error from cloudfront Strict-Transport-Security: max-age=31536000; includeSubDomains Cache-Control: no-cache, no-store, must-revalidate X-Amz-Cf-Pop: GRU1-P3 Connection: keep-alive X-Amz-Cf-Id: zML-1DJgqeXSk0jbWffb7o8uWVDtI0aDdhmopPGfWgWtL47cipwg== Content-Length: 198 ININ-Correlation-Id: eb42f511-0479-47c7-be7a-49a949623a47 Date: Fri, 12 Jan 2024 19:00:36 GMT Content-Type: application/json Via: 1.1 c1ed9cbf35a32086c5b7f239370933a6.cloudfront.net (CloudFront) CorrelationId: eb42f511-0479-47c7-be7a-49a949623a47 Body: {"message":"The request could not be understood by the server due to malformed syntax.","code":"bad.request","status":400,"contextId":"eb42f511-0479-47c7-be7a-49a949623a47","details":[],"errors":[]}

    IntegrationsRUs | 2024-01-12 23:04:16 UTC | #2

    I am not sure if it is the root cause but it appears your Interval has the start after the end time.

    2023-12-31T19:00:31.504Z/2023-12-01T19:00:31.504Z

    Start = 2023-12-31T19:00:31.504Z End = 2023-12-01T19:00:31.504Z

    Try it with this interval 2023-12-01T19:00:31.504Z/2023-12-31T19:00:31.504Z

    system | 2024-02-12 23:05:08 UTC | #3

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 24103



Related Content