This article covers creating a Google Maps API key inWP Google Maps.

  1. Generate Google Ajax Api Key Free
  2. Google Ajax Api Documentation
  3. Generate Google Ajax Api Key Finder
  4. Google Ajax Api Search

Option 1: Using our Cloud API Key

  1. Whilst it is true that V3 of the Google Maps API does not require an API key, it is there for a reason. Google recently introduced the following usage limits. Web sites and applications using each of the Maps API may at no cost generate.
  2. These instructions apply for non Google Cloud Platform (GCP) APIs. If you're building a GCP application, see using API keys for GCP. If your client application does not use OAuth 2.0, then it must include an API key when it calls an API that's enabled within a Google Cloud Platform project.
  3. REST authentication and exposing the API key. Ask Question Asked 9 years ago. I'd have to embed the api key in the ajax call so that it gets passed to the that point someone can see the API key. Create a CSRF token from the API key and the random value from the cookie, and sign it. (Rather than keeping a list of tokens on.
  4. Apr 10, 2020 The API key created dialog displays your newly created API key. The new API key is listed on the Credentials page under API keys. (Remember to restrict the API key before using it in production.) Add the API key to your request. You must include an API key with every Geocoding API request. In the following example, replace YOURAPI.

For: Standard Users

Navigate over to our Cloud API Key purchase page and get an API key with the click of a button.

How to use an API Key for an Ajax call? I am trying to include an API key for the first time from New York Times API. Sign up using Google.

Option 2: Creating a Google Maps API Key

For: Technical Users

Getting Started

Navigate to the Google Maps Platform and click on the Get Started button in the top right corner of the site.

Enable Google Maps Platform

Select the Maps, Routes and Places check boxes and press continue.

Select a Project

If this is your first time creating an API key, you will have to create a Project first.

  • Give your Project a name.
  • Click the next button at the bottom-right of the window.

Set up your billing

Wait for the billing prompt and select Create Billing Account

Select your country and accept Terms of Service. Click Continue.

Enter your customer info (details) and card information.


Please note that you a 12-month or $300 credit free trial. When this free trial ends, you will get up to 28 000 map requests per month and 40 000 direction calls per month, free of charge. You will only be billed when your usage exceeds your monthly $200 credit limit.

For more information about the free trial, please refer to Google’s documentation.

Once your billing has been set up, you can move onto creating your API Key.

Generate Your API Key

You will now receive your API Key

  • Copy the API key to your clipboard.
  • Return to your WordPress site and paste the API Key into the box labeled “Google Maps API Key” at the top of the page at WordPress Dashboard → Maps→ Settings→ Advanced.
  • Click the Save Settings button.

After pasting the API Key to your WordPress site and saving the settings, return to the Google API Manager. You will want to restrict access to your API Key to avoid having it “hijacked” and going over your quota. Click the API Console link on the Enable Google Maps Platformwindow as shown above.

Select HTTP referrers (web sites) and enter the following domains under Accept requests from these HTTP referrers (web sites) replacing with your domain name.

Please note that the Google Maps API is very specific about how this field is formatted – please use exactly this format.

Click the Save button to save your Key Restrictions.

Enable Required API Functions

Now you need to enable the required API functions for your project. Click the Library link in the API Manager sidebar menu. Click on the Google Maps JavaScript API panel.

The JavaScript API will probably already be enabled as shown in the screenshot below. If the JavaScript API is not enabled, then click Enable on the Google Maps Javascript API window.

The following is a quick list of all the APIs that need to be enabled along with your JavaScript API:

  • Google Maps JavaScript API
  • Google Maps Geocoding API
  • Google Places API
  • Google Maps Directions API

API Changes Introduced By Google

Recently, Google Maps have announced certain API changes that will affect everyone using Google Maps. Essentially, Google has implemented new pay-as-you-go pricing plans for their API. On this plan mention, users will get up to 28 000 map requests per month and 40 000 direction calls per month, free of charge.

Other rates and limits found here.

The only thing required from existing users, is to add a credit card to their Google Console account if they haven’t done so already. Unfortunately, the changes introduces are completely out of our control. However, WP Google Maps will be implementing an Open Street Maps integration for the users that would like an alternative solution to Google Maps.

For more information and questions on this topic, please refer to the FAQ for the new Google Maps API changes.

This article covered creating a Google Maps API key inWP Google Maps. If you need further assistance or are having other issues with the plugins, feel free to visit our Support Desk.

Was this article helpful to you?


This document is intended for developers who want to write applications that interact with YouTube. It explains basic concepts of YouTube and of the API itself. It also provides an overview of the different functions that the API supports.

