Deprecation Timeline

Following a timetable of the deprecation that will be introduced in the future and how to mitigate impacts on your integration.

Trustfull strives to maintain backward compatibility, so any change that could be considered breaking is always introduced to cover any blind spots in unintended use cases.

2026-10-19: DOMAIN REDIRECT SIGNALS

Announced on: 2026-04-19

The domain redirect signals are deprecated.

The change:

These signals are deprecated since 2026-10-19. They can still appear in the response, but we do not guarantee that they have a value.

Domain (Domain API and Get Domain API)

• website_redirect, website_redirect_to

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read one of these signals.

How to mitigate this situation:

• Remove these signals from your integration and from your rules.

2026-09-25: SNAPCHAT AND OPENAI SIGNALS

Announced on: 2026-03-25

The Snapchat and OpenAI signals are deprecated.

The change:

These signals are deprecated since 2026-09-25. They can still appear in the response, but we do not guarantee that they have a value.

Phone

• has_snapchat
• has_openai

Email

• has_openai, openai_login_provider

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read one of these signals.

How to mitigate this situation:

• Remove these signals from your integration and from your rules.

2026-07-31: DEVICE AND BROWSER API REMOVAL

Announced on: 2026-01-31

Device and browser API functionality was removed on 2026-07-31

The change:

Following the deprecation, the device and browser API were removed and are no longer available since 2026-07-31

Will this impact my API integration?

If you use the device or browser claim in your API integration, all calls fail.

How to mitigate this situation:

Reach out to your customer support specialist to better assess your use case and find a possible solution.

2026-07-31: MULTIPLE API REQUESTS WITH THE SAME CUSTOMER_ID

Announced on: 2026-01-31

Our identity document was never meant to contain a history of changes in the customer touchpoints.

Even a single new touchpoint could have a significant impact on the digital score.

The change:

In the API request, different touchpoint values are no longer supported for the same customer_id.

For this reason, we're now enforcing a new customer ID whenever we detect a change in previously collected data. This applies to all inputs.

Will this impact my API integration?

This change is possibly breaking for your integration if:

• You make multiple API calls with the same customer_id
• You change a previously submitted value

How to mitigate this situation:

• Don't update a previously submitted customer_id with new values, and generate a random customer ID for each new request.
• Whenever an update is necessary provide a new customer_id.

2026-06-09: WHATSAPP SIGNALS

Announced on: 2025-12-09

The WhatsApp profile and WhatsApp Business signals are deprecated.

The change:

These signals are deprecated since 2026-06-09. They can still appear in the response, but we do not guarantee that they have a value.

Phone

• whatsapp_image, whatsapp_privacy_status
• is_whatsapp_business, whatsapp_business_email, whatsapp_business_category, whatsapp_business_description, whatsapp_business_products_review_status, whatsapp_business_products_price_avg, whatsapp_business_products_price_std, whatsapp_business_products_currencies

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read one of these signals.

How to mitigate this situation:

• Remove these signals from your integration and from your rules.

2026-02-24: LINKEDIN PHONE SIGNAL

Announced on: 2025-08-24

The LinkedIn signal of the Phone product is deprecated.

The change:

This signal is deprecated since 2026-02-24. It can still appear in the response, but we do not guarantee that it has a value.

Phone

• has_linkedin

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read this signal.

How to mitigate this situation:

• Remove this signal from your integration and from your rules.

2026-01-05: SKYPE SIGNALS

Announced on: 2025-07-05

The Skype signals are deprecated.

The change:

These signals are deprecated since 2026-01-05. They can still appear in the response, but we do not guarantee that they have a value.

Phone

• has_skype, skype_profile_picture, skype_city, skype_country_code, skype_country, skype_state, skype_name, skype_id

Email

• has_skype, skype_profile_picture, skype_city, skype_country_code, skype_country, skype_state, skype_name, skype_id

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read one of these signals.

How to mitigate this situation:

• Remove these signals from your integration and from your rules.

2025-12-10: REVERSE IMAGE SEARCH SIGNALS

Announced on: 2025-06-10

The reverse image search signals are deprecated.

The change:

These signals are deprecated since 2025-12-10. They can still appear in the response, but we do not guarantee that they have a value.

Phone

• has_image_reverse_search, image_reverse_search, image_reverse_search_source, image2_reverse_search, image2_reverse_search_source, image3_reverse_search, image3_reverse_search_source

Email

• has_image_reverse_search, image_reverse_search, image_reverse_search_source, image2_reverse_search, image2_reverse_search_source, image3_reverse_search, image3_reverse_search_source

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read one of these signals.

