Skip to main content

Google Search API

Place Search API :


Below detail coming from above link

Need to first register for the API key then you are able to use below link services:
The Google Places API uses an API key to identify your application. API keys are managed through the Google APIs Console. You'll need your ownserver API key before you can begin using the API. To activate the Places API and create your key:
  1. Visit the Google APIs Console and log in with your Google account.
  2. A default project called API Project is created for you when you first log in to the APIs Console. You can use the project, or create a new one by clicking the API Project button at the top of the window and selecting Create. Google Maps API for Work customers must use the API project created for them as part of their Google Places API for Work purchase.
  3. Click the Services link in the left-hand navigation panel.
  4. Click the status switch (the on/off button) next to the Places API entry. The switch slides to ON.
  5. Click API Access in the left-hand navigation panel.
  6. Click Create new Server key.
  7. Enter one or more server IP addresses if you wish to restrict the servers that can send API requests.
  8. Click Create. Your API key appears under the heading Key for server apps (with IP locking).
Note: The Places API does not work with an Android or iOS API key.
After that you are ready to use below web services: 

https://developers.google.com/places/documentation/search


Labels:

Comments

Post a Comment

Popular posts from this blog

iOS Beta Builder

Download iOS Beta Builder 1.0 While I’ve been working on iOS for awhile, I don’t have a ton of experience with Cocoa proper – I’m sure there are probably some issues that slipped through the testing process. Screenshots:   How Does It Work? 1. Build your .ipa file using Xcode’s ‘Build and Archive’ option. Choose ‘Save to Disk’. 2. Launch BetaBuilder (or drag and drop the .ipa on to it). If you need to, select your .ipa file. The app should pre-fill the other details. 3. Enter your intended deployment URL. This is the URL on the Web where your beta will be posted / viewed in a browser. This info gets baked into the deployment file. 4. Hit ‘Generate Deployment Files’ and pick a location to output the files. That’s it – just upload the generated files to your Web server and then hit the URL in the device’s browser. BetaBuilder simply generates the HTML and manifest files needed to make wireless distribution work. As a convenience, it also bundles an iTunes install...
2 comments
Read more

Fixed : App crash on update with core data changes

Why migration required ? When the model does not match the store, a migration is required. In order to perform a migration, Core Data (technically, an instance of NSMigrationManager) requires these things: The destination managed object model (the one with the changes) A managed object model that can open the existing store The ability to infer mapping between the two models (for a lightweight migration), or a manual mapping model Permission to attempt to perform an automatic migration (for a lightweight migration) It is therefore absolutely essential that you never make changes to the managed object model for a released version of an app. That is, if your app is already in the App Store,  don’t change a single thing in that version of the managed object model . Solution for the Crash while update an application from the app store: Create a  new version  of the managed object model! This reminds me to mention some other best practices to adopt when worki...
3 comments
Read more