REST V2 Contact Email Addresses Opt Status Incorrect

API Q&A
1

When querying a specific customer via DataService EmailAddStatus, we are told the contact is opted in:

> $sdk->data()->query('EmailAddStatus',1000,0,['Email'=>'judy21214@gmail.com'],['LastClickDate','LastOpenDate','LastSentDate','Type'],'Id',true)
= [
    [
      "Type" => "SingleOptIn",
      "LastOpenDate" => DateTime @1771236017 {#8551
        date: 2026-02-16 10:00:17.0 UTC (+00:00),
      },
      "LastSentDate" => DateTime @1771235776 {#8555
        date: 2026-02-16 09:56:16.0 UTC (+00:00),
      },
    ],
  ]

When we fetch the contact via REST v2, we are told the contact is opted out:

> $sdk->restfulRequest('GET',$sdk->getBaseUrl().'/rest/v2/contacts/922493',['fields'=>'email_addresses'])
= [
    "id" => "922493",
    "family_name" => "Thigpen",
    "given_name" => "Judy",
    "email_addresses" => [
      [
        "email" => "judy21214@gmail.com",
        "field" => "EMAIL1",
        "opt_in_reason" => null,
        "is_opt_in" => false,
        "email_opt_status" => "NON_MARKETABLE",
      ],
    ],
  ]

When we fetch the contact via REST v1, we are told the contact is opted in:

$sdk->restfulRequest('GET',$sdk->getBaseUrl().'/rest/v1/contacts/922493')
= [
    "tag_ids" => [
      489,
      5466,
      5678,
      5960,
      6385,
      6387,
      6391,
      6409,
      6423,
      6449,
    ],
    "id" => 922493,
    "company" => null,
    "email_opted_in" => true,
    "email_status" => "SingleOptIn",
    "date_created" => "2026-02-12T18:58:30.000+0000",
    "last_updated" => "2026-02-15T17:32:46.000+0000",
    "ScoreValue" => null,
    "last_updated_utc_millis" => 1771176766048,
    "email_addresses" => [
      [
        "email" => "judy21214@gmail.com",
        "field" => "EMAIL1",
      ],
    ],

In the application, it is showing the contact as opted in:

image
image1754×556 53.5 KB

Is there a reason why V2 is reporting invalid information? I can provide app id if needed.

2

Hi @Timothy_Withers,

Thanks for flagging this, I’ll bring this up internally so we can investigate the discrepancy between XML-RPC/DataService, REST v1, and REST v2.

Could you please send me a DM with the app ID?

3

Hi @Timothy_Withers,

The issue with REST v2 showing incorrect opt-in status has been fixed. It should now match the app and the other APIs.

Thanks,
Omar