Before you start

  1. You need a Google Account to access the Google API Console, request an API key, and register your application.

  2. Create a project in the Google Developers Console and obtain authorization credentials so your application can submit API requests.

  3. After creating your project, make sure the YouTube Data API is one of the services that your application is registered to use:

    1. Go to the API Console and select the project that you just registered.
    2. Visit the Enabled APIs page. In the list of APIs, make sure the status is ON for the YouTube Data API v3.
  4. If your application will use any API methods that require user authorization, read the authentication guide to learn how to implement OAuth 2.0 authorization.

  5. Select a client library to simplify your API implementation.

  6. Familiarize yourself with the core concepts of the JSON (JavaScript Object Notation) data format. JSON is a common, language-independent data format that provides a simple text representation of arbitrary data structures. For more information, see

Resources and resource types

A resource is an individual data entity with a unique identifier. The table below describes the different types of resources that you can interact with using the API.

activityContains information about an action that a particular user has taken on the YouTube site. User actions that are reported in activity feeds include rating a video, sharing a video, marking a video as a favorite, and posting a channel bulletin, among others.
channelContains information about a single YouTube channel.
channelBannerIdentifies the URL to use to set a newly uploaded image as the banner image for a channel.
channelSectionContains information about a set of videos that a channel has chosen to feature. For example, a section could feature a channel's latest uploads, most popular uploads, or videos from one or more playlists.
guideCategoryIdentifies a category that YouTube associates with channels based on their content or other indicators, such as popularity. Guide categories seek to organize channels in a way that makes it easier for YouTube users to find the content they're looking for. While channels could be associated with one or more guide categories, they are not guaranteed to be in any guide categories.
i18nLanguageIdentifies an application language that the YouTube website supports. The application language can also be referred to as a UI language.
i18nRegionIdentifies a geographic area that a YouTube user can select as the preferred content region. The content region can also be referred to as a content locale.
playlistRepresents a single YouTube playlist. A playlist is a collection of videos that can be viewed sequentially and shared with other users.
playlistItemIdentifies a resource, such as a video, that is part of a playlist. The playlistItem resource also contains details that explain how the included resource is used in the playlist.
search resultContains information about a YouTube video, channel, or playlist that matches the search parameters specified in an API request. While a search result points to a uniquely identifiable resource, like a video, it does not have its own persistent data.
subscriptionContains information about a YouTube user subscription. A subscription notifies a user when new videos are added to a channel or when another user takes one of several actions on YouTube, such as uploading a video, rating a video, or commenting on a video.
thumbnailIdentifies thumbnail images associated with a resource.
videoRepresents a single YouTube video.
videoCategoryIdentifies a category that has been or could be associated with uploaded videos.
watermarkIdentifies an image that displays during playbacks of a specified channel's videos. The channel owner can also specify a target channel to which the image links as well as timing details that determine when the watermark appears during video playbacks and then length of time it is visible.

Note that, in many cases, a resource contains references to other resources. For example, a playlistItem resource's snippet.resourceId.videoId property identifies a video resource that, in turn, contains complete information about the video. As another example, a search result contains either a videoId, playlistId, or channelId property that identifies a particular video, playlist, or channel resource.

Supported operations

Generate Google Ajax Api Key Free

The following table shows the most common methods that the API supports. Some resources also support other methods that perform functions more specific to those resources. For example, the videos.rate method associates a user rating with a video, and the thumbnails.set method uploads a video thumbnail image to YouTube and associates it with a video.

listRetrieves (GET) a list of zero or more resources.
insertCreates (POST) a new resource.
updateModifies (PUT) an existing resource to reflect data in your request.
deleteRemoves (DELETE) a specific resource.

The API currently supports methods to list each of the supported resource types, and it supports write operations for many resources as well.

The table below identifies the operations that are supported for different types of resources. Operations that insert, update, or delete resources always require user authorization. In some cases, list methods support both authorized and unauthorized requests, where unauthorized requests only retrieve public data while authorized requests can also retrieve information about or private to the currently authenticated user.

Supported Operations
search result

Quota usage

The YouTube Data API uses a quota to ensure that developers use the service as intended and do not create applications that unfairly reduce service quality or limit access for others. All API requests, including invalid requests, incur at least a one-point quota cost. You can find the quota available to your application in the API Console.

Projects that enable the YouTube Data API have a default quota allocation of 10 thousand units per day, an amount sufficient for the overwhelming majority of our API users. Default quota, which is subject to change, helps us optimize quota allocations and scale our infrastructure in a way that is more meaningful to our API users. You can see your quota usage on the Usage tab for the API in the Google Developer's Console.

Google Ajax Api Documentation

Note: If you reach the quota limit, you can request additional quota on the Quotas tab in the Developer's Console.

Note that projects that had enabled the YouTube Data API before April 20, 2016, have a different default quota for that API.

Calculating quota usage

