Don't miss this post : Steps to Download Files Directly in Blogger.
What is the Blogger API and what would you be able to do with it?
An API, or Application Package Interface is a situated of
summons you can call, or interface with, from an outer provision. The engineers
of a requisition furnishes Apis when they need other engineer to make
applications and interface with their own.
Correspondingly, the Blogger group has made an API of its
own that permits outer engineers to associate with the Blogger content
administration framework. With this API, you can;
- Add posts, pages and remarks from your Blogger web journal to a non-blogger site
- Create desktop programming that permits clients to make or alter Blogger posts from their desktop Pcs
- Create browser and versatile based applications that serve the same reason as above.
Basics steps a developer must know :
To start with, you have to know a percentage of the
fundamentals of items and assets accessible in the API. There are five sorts of
assets presently accessible.
- Pages - An online journal has static pages which inherit from the site (as tyke articles).
- Blogs - A web journal asset speaks to a full Blogger blog. A client may have more than one Blogger writes, so the control of different sites is took care of by the websites asset. You can utilize it to record all the websites a client has entry to, or get a solitary blog by its ID.
- Comments - A remark asset speaks to a remark on a blog entry, and is intelligently a youngster object of the individual post asset. A remarks accumulation is a rundown of all remarks under a posts (guardian) asset.
- Posts - A post asset speaks to a post on a website, and every is a tyke of the online journal asset. A posts accumulation holds all the post assets inside a site asset.
- Users - A client asset speaks to a non-unnamed client, and is utilized to distinguish the creator of a blog entry, page, or remark. A clients gathering is a rundown of all the (worldwide) client assets on Blogger. For protection explanations, a rundown of every last one of clients on Blogger can't be recorded. Notwithstanding, you can recover your own particular client asset by your interesting ID (or by utilizing the self identifier)
Blogger API Operations
Here is a rundown of routines as depicted in the Blogger API
v3 reference.
Operation
|
Description
|
REST HTTP mappings
|
list
|
Lists
all resources within a collection.
|
GET on a
collection URI.
|
get
|
Gets a
specific resource.
|
GET on a
resource URI.
|
getByUrl
|
Gets a
resource, looking it up by URL.
|
GET with
the URL passed in as a parameter.
|
getByPath
|
Gets a
resource by looking it up by its path.
|
GET with
the Path passed in as a parameter.
|
listByUser
|
Lists
resources owned by a User.
|
GET on a
user owned collection.
|
search
|
Search
for resources, based on a query parameter.
|
GET on a
Search URL, with the query passed in as a parameter.
|
insert
|
Create
a resource in a collection.
|
POST on a
collection URI.
|
delete
|
Deletes
a resource.
|
DELETE on a
resource URI.
|
patch
|
Update
a resource, using Patch semantics.
|
PATCH on a
resource URI.
|
update
|
Update
a resource.
|
PUT on a
resource URI.
|
The accompanying table matches the asset sorts in the API
(which we talked about prior) with the techniques they help. more information please visit : https://developers.google.com/blogger/docs/3.0/getting_started
Resource Type
|
Supported Methods
|
||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| list | get | getByUrl | getByPath | listByUser | search | insert | delete | patch | update | ||||
| Blogs | no | yes | yes | no | yes | no | no | no | no | no | |||
| Posts | yes | yes | no | yes | no | yes | yes | yes | yes | yes | |||
| Comments | yes | yes | no | no | no | no | no | no | no | no | |||
| Pages | yes | yes | no | no | no | no | no | no | no | no | |||
| Users | no | yes | no | no | no | no | no | no | no | no | |||
You can utilize these routines to improve a completely
practical Blogger application. There are different methods for conjuring these
systems. You can utilize HTTP customer side orders, or from Javascript. You can
likewise improve utilizing customer libraries on any of the accompanying
stages.
- PHP
- .NET
- Ruby
- Java
- Python
- JavaScript
- Go
- GWT
- Node.js
- Objective-C
We will speak all the more about these customer libraries,
and calling routines in a future post. Meanwhile, when you have any inquiries
with respect to the practicality of this API or its routines, please don't
hesitate to ask in the remarks segment beneath. Cheers :)
Like the Post? Share with your Friends:-
0 comments: