OpenAPI Directory | Cenit Admin

Social media management for marketers and agencies

API for access to the data within Blogger.

Builds on top of the Google+ platform.

Description of Instagram RESTful API. Current limitations: * Instagram service does not support [cross origin headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS) for security reasons, therefore it is not possible to use Swagger UI and make API calls directly from browser. * Modification API requests (`POST`, `DELETE`) require additional security [scopes](https://instagram.com/developer/authorization/) that are available for Apps [created on or after Nov 17, 2015](http://instagram.com/developer/review/) and started in [Sandbox Mode](http://instagram.com/developer/sandbox/). * Consider the [Instagram limitations](https://instagram.com/developer/limits/) for API calls that depends on App Mode. **Warning:** For Apps [created on or after Nov 17, 2015](http://instagram.com/developer/changelog/) API responses containing media objects no longer return the `data` field in `comments` and `likes` nodes. Last update: 2015-11-28

Medium’s unofficial API documentation using OpenAPI specification. # Official API Official API document can also be viewed for most up to date API spec at [https://github.com/Medium/medium-api-docs](https://github.com/Medium/medium-api-docs). Developer Blog - [Welcome to the Medium API](https://medium.com/blog/welcome-to-the-medium-api-3418f956552)

RiteKit API is based on REST principles. Authentication uses standard OAuth 2.0 process ##Getting started 1. Sign up for [RiteKit](https://ritekit.com/) 1. Go to [developer dashboard](https://ritekit.com/developer/dashboard/) 1. Click "Create a token" button to get your **Client ID** and **Client secret** 1. Study the documentation below (for more info on oAuth go to http://oauth.net/) 1. When you reach your free limit of calls per month, [upgrade to paid tiers](https://ritekit.com/developer/) ## Options for authorizing API Calls #### A) Using Client ID directly You can directly connect to our API using your **client ID** by sending it as a GET query parameter. This option is simple (no need for oAuth) but it should be used only in case the Client ID is not exposed publicly. GET https://api.ritekit.com/v1/stats/basic/php?client_id=292c6912e7710c838347ae178b4a #### B) Using Access token (oAuth 2.0) Once you have valid Access token, you can access our API by sending the token in the Authorization header bearer or as a query Access token. See the oAuth 2.0 section to learn how to get Access token and keep refreshing it. Authorization: Bearer xxxx Or GET https://api.ritekit.com/v1/stats/basic/php?access_token=292c6912e7710c838347ae178b4a ## oAuth 2.0 ![oauthschema](https://cdn.ritekit.com/assets/media/1/oauth-simple.png) ### Get Access Token Use your Client Credentials to get the token. POST https://ritekit.com/oauth/token grant_type=client_credentials &client_id=CLIENT_ID &client_secret=CLIENT_SECRET &scope=data - [required] grant_type - client_credentials - [required] client_id (CLIENT ID) - [required] client_secret (CLIENT SECRET) - [required] (always use scope=data) #### Response { "access_token":292c6912e7710c838347ae178b4a, "token_type":"bearer", "expires_in": 3600, "refresh_token":292c6912e7710c838347ae178b4a, } ### Refresh token Every Access token has a lifetime. You can use Refresh token to request a new Access Token. POST https://ritekit.com/oauth/token grant_type=refresh_token &refresh_token=REFRESH_TOKEN &client_id=CLIENT_ID &scope=data - [required] grant_type - refresh_token - [required] refresh_token - (REFRESH TOKEN) the refresh token you got from the expired token - [required] client_id (CLIENT ID) - [required] client_secret (CLIENT SECRET) - [required] scope (always use scope=data) #### Response { "access_token":292c6912e7710c838347ae178b4a, "token_type":"bearer", "expires_in": 3600, "refresh_token":292c6912e7710c838347ae178b4a, }

Semantria applies Text and Sentiment Analysis to tweets, facebook posts, surveys, reviews or enterprise content.

API Reference:

The StatSocial API is organized around REST. Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which can be understood by off-the-shelf HTTP clients, and we support cross-origin resource sharing to allow you to interact securely with our API from a client-side web application (remember that you should never expose your secret API key in any public website's client-side code). JSON will be returned in all responses from the API, including errors (though if you're using API bindings, we will convert the response to the appropriate language-specific object).

Contact help@statsocial.com to obtain a test API key

8 api specs