Mock sample for your project: カラーミーショップアプリストア API

Who is this for?
This documentation is for developers creating their own integration with Feedback's API. If you are doing a standard integration, there's a really easy Javascript integration that you should know about before you go to the effort of building your own integration.
Authentication
API calls generally need to be authenticated. Generate an API Key at https://feedback.pendo.io/app/#/vendor/settings?section=integrate. This key should then be added to every request as a request header named 'auth-token' (preferred), or as a query parameter named 'auth-token'.
Endpoint
API endpoint is https://api.feedback.eu.pendo.io / https://api.feedback.us.pendo.io depending where your datacenter is located.
Notes
API endpoints are being added to this documentation as needed by customers. If you don't see an endpoint you need please contact support and if it exists we'll publish the docs here. The 'try it out' feature on this documentation page will probably be blocked by your browser because the Access-Control-Allow-Origin header has its value set by the Feedback server depending on your hostname.
Generating client code
This documentation is automatically generated from an OpenAPI spec available here. You can use Swagger to auto-generate API client code in many languages using the Swagger Editor

The Charity API allows third-party developers to search for and access details on supported charitable organizations.

Note: This is a (Limited Release) API available only to select developers approved by business units. Retrieves the authenticated user's account profile information. It can be used to let users log into your app or site using eBay, which frees you from needing to store and protect user's PII (Personal Identifiable Information) data.

The Metadata API has operations that retrieve configuration details pertaining to the different eBay marketplaces. In addition to marketplace information, the API also has operations that get information that helps sellers list items on eBay.

The DocuSign REST API provides you with a powerful, convenient, and simple Web services API for interacting with DocuSign.

The Negotiations API gives sellers the ability to proactively send discount offers to buyers who have shown an "interest" in their listings. By sending buyers discount offers on listings where they have shown an interest, sellers can increase the velocity of their sales. There are various ways for a buyer to show interest in a listing. For example, if a buyer adds the listing to their Watch list, or if they add the listing to their shopping cart and later abandon the cart, they are deemed to have shown an interest in the listing. In the offers that sellers send, they can discount their listings by either a percentage off the listing price, or they can set a new discounted price that is lower than the original listing price. For details about how seller offers work, see Sending offers to buyers.

The REST API of BeezUP system
Overview
The REST APIs provide programmatic access to read and write BeezUP data.
Basically, with this API you will be able to do everything like you were with your browser on https://go.beezup.com !
The main features are:
Register and manage your account
Create and manage and share your stores with your friends/co-workers.
Import your product catalog and schedule the auto importation
Search the channels your want to use
Configure your channels for your catalogs to export your product information:
cost and general settings
category and columns mappings
your will be able to create and manage your custom column
put in place exlusion filters based on simple conditions on your product data
override product values
get product vision for a channel catalog scope
Analyze and optimize your performance of your catalogs on all yours channels with different type of reportings by day, channel, category and by product.
Automatize your optimisation by using rules!
And of course... Manage your orders harvested from all your marketplaces:
Synchronize your orders in an uniformized way
Get the available actions and update the order status
...and more!
Authentication credentials
The public API with the base path /v2/public have been put in place to give you an entry point to our system for the user registration, login and lost password. The public API does not require any credentials.
We give you the some public list of values and public channels for our public commercial web site www.beezup.com.
The user API with the base path /v2/user requires a token which is available on this page:
https://go.beezup.com/Account/MyAccount
Things to keep in mind
API Rate Limits
The BeezUP REST API is limited to 100 calls/minute.
Media type
The default media type for requests and responses is application/json. Where noted, some operations support other content types. If no additional content type is mentioned for a specific operation, then the media type is application/json.
Required content type
The required and default encoding for the request and responses is UTF8.
Required date time format
All our date time are formatted in ISO 8601 format: 2014-06-24T16:25:00Z.
Base URL
The Base URL of the BeezUP API Order Management REST API conforms to the following template.
https://api.beezup.com
All URLs returned by the BeezUP API are relative to this base URL, and all requests to the REST API must use this base URL template.
You can test our API on https://api-docs.beezup.com/swagger-ui\\
You can contact us on gitter, #BeezUP/API

Import your orders, retrieve your orders and generate labels.

This is the koomalooma Partner API. koomalooma is the first Loyalty BPaaS (Business Process as a Service) for mobile and web companies. With koomalooma merchants issue points for actions their customers / users make on your mobile or web store, for example a purchase or a referral. koomalooma takes care of all the rest, from signing up users, keeping track of points and delivering rewards in over 80 countries. koomalooma offers an easy to integrate API and web backend to configure loyalty campaigns and track performance. You can find more at http://support.koomalooma.com

Just Eat API
Just Eat offers services for our various business partners and our consumer applications.
How you interact with the API depends on the services you wish to interact with.
Security
HTTPS
All api calls and callbacks require HTTPS. Your service will need a valid SSL certificate and be accessible via the standard SSL port (port 443).
Making an API request
Some API calls require an API key, to authenticate the partner calling the API.

Use the Taxonomy API to discover the most appropriate eBay categories under which sellers can offer inventory items for sale, and the most likely categories under which buyers can browse or search for items to purchase. In addition, the Taxonomy API provides metadata about the required and recommended category aspects to include in listings, and also has two operations to retrieve parts compatibility information.