Mock sample for your project: trash nothing API

Integrate with "trash nothing API" from trashnothing.com in no time with Mockoon's ready to use mock sample

trash nothing

trashnothing.com

Version: 1.2


Use this API in your project

Speed up your application development by using "trash nothing API" ready-to-use mock sample. Mocking this API will allow you to start working in no time. No more accounts to create, API keys to provision, accesses to configure, unplanned downtime, just work.
It also improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.

Description

This is the REST API for trashnothing.com.
To learn more about the API or to register your app for use with the API
visit the trash nothing Developer page.
NOTE: All date-time values are UTC
and are in ISO 8601 format (eg. 2019-02-03T01:23:53).

Other APIs in the same category

Discourse API Documentation

discourse.local
This page contains the documentation on how to use Discourse through API calls.
> Note: For any endpoints not listed you can follow the
reverse engineer the Discourse API
guide to figure out how to use an API endpoint.
Request Content-Type
The Content-Type for POST and PUT requests can be set to application/x-www-form-urlencoded,
multipart/form-data, or application/json.
Endpoint Names and Response Content-Type
Most API endpoints provide the same content as their HTML counterparts. For example
the URL /categories serves a list of categories, the /categories.json API provides the
same information in JSON format.
Instead of sending API requests to /categories.json you may also send them to /categories
and add an Accept: application/json header to the request to get the JSON response.
Sending requests with the Accept header is necessary if you want to use URLs
for related endpoints returned by the API, such as pagination URLs.
These URLs are returned without the .json prefix so you need to add the header in
order to get the correct response format.
Authentication
Some endpoints do not require any authentication, pretty much anything else will
require you to be authenticated.
To become authenticated you will need to create an API Key from the admin panel.
Once you have your API Key you can pass it in along with your API Username
as an HTTP header like this:
Boolean values
If an endpoint accepts a boolean be sure to specify it as a lowercase
true or false value unless noted otherwise.

Clubhouse API

clubhouseapi.com
Clubhouse API

Bufferapp

Social media management for marketers and agencies

Contribly

contribly.com

StatSocial Platform API

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 [email protected] to obtain a test API key

Tweets and Users

API Reference — Labs v2

trash nothing

trashnothing.com
This is the REST API for trashnothing.com.
To learn more about the API or to register your app for use with the API
visit the trash nothing Developer page.
NOTE: All date-time values are UTC
and are in ISO 8601 format (eg. 2019-02-03T01:23:53).

Twitter API v2

Twitter API v2 available endpoints

Wedpax

wedpax.com

Mastodon API

API for GNU Social-compatible microblogging server

RiteKit API

ritekit.com
RiteKit API is based on REST principles.
Authentication uses standard OAuth 2.0 process
##Getting started
Sign up for RiteKit
Go to developer dashboard
Click "Create a token" button to get your Client ID and Client secret
When you reach your free limit of calls per month, upgrade to paid tiers
Options for authorizing API Calls
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/multiple-hashtags?tags=php&client_id=292c6912e7710c838347ae178b4a