How to mitigate this situation:

• Remove these signals from your integration and from your rules.

2025-11-10: BUKALAPAK SIGNALS

Announced on: 2025-05-10

The Bukalapak signals are deprecated.

The change:

These signals are deprecated since 2025-11-10. They can still appear in the response, but we do not guarantee that they have a value.

Phone

• has_bukalapak, bukalapak_has_whatsapp_otp

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read one of these signals.

How to mitigate this situation:

• Remove these signals from your integration and from your rules.

2025-08-21: IDENTITY DEVICE COUNT SIGNAL

Announced on: 2025-02-21

The identity_device_count signal is deprecated.

The change:

This signal is deprecated since 2025-08-21. It can still appear in the response, but we do not guarantee that it has a value.

Phone

• identity_device_count

Email

• identity_device_count

IP

• identity_device_count

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read this signal.

How to mitigate this situation:

• Remove this signal from your integration and from your rules.

2025-07-21: EDUCATION SIGNAL

Announced on: 2025-01-21

The education signal is deprecated.

The change:

This signal is deprecated since 2025-07-21. It can still appear in the response, but we do not guarantee that it has a value.

Email

• education

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read this signal.

How to mitigate this situation:

• Remove this signal from your integration and from your rules.

2025-06-16: EBAY SIGNAL

Announced on: 2024-12-16

The eBay signal is deprecated.

The change:

This signal is deprecated since 2025-06-16. It can still appear in the response, but we do not guarantee that it has a value.

Email

• has_ebay

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read this signal.

How to mitigate this situation:

• Remove this signal from your integration and from your rules.

2025-04-14: BINANCE SIGNAL

Announced on: 2024-10-14

The Binance signal is deprecated.

The change:

This signal is deprecated since 2025-04-14. It can still appear in the response, but we do not guarantee that it has a value.

Email

• has_binance

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read this signal.

How to mitigate this situation:

• Remove this signal from your integration and from your rules.

2025-03-31: WEBHOOK REMOVAL

Announced on: 2024-09-30

After the deprecation of the webhook functionality in 2024 we reached the EOL for this feature.

The change:

After moving to a sync API integration, the webhook was left only to support some customers who were still using this integration method. Now, all customers need to look at the API response rather than resorting to the webhook functionality.

Will this impact my API integration?

If you're relying on the webhook to receive data you don't receive any data points on the provided endpoint, and the API returns status code 400 when passing the webhook URL.

How to mitigate this situation:

Since the webhook was available when calling the sync API endpoint rather than discarding the API response you can just look at the response and store the data.

Alternatively, you can wait for the API response and then forward the response to your webhook endpoint.

Please note that you need to remove the webhook endpoint from the call parameters.

2025-03-06: BOOKING SIGNAL

Announced on: 2024-09-06

The Booking signal is deprecated.

The change:

This signal is deprecated since 2025-03-06. It can still appear in the response, but we do not guarantee that it has a value.

Email

• has_booking

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read this signal.

How to mitigate this situation:

• Remove this signal from your integration and from your rules.

2025-01-29: JS-SDK REMOVAL

Announced on: 2024-07-29

Following our deprecation schedule, since 2025-01-29 we no longer support the collection of data via the JS-SDK for the onboarding solution or onboarding related product.

The change:

The JS-SDK and the connected endpoints were disabled.

Will this impact my API integration?

If you are using the JS-SDK as data collection you cannot see any data in the platform.

How to mitigate this situation:

Move to API integration, to know more about how to perform an API call to Trustfull's onboarding solution you can go here: API REFERENCE

2024-12-12: SAMSUNG SIGNAL

Announced on: 2024-06-12

The Samsung signal is deprecated.

The change:

This signal is deprecated since 2024-12-12. It can still appear in the response, but we do not guarantee that it has a value.

Email

• has_samsung

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read this signal.

How to mitigate this situation:

• Remove this signal from your integration and from your rules.

2024-09-14: VPN NAME SIGNAL

Announced on: 2024-03-14

The VPN name signal is deprecated.

The change:

This signal is deprecated since 2024-09-14. It can still appear in the response, but we do not guarantee that it has a value.

IP

• vpn_name

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read this signal.

How to mitigate this situation:

• Remove this signal from your integration and from your rules.

2024-06-06: FACEBOOK NAME SIGNALS

Announced on: 2023-12-06

The Facebook signals of the Name product are deprecated.

The change:

These signals are deprecated since 2024-06-06. They can still appear in the response, but we do not guarantee that they have a value.

Name

• has_facebook, facebook_avatar_url

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read one of these signals.

