Ryan_Coleman

Notary Professional Identify Field not found error

0 votes

Guys,

We have a backup account that is not tied to a vault for testing. We've been told that one account that we are using for a notary has been set up correctly but when I try to update the professional identity fields for that user, I get this error.

  { "messageKey": "error.validation.professionalIdentityField.notFound", "technical": "Professional identity field does not exist.", "message": "Professional identity field does not exist.", "code": 400, "name": "Validation Error" }

This functionality works just fine in our regular sandbox environment but does not work in our backup sandbox environment. Now the funny thing is, the field that is causing the problems is the field called "SEAL", which if you look at the user, has that field. Am I missing something or is there a possibility that this user is not set up correctly?

Reply to: Notary Professional Identify Field not found error

0 votes

Hi Ryan,

 

Are you trying to update the notary fields with below API and get a 400 "notFound" error?

 

POST /api/account/senders/{senderId}

{
  "professionalIdentityFields": [
    {
      "id": "SEAL",
      "value": "changed value"
    }
  ]
}

 

If that's the case, can you share the emails of your regular as well as the backup accounts to [email protected], so that I can check the account settings with support for you.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Notary Professional Identify Field not found error

0 votes

Yes, it is coming back as a 400. I'll send you an email.


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off