Base64 image deprecation — migration guide

Last updated: June 1, 2026

A complete field-by-field reference to help you migrate from base64-encoded images to signed S3 URLs.

What's changing

Starting June 15th, 2026, we will be deprecating base64-encoded images from our API payloads. The fields that currently return base64 data will instead return signed S3 URLs. The overall structure of the payload remains unchanged — only the content of these specific fields is affected.

The field names stay the same. What changes is the value — from a base64-encoded string to a signed S3 URL.

Affected fields

The following fields are affected across two response paths. Both follow the same mapping.

Under response.id_info.lookup_details.lookup_list[*].lookup_data

Deprecated field

New field

.user_photo

.user_photo_s3_url

.user_signature

.user_signature_s3_url

.signature

.signature_s3_url

.document

.document_s3_url

.issue_signature

.issue_signature_s3_url

.probationary_document

.probationary_document_s3_url

Under response.lookup_info[*].data.lookup_data

Deprecated field

New field

.user_photo

.user_photo_s3_url

.user_signature

.user_signature_s3_url

.signature

.signature_s3_url

.document

.document_s3_url

.issue_signature

.issue_signature_s3_url

.probationary_document

.probationary_document_s3_url

What you need to do

If your integration currently processes base64 data from any of the fields listed above, update your implementation to handle signed URLs instead. We recommend completing this migration well before the June 15th cutoff to avoid any disruptions.

Need help?

If you have any questions or need support with the migration, feel free to reach out to us at support@aiprise.com.