Google calculates your quota usage by assigning a cost to each request, but the cost is not the same for each request. Two primary factors influence a request's quota cost:

  1. Different types of operations have different quota costs.

    • A simple read operation that only retrieves the ID of each returned resource has a cost of approximately 1 unit.
    • A write operation has a cost of approximately 50 units.
    • A video upload has a cost of approximately 1600 units.
  2. Read and write operations use different amounts of quota depending on the number of resource parts that each request retrieves. Note that insert and update operations write data and also return a resource. So, for example, inserting a playlist has a quota cost of 50 units for the write operation plus the cost of the returned playlist resource.

    As discussed in the following section, each API resource is divided into parts. For example, a playlist resource has two parts, snippet and status, while a channel resource has six parts and a video resource has 10. Each part contains a group of related properties, and the groups are designed so that your application only needs to retrieve the types of data that it actually uses.

    An API request that returns resource data must specify the resource parts that the request retrieves. Each part then adds approximately 2 units to the request's quota cost. As such, a videos.list request that only retrieves the snippet part for each video might have a cost of 3 units. However, a videos.list request that retrieves all of the parts for each resource might have a cost of around 21 quota units.

With these rules in mind, you can estimate the number of read, write, or upload requests that your application could send per day without exceeding your quota. For example, if you have a daily quota of 1,000,000 units, your application could have any of the following approximate limits:

  • 200,000 read operations that each retrieve two resource parts.
  • 10,000 write operations and 90,000 additional read operations that each retrieve two resource parts.
  • 400 video uploads, 1500 write operations, and 50,000 read operations that each retrieve two resource parts.

Important: Only retrieving the resource parts that your application needs conserves your daily quota and make the entire system more efficient.

Partial resources

The API allows, and actually requires, the retrieval of partial resources so that applications avoid transferring, parsing, and storing unneeded data. This approach also ensures that the API uses network, CPU, and memory resources more efficiently.

The API supports two request parameters, which are explained in the following sections, that enable you to identify the resource properties that should be included in API responses.

  • The part parameter identifies groups of properties that should be returned for a resource.
  • The fields parameter filters the API response to only return specific properties within the requested resource parts.

How to use the part parameter

The part parameter is a required parameter for any API request that retrieves or returns a resource. The parameter identifies one or more top-level (non-nested) resource properties that should be included in an API response. For example, a video resource has the following parts:

  • snippet
  • contentDetails
  • fileDetails
  • player
  • processingDetails
  • recordingDetails
  • statistics
  • status
  • suggestions
  • topicDetails

All of these parts are objects that contain nested properties, and you can think of these objects as groups of metadata fields that the API server might (or might not) retrieve. As such, the part parameter requires you to select the resource components that your application actually uses. This requirement serves several purposes:

Google ajax search api
  • It lets you manage your API quota usage. If you increase the number of parts you retrieve in API responses, your API usage increases accordingly, and your available quota decreases.
  • It reduces latency by preventing the API server from spending time retrieving metadata fields that your application doesn't use.
  • It reduces bandwidth usage by reducing (or eliminating) the amount of unnecessary data that your application might retrieve.

Over time, as resources add more parts, these benefits will only increase since your application will not be requesting newly introduced properties that it doesn't support.

How to use the fields parameter

The fields parameter filters the API response, which only contains the resource parts identified in the part parameter value, so that the response only includes a specific set of fields. The fields parameter lets you remove nested properties from an API response and thereby further reduce your bandwidth usage. (The part parameter cannot be used to filter nested properties from a response.)

The following rules explain the supported syntax for the fields parameter value, which is loosely based on XPath syntax:

  • Use a comma-separated list (fields=a,b) to select multiple fields.
  • Use an asterisk (fields=*) as a wildcard to identify all fields.
  • Use parentheses (fields=a(b,c)) to specify a group of nested properties that will be included in the API response.
  • Use a forward slash (fields=a/b) to identify a nested property.

Generate Google Ajax Api Key Finder

In practice, these rules often allow several different fields parameter values to retrieve the same API response. For example, if you want to retrieve the playlist item ID, title, and position for every item in a playlist, you could use any of the following values:

  • fields=items/id,playlistItems/snippet/title,playlistItems/snippet/position
  • fields=items(id,snippet/title,snippet/position)
  • fields=items(id,snippet(title,position))

Note: As with all query parameter values, the fields parameter value must be URL encoded. For better readability, the examples in this document omit the encoding.

Sample partial requests

The examples below demonstrate how you can use the part and fields parameters to ensure that API responses only include the data that your application uses:

  1. Example 1 returns a video resource that includes four parts as well as kind and etag properties.
  2. Example 2 returns a video resource that includes two parts as well as kind and etag properties.
  3. Example 3 returns a video resource that includes two parts but excludes kind and etag properties.
  4. Example 4 returns a video resource that includes two parts but excludes kind and etag as well as some nested properties in the resource's snippet object.
Coments are closed
Scroll to top