How do I connect Postal Data API?

Sign up for Conductor Deck, then add a Postal Data API step to a workflow on the visual canvas. The builder walks you through the connection it needs — an account authorization or the required keys — right inside the step. No separate setup or code.

Yes — Conductor Deck has a free tier you can build and run workflows on, with no credit card required. Paid plans raise the monthly run limits and add advanced features when you need them.

What's the difference between a trigger and an action?

A trigger is the event that starts a workflow — for example, a Stream Deck button press or an incoming event from a connected app. An action is a step the workflow performs once it runs. A workflow is one trigger followed by one or more actions.

Postal Data API + Stream Deck

developer-tools · 0 triggers · 6 actions

Postal Data API validates and looks up postal codes, locations, coordinates, and regional metadata across more than 240 countries and territories. Add Postal Data API to your Stream Deck workflows with guided setup for the connection details it needs.

Build a Postal Data API workflow — free See how it works

No code
Free tier
One Stream Deck press
Pairs with OBS & Elgato tools
OAuth & keys handled in-builder

Triggers & actions

Steps your workflow can perform in Postal Data API.

Get API Information

Return Postal Data API version, coverage, usage guidance, current balance, and configured rate-limit status when returned, for connectivity or service discovery. The provider does not document this endpoint as unbilled, so assume it may consume one query.

Get Postal Code Metadata

Return all available country-specific metadata for a postal code, such as coordinates, timezone, county, elevation, and administrative levels. The metadata fields vary by country and availability. Each successful call consumes one Postal Data API query.

Look Up Postal Code

Look up the city, region, and coordinates for a postal code. Use this for a concise location result; use Get Postal Code Metadata for country-specific administrative details. Each successful call consumes one query.

Search Postal Codes by City

Return all postal codes matching a city and optional region, including fuzzy-match details. For US searches, provide a state name or state code. Each successful call consumes one Postal Data API query.

Validate Postal Code

Check whether one postal code exists without treating a nonexistent code as an execution error. Inspect valid in the response. Each successful call consumes one Postal Data API query.

Validate Postal Codes in Bulk

Validate 1 to 1,000 postal codes synchronously, including mixed-country batches. Results preserve input order and report per-record failures. A batch of N records consumes N queries and is rejected atomically if balance or rate-limit budget is insufficient.

About Postal Data API

Postal Data API validates and looks up postal codes, locations, coordinates, and regional metadata across more than 240 countries and territories.

developer-tools

How to connect

Sign up for free

Create your Conductor Deck account: no credit card required.

Connect Postal Data API

Follow the setup prompts for Postal Data API. Conductor Deck handles the app authorization or required connection details inside the workflow builder.

Build a workflow

Add a Postal Data API action to your visual workflow canvas. Configure the options you need, then connect it to other steps.

Assign to Stream Deck

Sync your workflow to any Stream Deck button. Press once to trigger the entire sequence.

Frequently asked questions

How do I connect Postal Data API?: Sign up for Conductor Deck, then add a Postal Data API step to a workflow on the visual canvas. The builder walks you through the connection it needs — an account authorization or the required keys — right inside the step. No separate setup or code.
Is it free?: Yes — Conductor Deck has a free tier you can build and run workflows on, with no credit card required. Paid plans raise the monthly run limits and add advanced features when you need them.
What's the difference between a trigger and an action?: A trigger is the event that starts a workflow — for example, a Stream Deck button press or an incoming event from a connected app. An action is a step the workflow performs once it runs. A workflow is one trigger followed by one or more actions.