How to validate addresses before submitting API requests

Question

We are syncing some user data from our own platform to RE on behalf of a client. One of the fields we are trying to sync is the user's address.

We know we can use CreateConstituentAddress and EditConstituentAddress to copy data over, which works fine for some countries, but others have validation on what (e.g.) the state or county is allowed to be. I don't see those mappings in the documentation.

We've seen a "counties" code table, but that doesn't seem to quite match what we want.

How can I recreate the functionality of the "parish" dropdown for Jamaica, for example? Is ISO 3166-2 enough?

Alex Wong · Answer

in your screenshot, it looks to be the "state" section of an address (if United States). In other country that same code table is used to store "region".

You can try the "States" code table and see if it has the table entries values you would see in the dropdown, the code table id is 5049

Connor VeryConnect · Answer

@Alex Wong Thank you for your reply. I hope you enjoyed your holiday season. We are just now getting to look at this.

We did suspect that the data may be stored in a code table, but we can't find one that matches. I don't think adding a new code table entry would work for us — we're trying to replicate the behaviour the RE has, not change it at all.

With further experiments, we're quite confident that the validation is based on ISO 3166-2 Subdivisions, but we would like confirmation before starting our implementation.

Thank you

Alex Wong · Answer

you can use the get code table list endpoint to see all code table to find out which code table is the one matches.

once you know which code table, you can use the get table entries list endpoint to see all its values for you to do validation. If you can't find the right fit, you can programmatically add to the code table a new table entry for use in subsequent add/update address call.