How to validate addresses before submitting API requests
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?
Answers
-
Hi @Connor VeryConnect I'm checking with my team to see if there is any help we can provide here.
0 -
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.
0 -
@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
0 -
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
0
Categories
- All Categories
- 6 Blackbaud Community Help
- 213 bbcon®
- 1.4K Blackbaud Altru®
- 403 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 1.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- 15 donorCentrics®
- 360 Blackbaud eTapestry®
- 2.6K Blackbaud Financial Edge NXT®
- 656 Blackbaud Grantmaking™
- 576 Blackbaud Education Management Solutions for Higher Education
- 3.2K Blackbaud Education Management Solutions for K-12 Schools
- 939 Blackbaud Luminate Online® and Blackbaud TeamRaiser®
- 84 JustGiving® from Blackbaud®
- 6.6K Blackbaud Raiser's Edge NXT®
- 3.7K SKY Developer
- 248 ResearchPoint™
- 119 Blackbaud Tuition Management™
- 165 Organizational Best Practices
- 241 Member Lounge (Just for Fun)
- 34 Blackbaud Community Challenges
- 34 PowerUp Challenges
- 3 (Open) PowerUp Challenge: Chat for Blackbaud AI
- 3 (Closed) PowerUp Challenge: Data Health
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Product Update Briefing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports+
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Email Marketing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Gift Management
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Event Management
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Home Page
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Query
- 793 Community News
- 2.9K Jobs Board
- 54 Blackbaud SKY® Reporting Announcements
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)


