Overview

The VAMedPulse API is composed of “resources” that you can manipulate through a REST API. All resources can be interacted with a variety of HTTP Methods, and most support methods to list, create, read, update, and delete either specific or all resources. All resources have an accompanying resource “id” that is generated by the VAMedPulse servers and is usually how you reference resources for manipulation via the API.

A VAMedPulse resource URI is composed of 3 components, the host url, the api version, and the resource identifier.

Authentication

You must authenticate to use the VAMedPulse REST API. This can be done either through an API Key or an API Access Token. By default, a user will need to be issued an API_KEY via Management Console or via the Users API. An ACCESS_TOKEN can only be issued via the Users API.

Both authentication schemes require that you provide the key or token using the HTTP Basic Authorization Header; you must provide the API_KEY or ACCESS_TOKEN as the username and an empty string as the password.

For example, to make a request with an API_KEY of 00000000-0000-0000-0000-000000000000, first append a colon and Base64 encode the string. The resulting header is the following:

Authorization: Basic MDAwMDAwMDAtMDAwMC0wMDAwLTAwMDAtMDAwMDAwMDAwMDAwOg==

API Keys

An API_KEY does not expire unless explictly expired via the Management Console or via the Users API. The API_KEY is the default access method for all APIs. We recommend that you ensure these are stored safely as they do not expire and could have full access to the VAMedPulse REST API. We recommend that you use these for Administrators, Owners, and Developers and consider using anACCESS_TOKEN for regular users.

Provider API

Create a Provider

api/VamedProviderApi/Insert

Sample in C#

Provider Search

api/VamedProviderApi/SelectSkipAndTake

For example, if ther are 200 records (totalRecordCount), take only 10 records (numberOfRecordsToRetrieve), starting from the first index (startRetrievalFromRecordIndex = 0)

RSS feed for Blog

Note:These full-site feeds are real-time enabled; developers can subscribe to low-latency updates by using the PubSubHubbub protocol.

Atom 1.0: http://dmvdatadrivers.blogspot.com/feeds/posts/default
RSS 2.0: http://dmvdatadrivers.blogspot.com/feeds/posts/default?alt=rss

Comments-only feed:

Atom 1.0: http://dmvdatadrivers.blogspot.com/feeds/comments/default
RSS 2.0: http://dmvdatadrivers.blogspot.com/feeds/comments/default?alt=rss

Label-specific site feed:

Atom 1.0: http://www.googleblog.blogspot.com/feeds/posts/default/-/privacy
RSS 2.0: http://www.googleblog.blogspot.com/feeds/posts/default?alt=rss/-/privacy

Individual post comment feed:

Note: You can find the postId of an individual post from the Posting | Edit Posts tab. Simply mouseover the 'Edit' link next to a particular post, and that postId will be displayed in your browser's status bar.

Atom 1.0: http://dmvdatadrivers.blogspot.com/feeds/postId/comments/default
RSS 2.0: http://dmvdatadrivers.blogspot.com/feeds/postId/comments/default?alt=rss

Integration with WordPress (and other CMS)

Top of the page TABS

API