# ParseAPI > Parse messy input into structured JSON. Read the selected endpoint's parameters, response fields, and coverage before integrating. - Base: https://api.parseapi.com - Auth: `X-API-Key` header (or `Authorization: Bearer`) - OpenAPI: https://parseapi.com/openapi.json - Try it: `curl "https://api.parseapi.com/ip/8.8.8.8" -H "X-API-Version: 2.2.0" -H "X-API-Key: YOUR_API_KEY"` - Start with one lookup, inspect the returned JSON, then connect the fields the application needs. Prefer an official SDK for the project's language and runtime. Read its current installation instructions. ## Integration rules - Most lookup requests use GET at https://api.parseapi.com. Send X-API-Key, or Authorization: Bearer. Bare /ip and /useragent self-lookups also work without a key. - Free-plan users must include a link to ParseAPI on their website, app, or project documentation. A footer, about page, credits page, or another reasonable location is fine. Paid plans do not require ParseAPI attribution. Example HTML: Data provided by ParseAPI. Details: https://parseapi.com/legal/attribution#crediting-parseapi. - Pin application lookups with an exact X-API-Version request header, such as 2.2.0. Legacy Parse-Version pins are also accepted; both headers must match if sent together. With neither header, keyed requests use the saved team default and keyless self-lookups use 1.0.0. Keep the pin with the code through staging, deployment and rollback. Version-pinned SDKs send their supported contract automatically. Earlier published packages keep their original behavior. Check the X-API-Version response header for the exact version that answered. Invalid or unsupported headers return invalid_request (400), and retired selections return api_version_retired (410). - Keep secret keys on the server and out of source control, logs, URLs, browser bundles, and mobile apps. Use a parse_public_ key for browsers and list the allowed domains, including localhost for local development. Use a parse_app_ key with the Swift or Kotlin SDK for native apps. List the exact bundle ID or package name and send X-App-Id. - App keys support routine lookups and eligible plan detail. Metered endpoints, including GET /email/verify, return 403 for App keys. Run metered checks from a server with a secret key. - Read the selected endpoint's parameters and coverage before coding. Country is optional for State and Postal. Add a country code, such as ?country=US, when the input needs disambiguation. Encode values and query parameters instead of concatenating raw user input. - Check HTTP status and response fields. false is a negative answer. null means no answer is available. An omitted field is absent from this response. Do not turn unknown values into false or reject a valid response because a new field appears. - API 2.1 returns the complete ordinary answer on Free and automatically includes existing profile detail on paid plans. Available fields appear at their natural homes beside the routine answer, including each collection item. There is no response deep object. Inaccessible optional fields are absent; returned unknown values are null. Test the field you need. Carrier and HLR return their complete selected result without a deep switch. - Email mailbox verification is explicit GET /email/verify?email=address%40example.com; it uses your account's verification allowance or enabled on-demand billing. Use GET /email/{email} for ordinary validation; deep=true is rejected on that route in 2.1. /carrier/{number} (carrier + line type), /caller/{number} (caller ID, NANP), /hlr/{number} (live phone status, worldwide) are separate metered lookups. Check https://parseapi.com/docs/usage and https://parseapi.com/pricing for allowances and rates. - Errors contain code, message, docs, and request_id. A failed DNS lookup returns HTTP 503 with code dns_resolution_failed. Handle the code, not message text; this is not an invalid-mailbox verdict. Honor Retry-After on DNS failures, use at most two retries with jitter, and keep a total deadline. Set a timeout. Honor Retry-After for rate_limited, and use bounded backoff for temporary connection failures, server_error, or service_unavailable. quota_exceeded needs allowance or billing action, not a retry loop. A timeout may follow a processed request. Repeating a metered check can consume another unit. Official SDKs default to no automatic retries for metered checks. - Before running live metered checks or starting paid Bulk processing, explain the intended checks and usage, and get the user's approval unless that scope is already authorized. Do not enable paid checks, on-demand usage, or automatic metered retries as an incidental part of setup. - Use POST /preflight with operation counts to estimate permissions, advisory capacity and additional charges. Its budget_usd is advisory. For an authorized task with an enforced additional-charge limit, POST /task with operations and budget_usd, then POST /task/{id}/lookup with operation, value, optional country and optional deep. Send a unique Idempotency-Key for creation and each intended lookup, and reuse it with identical inputs on retries. Tasks allow up to 1000 lookups, expire after 24 hours, and retain accessible results for 48 hours from creation. Inspect status_code and result in each saved execution. task_in_progress and task_outcome_unknown retain the reservation; never use a new ID to repeat uncertain work. GET /task/{id} reports budget and progress. POST /task/{id}/cancel prevents new work while started lookups can finish. A new request still needs room for its conservative maximum charge, even when included quota appears available. These task limits apply only through the task endpoint. Existing account limits still apply. ## Docs - [Agent integration guide](https://parseapi.com/agents): instructions for discovering endpoints, making requests, and handling responses, errors, and usage - [MCP](https://parseapi.com/mcp): connect to the hosted server at https://mcp.parseapi.com through browser sign-in, or use X-API-Key for headless access - [OpenAPI](https://parseapi.com/openapi.json): machine-readable paths + auth (OpenAPI 3.1) - [Docs](https://parseapi.com/docs): welcome and getting started - [Quickstart](https://parseapi.com/docs/quickstart): Identify your browser, operating system and device in your first lookup. - [API reference](https://parseapi.com/docs/apis): Find an API by the value you already have, then read its inputs and response fields. - [API keys](https://parseapi.com/docs/keys): Choose a key, send it with your request, and configure server, browser or app access. - [Request](https://parseapi.com/docs/request): Build a request using the documented method, path, query, headers, and JSON body. - [Response](https://parseapi.com/docs/response): Understand successful lookups, included profile data, null values and omitted fields. - [Errors](https://parseapi.com/docs/errors): Look up an error code, understand its cause, and find the next step. - [Usage and metered lookups](https://parseapi.com/docs/usage): Understand monthly request allowances, metered checks, and on-demand spending limits. - [Explore](https://parseapi.com/docs/explore): browse APIs, follow references, and inspect JSON responses - [Account](https://parseapi.com/docs/account): GET /account with a secret key for remaining allowances, request limits, additional-unit prices and monthly spending room. Inspection is free and has a separate rate limit. Use HTTP for Account inspection - [Preflight](https://parseapi.com/docs/preflight): estimate access, additional cost and allowance for operation counts before running requests. Requires a secret key. Reserves no units or money and does not enforce a budget - [Integrate](https://parseapi.com/integrate): API clients, AI tools, automation workflows, form.js and official SDKs - [n8n](https://parseapi.com/integrate/n8n): import a manual starter workflow and configure a Header Auth credential - [n8n starter workflow](https://parseapi.com/integrations/n8n/parseapi-starter.json): example email and core lookup, inactive with no saved credentials - [Make](https://parseapi.com/integrate/make): connect through the HTTP app using a stored API key - [Zapier](https://parseapi.com/integrate/zapier): connect through API by Zapier using a Static Headers connection - [Bruno](https://parseapi.com/integrate/bruno): import the starter collection and configure a secret environment variable - [Insomnia](https://parseapi.com/integrate/insomnia): import the starter collection and configure a private environment - [Postman](https://parseapi.com/integrate/postman): download the starter collection and empty-key environment, then send five example requests - [API versions](https://parseapi.com/docs/versioning): send an exact X-API-Version request header to pin the contract in application code. When neither version header is sent, requests use the saved team default. Review that fallback in Settings → API version - [Release history](https://parseapi.com/docs/releases): API response changes and migration notes - [API 2.3.0 release notes](https://parseapi.com/docs/releases/2.3.0): released; Choose independent email delivery and catchall facts, explicit verification assessments, and successful negative checks for supplied invalid values. - [API 2.2.0 release notes](https://parseapi.com/docs/releases/2.2.0): released; Use County consistently for counties and comparable administrative areas. Earlier contracts retain their existing District routes and fields. - [API 2.1.0 release notes](https://parseapi.com/docs/releases/2.1.0): upcoming, not released; Read profile fields directly from the response and use a separate request to verify email delivery. - [API 2.0.0 release notes](https://parseapi.com/docs/releases/2.0.0): released; Core responses focus on the common task, with optional detail in deep. Review field moves, renamed fields, removals and plan requirements before changing your team’s version. - [API 1.0.0 release notes](https://parseapi.com/docs/releases/1.0.0): original contract; The name for the API contract that existed before explicit version selection. Existing teams keep its response fields and access rules while they prepare an upgrade. - [Company API](https://parseapi.com/docs/company): Find a company by name, website, ticker or registration identifier. - [Stack API](https://parseapi.com/docs/stack): Identify the technologies observed on a website. - [Card API](https://parseapi.com/docs/card): Card brand and CDN logo from 2–11 leading digits. Optional issuer details in Deep. - [Industry API](https://parseapi.com/docs/industry): Find an industry by code or business activity. - [ASN Lookup API](https://parseapi.com/docs/asn): A network organization and recorded country from its ASN. - [IP Address API](https://parseapi.com/docs/ip): Where an IP is from, country, ASN, network. - [Continent API](https://parseapi.com/docs/continent): A continent by code, or every country in it. - [Country API](https://parseapi.com/docs/country): Country names, currency, languages, and timezones. - [State API](https://parseapi.com/docs/state): A state or province by code or name, with timezones. - [County API](https://parseapi.com/docs/county): A county by code or name, with its state and timezones. - [City API](https://parseapi.com/docs/city): Exact name, typeahead, nearest, or nearby cities. - [Postal API](https://parseapi.com/docs/postal): A ZIP or postal code to its city, state, coordinates, and timezone. - [Address API](https://parseapi.com/docs/address): A US address, checked against official records. - [Population](https://parseapi.com/docs/population): Population by place. - [Tax](https://parseapi.com/docs/tax): Sales tax rates and US property-tax medians in paid place detail. - [Point API](https://parseapi.com/docs/point): Country, state, county, and timezone at a coordinate. - [Name API](https://parseapi.com/docs/name): A person's name, split, cased, and checked. - [Email API](https://parseapi.com/docs/email): Format, domain, role, and a typo suggestion, on every call. - [Phone Number API](https://parseapi.com/docs/phone): Validate and format a number. 246 countries and regions. - [Carrier Lookup API](https://parseapi.com/docs/carrier): Who serves a number: carrier, line type, and burner. - [Caller ID API](https://parseapi.com/docs/caller): The registered caller ID (CNAM) for a number. - [HLR Lookup API](https://parseapi.com/docs/hlr): Assignment and reachability at the last network check. - [Domain API](https://parseapi.com/docs/domain): Whether a domain is available to register. - [DNS Lookup API](https://parseapi.com/docs/dns): DNS record names, types, values, and remaining TTLs. - [MX API](https://parseapi.com/docs/mx): Mail exchange records for a domain. - [Useragent API](https://parseapi.com/docs/useragent): Device, OS, browser, and bot, from one header. - [Language API](https://parseapi.com/docs/language): Detect text in 32 languages, or look up an ISO language code. - [Time API](https://parseapi.com/docs/time): Local time, timezone lookup, and conversion. - [Date API](https://parseapi.com/docs/date): An ISO date, validity, and Unix timestamp. - [Elevation API](https://parseapi.com/docs/elevation): Elevation at a point, a list of coordinates, or evenly along a path, in feet and meters. - [Weather API](https://parseapi.com/docs/weather): Current conditions at a latitude and longitude. - [Emoji API](https://parseapi.com/docs/emoji): Resolve, browse, and find emoji in text. - [Holiday API](https://parseapi.com/docs/holiday): Public holidays by country, year, month, or day. - [Currency API](https://parseapi.com/docs/currency): Currency names and symbols, plus daily exchange rates. ## Integration pages - [Postman](https://parseapi.com/integrate/postman): Your first request, ready to send. - [Bruno](https://parseapi.com/integrate/bruno): Keep your requests close to your code. - [Insomnia](https://parseapi.com/integrate/insomnia): Import. Send. Explore the response. - [Cursor](https://parseapi.com/integrate/cursor): Let your agent build with actual lookup results. - [VS Code](https://parseapi.com/integrate/vscode): Give Copilot the data behind the feature. - [Claude](https://parseapi.com/integrate/claude): Check the details behind your next decision. - [Claude Code](https://parseapi.com/integrate/claude-code): Build and debug against actual API responses. - [ChatGPT](https://parseapi.com/integrate/chatgpt): Check the details behind your next decision. - [n8n](https://parseapi.com/integrate/n8n): Drop a lookup into your workflow. - [Make](https://parseapi.com/integrate/make): Add useful data to your scenario. - [Zapier](https://parseapi.com/integrate/zapier): Connect a lookup to your next step. - [form.js](https://parseapi.com/integrate/form): Validation and autofill for your own form. - [Node](https://parseapi.com/integrate/node): The official Node SDK. - [Python](https://parseapi.com/integrate/python): The official Python SDK. - [Go](https://parseapi.com/integrate/go): The official Go SDK. - [Ruby](https://parseapi.com/integrate/ruby): The official Ruby SDK. - [PHP](https://parseapi.com/integrate/php): The official PHP SDK. - [Rust](https://parseapi.com/integrate/rust): The official Rust SDK. - [Swift](https://parseapi.com/integrate/swift): The official Swift SDK. - [Kotlin](https://parseapi.com/integrate/kotlin): The official Kotlin SDK. ## Tutorials - [Tutorials](https://parseapi.com/tutorials): build complete features with working demos and downloadable examples - [Autofill city and state from a ZIP code](https://parseapi.com/tutorials/zip-code-autofill): Autofill editable city and state fields from a US ZIP code in your existing HTML form. - [Choose an Australian suburb from a postcode](https://parseapi.com/tutorials/australian-postcode-suburbs): Add Australian postcode autofill with editable suburb suggestions and state fields. - [Find nearby ZIP codes](https://parseapi.com/tutorials/zip-code-radius): Build a browser search that lists nearby US ZIP codes with distances in miles and kilometers, using an adjustable radius. - [Calculate distance between ZIP codes](https://parseapi.com/tutorials/zip-code-distance): Calculate straight-line distance between two US ZIP codes in a browser or Python, with results in miles and kilometers. - [Check an email as someone types](https://parseapi.com/tutorials/check-email-before-submit): Add email validation and optional typo corrections to an existing HTML input with form.js. - [Suggest a country from a visitor's IP address](https://parseapi.com/tutorials/suggest-country-from-ip): Suggest a visitor's country with IP geolocation and keep their own regional preference in control. - [Connect country, state and county choices](https://parseapi.com/tutorials/country-state-dropdown): Load state suggestions from a country, then county suggestions from the selected state in your own form. - [Estimate a date in business days](https://parseapi.com/tutorials/add-business-days): Add business days to a date in JavaScript, skipping weekends, public holidays, and your own closed dates. - [Find an open store nearby](https://parseapi.com/tutorials/store-locator): Build a JavaScript store locator with nearby branches, approximate distances, and opening status from your schedules. - [Show an event in the visitor's time zone](https://parseapi.com/tutorials/event-local-time): Convert an event's UTC start time to each visitor's time zone, including the local date and daylight-saving offset. - [Add city autocomplete to an existing field](https://parseapi.com/tutorials/city-autocomplete): Use form.js to suggest cities and keep the selected city ID with your form. - [Add address autocomplete to an existing field](https://parseapi.com/tutorials/address-autocomplete): Add US address autocomplete to an existing HTML input, with keyboard navigation and editable suggestions. - [Add an email delivery check to your app](https://parseapi.com/tutorials/verify-email-server): Check a submitted email on your Node server and use format, domain and delivery results to give useful feedback. - [Label a location from a map click](https://parseapi.com/tutorials/map-click-place): Build a map location picker that reverse geocodes selected coordinates into a region and country label. - [Find shared working hours](https://parseapi.com/tutorials/meeting-time-overlap): Find overlapping working hours across two time zones for a chosen date, with daylight-saving transitions handled. - [Build a local weather card](https://parseapi.com/tutorials/weather-card): Build a weather card from a postal code using JavaScript, Node, or Python, with current conditions and observation time. - [Show opening hours on a business page](https://parseapi.com/tutorials/business-open-now): Show whether a business is open now from its maintained opening hours, local time zone, and holiday policy. - [Build a currency picker](https://parseapi.com/tutorials/currency-picker): Build a currency selector that suggests a currency from a country and applies only the choice the person accepts. - [Build a contact review step for inbound emails](https://parseapi.com/tutorials/email-to-crm): Use ParseAPI in Node to turn copied contact fields into a review form before your application saves them to a CRM. - [Validate a phone number in your form](https://parseapi.com/tutorials/validate-phone-field): Add phone-number feedback to an existing HTML field with form.js, keeping the input editable and country context explicit. - [Build a PHP contact form](https://parseapi.com/tutorials/php-contact-form): Check submitted email and phone values, keep valid entries after errors, and hand the message to your existing PHP mail transport. - [Build a currency converter with Python](https://parseapi.com/tutorials/python-currency-converter): Build a Flask form that converts an amount with a dated reference rate and displays the published date beside the result. - [Build an emoji picker with React](https://parseapi.com/tutorials/react-emoji-picker): Add an emoji picker to a React message composer, with instant choices and search powered by ParseAPI. - [Build a route elevation profile with Node](https://parseapi.com/tutorials/route-elevation-profile): Sample your route's waypoints with the Elevation API and draw a distance-based SVG profile that preserves unknown heights. - [Route support requests by language](https://parseapi.com/tutorials/support-language-routing): Build a Python support form that detects a message's language and assigns an application-owned queue, with a review path for uncertain results. - [Recheck a booking date before accepting it](https://parseapi.com/tutorials/holiday-booking-form): Build a date form that checks your business weekday, holiday, and closure policy again on the server. - [Show a dispatch estimate at checkout](https://parseapi.com/tutorials/checkout-dispatch-date): Use your order cutoff, business time zone, and public holiday calendar to show when preparation should finish. - [Build a domain availability form](https://parseapi.com/tutorials/domain-search-form): Check an exact domain name and show available, taken, or unknown without treating a failed lookup as availability. - [Build an industry selector for business onboarding](https://parseapi.com/tutorials/industry-selector): Search US NAICS 2022 titles with the Node SDK and keep the code and title a person selects in your onboarding form. - [Add website technologies to a CRM account](https://parseapi.com/tutorials/crm-website-technologies): Use a company website to show detected technologies, versions, and their recorded check time on an account card. ## SDKs Official clients (https://parseapi.com/integrate#sdks). One method per endpoint, named after the route. MIT licensed. Swift and Kotlin take an app key and send the bundle ID. - Node: `npm install @parseapi/sdk@1.15.1` (https://github.com/parseapi/node) - Python: `pip install parseapi==1.13.1` (https://github.com/parseapi/python) - Go: `go get github.com/parseapi/go@v1.13.1` (https://github.com/parseapi/go) - Ruby: `gem install parseapi --version 1.13.1` (https://github.com/parseapi/ruby) - PHP: `composer require parseapi/sdk:1.13.1` (https://github.com/parseapi/php) - Rust: `cargo add parseapi@2.6.1 cargo add tokio --features macros,rt-multi-thread` (https://github.com/parseapi/rust) - Swift: `.package(url: "https://github.com/parseapi/swift", from: "1.13.1")` (https://github.com/parseapi/swift) - Kotlin: `git clone --branch 1.13.2 --depth 1 https://github.com/parseapi/kotlin.git ../parseapi-kotlin` (https://github.com/parseapi/kotlin) ## Bulk The same lookups over whole files, no code. Upload a CSV, Excel, or Numbers file and download a copy with parse_ columns added. Preview the results, choose columns, and approve the exact quote before paid processing. Pricing follows the selected checks, unique values, and the account's plan. Use the quote and current product pages for pricing, refund rules, and download availability. - [Bulk CSV cleaning](https://parseapi.com/bulk): one drop, every column we can parse (emails, phones, IPs, domains, user agents, countries, street addresses, postal codes, names, dates) - [Bulk email verification](https://parseapi.com/bulk/email): deliverability, disposable, and role flags on every row - [Bulk phone validation](https://parseapi.com/bulk/phone): validity and formats on every row, carrier and live status as toggles - [Bulk IP](https://parseapi.com/bulk/ip): country, city, network operator, datacenter and VPN flags on every row - [Bulk domain](https://parseapi.com/bulk/domain): registration status and the registrar for every domain - [Bulk address validation](https://parseapi.com/bulk/address): US street-address checks and standardized parts, plus ZIP and postal-code lookups ## Free tools Interactive, no signup to use. API lookups use our public APIs. Date calculations, service ZIP matching, and the bundled planting-zone reference run in the browser. - [Planting zone by ZIP code](https://parseapi.com/tool/planting-zone-by-zip-code): planting zone and winter temperature range by ZIP - [ZIP code service area checker](https://parseapi.com/tool/zip-code-service-area-checker): match a ZIP against your list of up to 200 US ZIP codes, browser-only - [Split first and last names](https://parseapi.com/tool/split-names): paste full names, get clean first, middle, and last columns back - [ZIP code radius finder](https://parseapi.com/tool/zip-code-radius-finder): up to 100 nearby ZIPs with city, state, and straight-line distance, CSV export - [Distance between ZIP codes](https://parseapi.com/tool/zip-code-distance): straight-line miles and kilometers between two ZIPs - [Area code lookup](https://parseapi.com/tool/area-code-lookup): the state or province behind any North American area code - [What is my elevation](https://parseapi.com/tool/what-is-my-elevation): height above sea level in feet and meters, from your location or any coordinates - [Time zone by ZIP code](https://parseapi.com/tool/timezone-by-zip): the time zone and current local time for any US ZIP - [County lookup by ZIP code](https://parseapi.com/tool/county-by-zip): the county and FIPS code behind any US ZIP - [What is my user agent](https://parseapi.com/tool/what-is-my-user-agent): your User-Agent string parsed on load, or paste any string - [What is my IP](https://parseapi.com/tool/what-is-my-ip): your public IP, country, and network on load, or look up any address - [Email checker](https://parseapi.com/tool/email-checker): shape, domain, disposable, and role checks for any email address - [Business days calculator](https://parseapi.com/tool/business-days-calculator): count weekdays between dates, with optional UK regional bank-holiday exclusion - [Phone validator](https://parseapi.com/tool/phone-validator): check numbering-plan validity and get E.164, national, and international formats, no live-status check - [Public holidays](https://parseapi.com/tool/public-holidays): official holiday calendars by country with the next one counted down - [MX lookup](https://parseapi.com/tool/mx-lookup): the mail servers behind any domain, live from DNS - [Distance between cities](https://parseapi.com/tool/distance-between-cities): straight-line miles and kilometers between any two cities - [Domain availability checker](https://parseapi.com/tool/domain-availability-checker): check whether a domain is available or taken - [State abbreviations list](https://parseapi.com/tool/state-abbreviations): all 50 two-letter codes plus DC, territories, and military regions - [What time zone am I in](https://parseapi.com/tool/what-time-zone-am-i-in): your zone from your location, with the next daylight change - [Emoji copy and paste](https://parseapi.com/tool/emoji-copy-paste): search every emoji by keyword, click to copy - [Weather at my location](https://parseapi.com/tool/weather-at-my-location): current conditions from the nearest official station - [ZIP code lookup](https://parseapi.com/tool/zip-code-lookup): city, county, timezone, and coordinates for a US ZIP - [Country codes list](https://parseapi.com/tool/country-codes): ISO alpha-2, alpha-3, numeric, and calling codes in one table - [What county am I in](https://parseapi.com/tool/what-county-am-i-in): the county at your exact coordinates from real boundaries - [Time zone converter](https://parseapi.com/tool/time-zone-converter): a time and two zones in, the local time out ## Product - [WHOIS lookup](https://parseapi.com/whois): domain registration dates, registrar, and status on paid plans. Uses `GET /domain/{domain}?deep=true`; read the [Domain API reference](https://parseapi.com/docs/domain) for the response and coverage. Results are cached. - [Pricing](https://parseapi.com/pricing): plans, included allowances and rates - [FAQ](https://parseapi.com/faq): limits, billing, and how quotas work ## Optional - [Useragent directory](https://parseapi.com/useragent): browsers, bots, operating systems, engines, and devices - [Area codes](https://parseapi.com/phone/area-code): every North American area code with the state it serves, time zone, and in-service date - [About](https://parseapi.com/about): the ParseAPI story - [Brand](https://parseapi.com/brand): wordmark, icon, colors, and downloadable assets - [Status](https://parseapi.com/status): live status and latency