Changelog

​

Breaking changes

​

Improved

• More social media link formats. Social media link imports now accept shortened and mobile links. That includes vm.tiktok.com, vt.tiktok.com, tiktok.com/t/, fb.me, and instagram.com/share/ links, mobile hosts such as mobile.twitter.com, m.tiktok.com, and web.facebook.com, and Threads share links.

​

Fixed

• More reliable presigned uploads. A presigned URL could stop working minutes after it was requested, before the lifetime it was given, because it was signed with credentials that were about to expire. These URLs now stay valid for the lifetime they were issued with.

​

Breaking changes

​

Improved

• Image support for social media links. Social media link imports now download and analyze images, not just videos. Image scans are supported only for public posts on X, Facebook, Instagram, and Threads. For posts with multiple images, only the first image is analyzed. Mobile and shortened links aren’t supported yet.

​

Fixed

• Social media imports no longer stall. Imports that could stay in a downloading state indefinitely now time out. A timed-out import returns DOWNLOAD_FAILED in overallStatus, and socialLinkDownloadFailed is true.

​

Breaking changes

• Presigned uploads use a new domain. The signedUrl returned by POST /api/files/aws-presigned now points to api.prd.realitydefender.xyz instead of AWS S3. If your network or client restricts which hosts it can upload to, allow api.prd.realitydefender.xyz. The official SDKs already use this flow, so no code change is needed if you use one. If you upload with your own HTTP client, send a PUT request to the signedUrl exactly as returned, with the file as the raw request body and a Content-Type: application/octet-stream header.

​

Improved

• 30-minute limit on video. Video files longer than 30 minutes are no longer analyzed. Split longer recordings into segments of 30 minutes or less before uploading. Media Detail returns a not-applicable result instead of a processing error. overallStatus and resultsSummary.status are both NOT_APPLICABLE. resultsSummary.metadata.reasons contains:

"reasons": [
  {
    "code": "duration: video too long",
    "type": "Not applicable",
    "name": "Video too long",
    "explanation": "Videos longer than 30 minutes are not analyzed. Trim the video to 30 minutes or less and try again.",
    "rawReason": "duration: video too long"
  }
]

• Context-aware explainability fields withheld. Media Detail still returns the image or video context model. Its data keeps score and decision. The sources field remains only when reverse-image results are already included. These undocumented fields are omitted: explanation, image_description, manipulation_reasons, potential_source, image_type, and recognizable_identities. aggregation.json for scans run after this change omits contextResult. Files written earlier still include it. If your integration reads those fields, use the documented response fields only.
• Faster video results. Video analysis now completes about twice as fast.
• Shorter queue times during busy periods. Video processing capacity now scales with demand.

​

Breaking changes

​

Changes to be aware of

• API keys and webhooks have their own pages. In the web app, API keys and webhooks are now separate pages in the main navigation, each with a tab per product. To manage RealScan keys, go to API keys > RealScan. To manage RealScan webhooks, go to Webhooks > RealScan.

​

Breaking changes

​

Improved

• Faster results for social media links that can’t be downloaded. When a submitted social media URL can never be downloaded, such as a post with no media attached or content that requires app-only access, the request now fails after the first confirmed error instead of retrying up to five times. You receive the failure result sooner. The set of links that fail is unchanged.