The API returns information about each zip code, including zip code, province, city, type, geographic coordinates (latitude and longitude), and more. This data can be used for a wide range of applications, such as address validation, geolocation, data analysis, and mapping.
The API allows developers to integrate zip code data into their own systems and applications, streamlining processes and improving data quality. For example, businesses and organizations can use the API to validate and normalize addresses, calculate shipping rates, or determine customer locations for targeted marketing campaigns.
In addition to zip code data, the API can also provide additional information, such as street name, and confidence ratings. This can help companies and organizations better understand the areas they serve and make data-driven decisions.
Overall, The All postal codes Canada API is a valuable resource for businesses, organizations, and developers looking to improve the quality of their data, enhance their location-based services or gain a deeper understanding of Canada's postal codes.
It will receive parameters and provide you with a JSON.
Address Validation: The API can be used to validate and standardize postal codes, improving the accuracy of address data and reducing the number of undeliverable packages.
Mapping and Geolocation: The API can be used to map postal codes and determine the location of addresses, enabling the creation of location-based services and applications.
E-commerce: Online retailers can use the API to calculate shipping rates, tax rates, and delivery times based on the postal code of the customer.
Data Analysis: The API can be used to analyze and visualize postal code data, helping businesses and organizations to better understand their customers and make data-driven decisions.
Marketing: The API can be used to segment customers and target marketing campaigns based on their postal code, improving the effectiveness of marketing efforts.
Besides API call limitations per month, there are no other limitations.
To use this endpoint all you have to do is run it, it will return information such as street name, city, province, latitude, longitude, type, postcode, and confidentiality number.
[
{
"id": 1,
"City": "EDMONTON",
"Type": "HWY",
"Unit": "",
"Count": "1",
"aType": "NonRES",
"Number": "408",
"Street": "28a HWY",
"Latitude": "53.840313",
"PostCode": "T0A0H0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.321822",
"Confidence": "0.7",
"Street Name": "28A"
},
{
"id": 2,
"City": "BON ACCORD",
"Type": "",
"Unit": "",
"Count": "1",
"aType": "NonRES",
"Number": "49",
"Street": "38",
"Latitude": "53.813742",
"PostCode": "T0A0K0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.332283",
"Confidence": "",
"Street Name": "38"
},
{
"id": 3,
"City": "Bon Accord",
"Type": "AVE",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "4920",
"Street": "40 ave",
"Latitude": "53.816741",
"PostCode": "T0A0K0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.332361",
"Confidence": "0.7",
"Street Name": "40"
},
{
"id": 4,
"City": "Bon Accord",
"Type": "AVE",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "7",
"Street": "Honeybear Av",
"Latitude": "53.900320",
"PostCode": "T0A0K0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.351484",
"Confidence": "0.8",
"Street Name": "Honeybear"
},
{
"id": 5,
"City": "BON ACCORD",
"Type": "TRAIL",
"Unit": "",
"Count": "2",
"aType": "RES",
"Number": "33",
"Street": "Landing TRAIL",
"Latitude": "53.825546",
"PostCode": "T0A0K0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.334654",
"Confidence": "0.7",
"Street Name": "LANDING"
},
{
"id": 6,
"City": "Gibbons",
"Type": "ST",
"Unit": "2",
"Count": "2",
"aType": "RES",
"Number": "4905",
"Street": "47 ST",
"Latitude": "53.826300",
"PostCode": "T0A0K0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.325521",
"Confidence": "0.9",
"Street Name": "47"
},
{
"id": 7,
"City": "Rural Sturgeon County",
"Type": "HWY",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "23507",
"Street": "28 Highway",
"Latitude": "53.832757",
"PostCode": "T0A0K0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.347598",
"Confidence": "0.7",
"Street Name": "28"
},
{
"id": 8,
"City": "Rural Sturgeon County",
"Type": "HWY",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "23507",
"Street": "28 HWY",
"Latitude": "53.832757",
"PostCode": "T0A0K0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.347598",
"Confidence": "0.7",
"Street Name": "28"
},
{
"id": 9,
"City": "Rural Sturgeon County",
"Type": "AVE",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "14",
"Street": "Honeybear Avenue",
"Latitude": "53.716091",
"PostCode": "T0A0K0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.321292",
"Confidence": "0.8",
"Street Name": "HONEYBEAR"
},
{
"id": 10,
"City": "Sturgeon County",
"Type": "",
"Unit": "45",
"Count": "5",
"aType": "RES",
"Number": "56220",
"Street": "Range Road 230",
"Latitude": "53.841724",
"PostCode": "T0A0K0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.273216",
"Confidence": "0.9",
"Street Name": "RANGE ROAD 230"
},
{
"id": 11,
"City": "Sturgeon County",
"Type": "",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "23250",
"Street": "Township Road 570",
"Latitude": "53.890952",
"PostCode": "T0A0K0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.347587",
"Confidence": "0.8",
"Street Name": "TOWNSHIP ROAD 570"
},
{
"id": 12,
"City": "Edmonton",
"Type": "",
"Unit": "",
"Count": "2",
"aType": "RES",
"Number": "42",
"Street": "Rex",
"Latitude": "53.522827",
"PostCode": "T0A0K4",
"Province": "AB",
"Direction": "",
"Longitude": "-113.289338",
"Confidence": "0.4",
"Street Name": "REX"
},
{
"id": 13,
"City": "CORONADO",
"Type": "",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "1",
"Street": "Coronado",
"Latitude": "53.885404",
"PostCode": "T0A0X0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.297941",
"Confidence": "0.35",
"Street Name": "CORONADO"
},
{
"id": 14,
"City": "CORONADO",
"Type": "",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "1",
"Street": "Coronado CA",
"Latitude": "53.885404",
"PostCode": "T0A0X0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.297941",
"Confidence": "0.3",
"Street Name": "CORONADO CA"
},
{
"id": 15,
"City": "CORONADO",
"Type": "DR",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "1",
"Street": "Coronado DR",
"Latitude": "53.885404",
"PostCode": "T0A0X0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.297941",
"Confidence": "0.35",
"Street Name": "Coronado"
},
{
"id": 16,
"City": "Sturgeon County",
"Type": "DR",
"Unit": "",
"Count": "2",
"aType": "RES",
"Number": "50",
"Street": "Coronado DR",
"Latitude": "53.887356",
"PostCode": "T0A0X0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.289876",
"Confidence": "0.8",
"Street Name": "Coronado"
},
{
"id": 17,
"City": "Sturgeon County",
"Type": "DR",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "231",
"Street": "Lostpoint Lake DR",
"Latitude": "53.881846",
"PostCode": "T0A0X0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.291263",
"Confidence": "0.8",
"Street Name": "Lostpoint Lake"
},
{
"id": 18,
"City": "Sturgeon County",
"Type": "AVE",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "231",
"Street": "Range Road N A and Willow AVE",
"Latitude": "53.881846",
"PostCode": "T0A0X0",
"Province": "AB",
"Direction": "N",
"Longitude": "-113.291263",
"Confidence": "0.7",
"Street Name": "Range RoadA and Willow"
},
{
"id": 19,
"City": "Sturgeon County",
"Type": "",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "20",
"Street": "Willow",
"Latitude": "53.881846",
"PostCode": "T0A0X0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.291263",
"Confidence": "0.8",
"Street Name": "WILLOW"
},
{
"id": 20,
"City": "Sturgeon County",
"Type": "AVE",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "20",
"Street": "Willow AVE",
"Latitude": "53.881846",
"PostCode": "T0A0X0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.291263",
"Confidence": "0.8",
"Street Name": "Willow"
},
{
"id": 21,
"City": "Sturgeon County",
"Type": "AVE",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "231",
"Street": "Willow AVE",
"Latitude": "53.881846",
"PostCode": "T0A0X0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.291263",
"Confidence": "0.8",
"Street Name": "Willow"
},
{
"id": 22,
"City": "Fort",
"Type": "LANE",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "8",
"Street": "Connor LANE",
"Latitude": "53.550565",
"PostCode": "T0A1H0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.272949",
"Confidence": "0.8",
"Street Name": "CONNOR"
},
{
"id": 23,
"City": "BON ACCORD",
"Type": "ST",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "51",
"Street": "47 ST",
"Latitude": "53.814995",
"PostCode": "T0A1N0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.326273",
"Confidence": "0.7",
"Street Name": "47"
},
{
"id": 24,
"City": "BON ACCORD",
"Type": "ST",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "53",
"Street": "47 ST",
"Latitude": "53.814995",
"PostCode": "T0A1N0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.326273",
"Confidence": "0.7",
"Street Name": "47"
},
{
"id": 25,
"City": "BON ACCORD",
"Type": "ST",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "53",
"Street": "47 ST NW",
"Latitude": "53.828714",
"PostCode": "T0A1N0",
"Province": "AB",
"Direction": "NW",
"Longitude": "-113.324026",
"Confidence": "0.7",
"Street Name": "47"
},
{
"id": 26,
"City": "BON ACCORD",
"Type": "AVE",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "54",
"Street": "52 AVE",
"Latitude": "53.831789",
"PostCode": "T0A1N0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.319637",
"Confidence": "0.7",
"Street Name": "52"
},
{
"id": 27,
"City": "BON ACCORD",
"Type": "AVE",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "55",
"Street": "52 AVE",
"Latitude": "53.831789",
"PostCode": "T0A1N0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.319637",
"Confidence": "0.7",
"Street Name": "52"
},
{
"id": 28,
"City": "BON ACCORD",
"Type": "AVE",
"Unit": "",
"Count": "1",
"aType": "RES",
"Number": "56",
"Street": "52 AVE",
"Latitude": "53.831789",
"PostCode": "T0A1N0",
"Province": "AB",
"Direction": "",
"Longitude": "-113.319637",
"Confidence": "0.7",
"Street Name": "52"
},
{
"id": 29,
"City": "Bon Accord",
"Type": "AVE",
...
curl --location --request GET 'https://zylalabs.com/api/1473/canada+postal+codes+api/1219/get+canada+info' --header 'Authorization: Bearer YOUR_API_KEY'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, look at the βX-Zyla-API-Calls-Monthly-Remainingβ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
1,219ms
Service Level:
100%
Response Time:
917ms
Service Level:
100%
Response Time:
876ms
Service Level:
100%
Response Time:
1,148ms
Service Level:
100%
Response Time:
226ms
Service Level:
100%
Response Time:
190ms
Service Level:
100%
Response Time:
1,303ms
Service Level:
100%
Response Time:
537ms
Service Level:
100%
Response Time:
132ms
Service Level:
100%
Response Time:
361ms
Service Level:
100%
Response Time:
722ms
Service Level:
100%
Response Time:
492ms
Service Level:
100%
Response Time:
202ms
Service Level:
100%
Response Time:
112ms
Service Level:
100%
Response Time:
689ms
Service Level:
100%
Response Time:
205ms
Service Level:
100%
Response Time:
239ms