Your API Docs Shouldn't Include Fake Addresses
When location API docs are published in Zeplin, Notis validates all mock address examples. Developers get real, valid data for testing and integration.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Validate Address
Tool to validate and standardize addresses. Use when you need detailed parsing, geocode, and deliverability verdict of an address.
Why this helps
API documentation includes mock response examples with placeholder addresses. Developers copy those into tests, then hit issues with validation or formatting. Bad mock data propagates into production code.
- Real mock data in API docs
- Fewer developer-side validation bugs
- Better integration outcomes
Setup
Build it in a few focused steps.
- 1Connect Zeplin and Google Address Validation to Notis.
- 2Ask Notis: "Before publishing location API documentation in Zeplin, validate all mock address examples to ensure they're real and correctly formatted."
- 3Trigger via webhook when docs are marked ready to publish.
- 4Get validation results before the docs go live.
- 5Test with an API doc section and verify mock addresses are validated.
Questions about this workflow
Should mock data be anonymized for privacy?
You can use real-but-public addresses like landmarks or commercial locations. Notis validates real data; you handle privacy guidelines.
Can I mark certain mock addresses as 'approved'?
Yes. Notis can keep a list of pre-approved addresses for repeated use in docs.
What if a mock address needs to stay fictional for security testing?
You can exclude specific examples from validation or add explanatory notes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zeplin to Google address validation. A trigger fires from one place; an action lands in another.
Zeplin triggers
Google address validation actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Provide Validation Feedback
Tool to provide feedback on an address validation attempt. Use after completing an address validation sequence.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Validate Address
Tool to validate and standardize addresses. Use when you need detailed parsing, geocode, and deliverability verdict of an address.
Connect any two apps with Notis in the middle.
Zeplin and Google address validation, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Google address validation.