How to mitigate this situation:

• Remove these signals from your integration and from your rules.

2024-06-01: PROFILE INTEGRATION

Announced on: 2023-12-01

Following our deprecation plan for the customer_id identity merge. We no longer support multiple calls on the same customer_id even in the form of a profile integration.

What is a profile integration?

Profile integration is when an API request is sent to our system with a subset of data.

API CALL 1 -> customer_id_000 + PHONE + EMAIL

API CALL 2 -> customer_id_000 + IP

Before this change, we merged the two requests into the same customer_id (in this case customer_id_000)

Resulting in an identity with PHONE + EMAIL + IP

The change:

In the API request, multiple subsequent calls with the same customer_id are not supported.

For this reason, we're now enforcing a new customer ID for every API call.

Profile integration was deprecated and removed on 2024-06-01.

Since the removal date, you receive a 400 BAD REQUEST.

Will this impact my API integration?

This change is possibly breaking for your integration if:

• You make multiple API calls with the same customer_id and incrementally provide products.

How to mitigate this situation:

• Whenever a profile integration is necessary provide a new customer_id

2024-05-21: EMAIL ROLE SIGNAL

Announced on: 2023-11-21

The email role signal is deprecated.

The change:

This signal is deprecated since 2024-05-21. It can still appear in the response, but we do not guarantee that it has a value.

Email

• is_role

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read this signal.

How to mitigate this situation:

• Remove this signal from your integration and from your rules.

2024-05-01: PHONE API WITH FIXED_LINE/LANDLINE

Announced on: 2023-11-01

Calls made to fixed lines using our Phone API are rejected by the system.

The change:

Trustfull prioritizes the digital footprint and online presence, and fixed lines do not offer the meaningful information required to accurately assess an identity's quality.

{
"status": "ko",
"message": "Landline are not supported for the phone api. Only mobile phone numbers are supported for scoring and enrichment. If you call the onboarding solution you can retry this call by removing the phone claim and phone_number from the call",
"errors": {"phone_number": "..."}
}

Will this impact my API integration?

• Your integration is affected if you call the phone API or the onboarding solution with a fixed line or landline number

How to mitigate this situation:

Whenever you receive this error you can retry the call removing the phone claim and the phone_number. If the API call is specific to the "phone" product there is no mitigation.

2024-04-01: MULTIPLE CLAIMS WITHOUT "SCORE"

Announced on: 2023-10-01

A call with multiple claims without the claim score is no longer supported.

The change:

An example of such a call is:

{
  "customer_id":"...",
  "email": "...",
  "phone_number": "...",
  "claims": [
     "phone",
     "email"
  ]
}

Will this impact my API integration?

This change is possibly breaking for your integration if:

• You make a call to individual products bundled in a single API call.

How to mitigate this situation:

There are two possible ways to mitigate this change:

1. Use the claim 'score'. The resulting call will be similar to :

{
  "customer_id":"...",
  "email": "...",
  "phone_number": "...",
  "claims": [
     "phone",
     "email",
     "score"
  ]
}

2. Make two separate calls

Call 1: This is a call to the PHONE API:

{
  "customer_id":"...",
  "phone_number": "...",
  "claims": [
     "phone"
  ]
}

Call 2: This is a call to the EMAIL API:

{
  "customer_id":"...",
  "email": "...",
  "claims": [
     "email"
  ]
}

2024-01-08: PHONE STATUS SIGNALS

Announced on: 2023-07-08

The phone connection status signals are deprecated.

The change:

These signals are deprecated since 2024-01-08. They can still appear in the response, but we do not guarantee that they have a value.

Phone

• status, is_valid

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read one of these signals.

How to mitigate this situation:

• Use score or score_cluster. A score below 450 (cluster poor or bad) means that the phone number is likely not connected. A score of 450 or more (cluster moderate, good or high) means that it is likely connected.

2023-10-09: PHONE TYPE SIGNAL

Announced on: 2023-04-09

The phone type signal is deprecated.

The change:

This signal is deprecated since 2023-10-09. It can still appear in the response, but we do not guarantee that it has a value.

Phone

• type

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read this signal.

How to mitigate this situation:

• Use number_type.

2023-08-07: AIRBNB SIGNAL

Announced on: 2023-02-07

The Airbnb signal is deprecated.

The change:

This signal is deprecated since 2023-08-07. It can still appear in the response, but we do not guarantee that it has a value.

Email

• has_airbnb

Will this impact my API integration?

This change is possibly breaking for your integration if your code or your rules read this signal.

How to mitigate this situation:

• Remove this signal from your integration and from your rules.