Interzoid is an AI-powered data quality, data matching, and data enrichment platform that provides real-time cloud APIs for cleansing, normalizing, standardizing, and enriching data across a wide range of domains—including names, addresses, phone numbers, companies, emails, and more. Interzoid's REST APIs use advanced machine learning and AI models to generate similarity match keys, verify contact information, and append enriched attributes to existing records, helping organizations improve data quality, reduce duplicate records, and increase the accuracy of their analytics and operational systems. A single API license key provides access to all Interzoid APIs.
Power end-to-end data operations for your Interzoid API with Nexla. Our bi-directional Interzoid connector is purpose-built for Interzoid, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Interzoid or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Interzoid workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
To connect Nexla to Interzoid, you need an active Interzoid account and an API license key. Interzoid offers a free trial with starting credits upon registration, so you can begin using the APIs immediately.
Once logged in, navigate to your account dashboard to locate your API license key.
Copy your API license key and store it securely. This key authenticates all API requests from Nexla to Interzoid services.
Your Interzoid API license key provides access to all Interzoid APIs—there is no need to generate separate keys for different endpoints. For complete information about API license keys and credit usage, refer to the Interzoid API License Keys documentation.
After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Interzoid API license key in the API Key field. This key is used to authenticate all requests that Nexla makes to the Interzoid API on your behalf. Your API license key can be found in your Interzoid account dashboard after logging in at https://www.interzoid.com.
Important
Keep your Interzoid API license key secure and do not share it publicly. Each API call made using your key consumes credits from your account balance. For information about monitoring remaining credits, refer to the Interzoid documentation.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation and can be selected for use with a new data source.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Interzoid connector tile, then select the credential that will be used to connect to the Interzoid API, and click Next; or, create a new Interzoid credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Interzoid endpoints. Each template is designed specifically for the corresponding Interzoid endpoint, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Company Name Matching
Matches and compares company names to identify similar or duplicate entries across datasets using Interzoid's advanced algorithm. Use this endpoint to generate similarity keys for company name deduplication and matching workflows.
Issues a GET request to the company match advanced endpoint, passing the company name and optional algorithm as query parameters.
Response data path: $ — the entire JSON response is treated as a single record containing the similarity key and match metadata. Configure the Company Name and Algorithm parameters.
Use a lookup-based macro to pass company name values from an upstream Nexset into this endpoint, enabling bulk company name deduplication across an entire dataset. Each API call consumes one API credit.
Convert Currency
Converts a monetary amount from one currency to another using current exchange rates. Use this endpoint to enrich financial data with real-time currency conversions as part of a Nexla data flow.
Issues a GET request to the currency conversion endpoint, passing the source currency, target currency, and amount as query parameters.
Response data path: $ — the entire JSON response object is treated as a single record. Configure the From Currency, To Currency, and Amount parameters.
Currency codes follow the ISO 4217 standard (e.g., USD, EUR, GBP). Use lookup-based macros to pass amounts and currency codes dynamically from an upstream financial dataset.
Address Similarity Key
Generates a similarity key for a street address to support fuzzy address matching and deduplication. Use this endpoint to standardize address data and identify duplicate records with variant address formats.
Issues a GET request to the address match endpoint, passing the street address as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the Address parameter with the street address to process.
Use a lookup-based macro to pass address values from an upstream Nexset to generate similarity keys in bulk. Records with identical similarity keys can be treated as potential duplicates for deduplication workflows.
Area Code Information
Returns city, state, and timezone metadata for a North American telephone area code. Use this endpoint to enrich contact or customer records with geographic data derived from phone area codes.
Issues a GET request to the area code information endpoint, passing the 3-digit area code as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the Area Code parameter.
This endpoint covers North American (NANP) area codes only. Use a lookup-based macro to process multiple area codes from an upstream Nexset in a single data flow.
City Name Similarity Key
Generates a similarity key for city names to support fuzzy city-level address matching. Use this endpoint to normalize variant city name spellings in address datasets.
Issues a GET request to the city match endpoint, passing the city name as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the City parameter.
City name similarity keys help identify records where the same city is spelled differently (e.g., "New York", "N.Y.", "NYC"). Combine with address and ZIP code endpoints for comprehensive address standardization.
Company Name Similarity Key (Standard)
Generates a similarity key for a company name using Interzoid's standard algorithm. Use this endpoint as a lightweight alternative to the advanced company matching endpoint when processing speed is a priority.
Issues a GET request to the standard company match endpoint, passing the company name as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the Company parameter.
The standard algorithm is faster but less precise than the advanced algorithm. Use it for large-scale initial deduplication passes, and the advanced endpoint for detailed matching on smaller datasets.
Currency Exchange Rate
Returns the current exchange rate between two currencies without applying a conversion. Use this endpoint to retrieve live exchange rate data for financial reporting or pricing calculations.
Issues a GET request to the currency rate endpoint, passing the source and target currency codes as query parameters.
Response data path: $ — the entire JSON response is treated as a single record. Configure the From Currency and To Currency parameters.
Use this endpoint when you only need the exchange rate itself and not a converted amount. Currency codes follow the ISO 4217 standard.
Email Validation
Validates an email address and returns mailbox status, domain status, deliverability indicators, and standardization information. Use this endpoint to enrich contact records with email quality scores and validation results.
Issues a GET request to the email info endpoint, passing the email address as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the Email Address parameter.
Use a lookup-based macro to validate email addresses from an upstream Nexset in bulk. The response includes fields such as mailbox validity, domain MX record status, and disposable email detection.
Email Address Similarity Key
Generates a similarity key for an email address to support fuzzy email deduplication. Use this endpoint to identify duplicate email records with variant formatting (e.g., different capitalization or alias addresses).
Issues a GET request to the email match endpoint, passing the email address as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the Email Address parameter.
Email similarity keys normalize address formatting to identify records that represent the same mailbox despite superficial differences. Use with lookup-based macros for bulk processing.
First Name Similarity Key
Generates a similarity key specifically for first or given names. Use this endpoint to support fuzzy matching of person records across datasets where name formatting varies.
Issues a GET request to the first name match endpoint, passing the first name as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the First Name parameter.
First name similarity keys handle common name variations, nicknames, and alternate spellings. Combine with the Last Name Similarity Key endpoint for comprehensive person record deduplication.
Full Name Similarity Key
Generates an AI-powered similarity key for a full individual name to support fuzzy matching of person records across datasets. Use this endpoint for comprehensive person record deduplication when a full name string is available.
Issues a GET request to the full name match endpoint, passing the full name as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the Full Name parameter.
The full name endpoint uses AI to handle name variations including reversed name order, nicknames, and cultural naming conventions. Use a lookup-based macro to process names from an upstream Nexset in bulk.
Last Name Similarity Key
Generates a similarity key for surnames or last names. Use this endpoint to normalize surname variations for person record matching and deduplication across datasets.
Issues a GET request to the last name match endpoint, passing the last name as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the Last Name parameter.
Last name similarity keys handle hyphenated surnames, prefixes, and spelling variations. Combine with the First Name Similarity Key endpoint for comprehensive person matching workflows.
ZIP Code Information
Returns city, state, county, latitude/longitude, and timezone data for a US ZIP code. Use this endpoint to enrich address records with geographic metadata derived from ZIP codes.
Issues a GET request to the ZIP code info endpoint, passing the 5-digit ZIP code as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the ZIP Code parameter.
This endpoint covers US ZIP codes only. Use a lookup-based macro to process ZIP codes from an upstream Nexset in bulk for geographic enrichment of address datasets.
Stock Information
Returns real-time stock price, analyst recommendations, financial metrics, and company information for a given ticker symbol or company name. Use this endpoint to enrich financial datasets with current market data.
Issues a GET request to the stock info endpoint, passing the ticker symbol or company name as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the Stock Ticker or Company Name parameter.
Market data is provided in real time. Use this endpoint sparingly in high-frequency data flows, as each call consumes API credits. Consider scheduling this source at appropriate intervals to balance data freshness with credit consumption.
IP Address Profile
Retrieves IP address intelligence including ASN, organization, CIDR, hostname, geolocation, and reputation/abuse signals for a given IP address. Use this endpoint to enrich security or analytics data with IP-based context.
Issues a GET request to the IP profile endpoint, passing the IP address as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the IP Address parameter.
Use a lookup-based macro to process IP addresses from an upstream Nexset for bulk IP enrichment. The abuse signal data is useful for security threat detection and fraud prevention workflows.
Phone Number Information
Retrieves global telephone number information including formatting, validation data, geographic details, and carrier information. Use this endpoint to validate and enrich phone number data in contact records.
Issues a GET request to the phone info endpoint, passing the phone number as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the Phone Number parameter.
This endpoint accepts phone numbers in various formats. Use lookup-based macros to validate phone numbers from an upstream contact Nexset in bulk, then use the results to flag invalid or undeliverable numbers.
Weather by ZIP Code
Retrieves current weather conditions including temperature and conditions description for a US ZIP code. Use this endpoint to enrich operational or logistics data with location-based weather context.
Issues a GET request to the weather by ZIP endpoint, passing the 5-digit US ZIP code as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the US Zip Code parameter.
Weather data reflects current conditions at the time of the API call. Schedule this source to run at appropriate intervals to capture condition changes. This endpoint covers US ZIP codes only.
Web Page Performance
Measures web page load performance from various geographic locations for a given URL. Use this endpoint to ingest page performance data for web monitoring, competitive analysis, or SLA tracking.
Issues a GET request to the page info endpoint, passing the URL to test as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the URL parameter with the web page URL to test.
Each call measures performance from Interzoid's monitoring locations. Use lookup-based macros to test a list of URLs from an upstream Nexset for bulk performance benchmarking.
Remaining API Credits
Returns the number of remaining API credits on the account's license key. Use this endpoint to monitor API credit consumption and trigger alerts when credit levels fall below a threshold.
Issues a GET request to the remaining credits endpoint. No query parameters are required beyond the API key included automatically by Nexla.
Response data path: $ — the entire JSON response is treated as a single record containing the remaining credit count.
This endpoint also serves as the authentication test URL for the Interzoid connector. Use it in a scheduled Nexla data flow to track credit consumption over time and alert when credits need to be renewed.
Get Global Phone Number Information
Retrieves geographic information, primary languages spoken, and mobile device identification for a global telephone number. Use this endpoint to enrich international phone number data with country and regional context.
Issues a GET request to the global number info endpoint, passing the international phone number as a query parameter.
Response data path: $ — the entire JSON response is treated as a single record. Configure the International Phone Number parameter (include country code, e.g., +1 for US numbers).
Use a lookup-based macro to process international phone numbers from an upstream Nexset. This endpoint complements the Phone Number Information endpoint by providing additional global geographic and language context.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Interzoid data sources can also be manually configured to ingest data from any valid Interzoid API endpoint not covered by the pre-built templates, using the GET or POST method as required by the target endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Interzoid maintains a directory of all available API endpoints at https://www.interzoid.com/cloud-api-directory. Every endpoint requires the API license key as the apikey query parameter—automatically included by Nexla from your saved credential—for example, https://api.interzoid.com/getfullnamematch?apikey=YOUR_KEY&fullname=John+Smith. Most Interzoid endpoints return a flat JSON object, so use $ as the path to data to treat the entire response as a single record, or a field-specific path such as $.MatchKey to extract only that attribute. The Code (status) and Credits (remaining balance) fields returned alongside the primary result can be captured as metadata using the same path syntax.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Interzoid data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
