This is a generated connector for [Elastic Cloud API](https://cloud.elastic.co/api/v1/api-docs/spec.json) OpenAPI Specification.
This is a generated connector for [Einstein Vision and Einstein Language API](https://metamind.readme.io/reference#predictive-vision-service-api) OpenAPI specification. Allows you to access the Einstein Vision and Einstein Language services via the standard REST API calls. Use the APIs to programmatically work with datasets, labels, examples, models, and predictions.
This is a generated connector for [eBay Account API v1.6.3](https://developer.ebay.com/api-docs/sell/account/overview.html) OpenAPI Specification. The Account API provide capability to access configure their eBay seller accounts, including the seller''s policies (the Fulfillment Policy, Payment Policy, and Return Policy), opt in and out of eBay seller programs, configure sales tax tables, and get account information.
sinum Main Process BackEnd API documentation
This is a generated connector from [eDocs](https://www.opentext.com/products-and-solutions/industries/legal/legal-content-management-edocs) OpenAPI Specification. An API that allows interaction with the resources stored on an eDOCS DM Server.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Edco. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the EBOX. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This is a generated connector for [eBay Negotiation API v1.1.0](https://developer.ebay.com/api-docs/sell/negotiation/overview.html) OpenAPI Specification The Negotiations API provides capability to access sellers 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 "/api-docs/sell/static/marketing/offers-to-buyers.html" title="Selling Integration Guide">Sending offers to buyers.
This is a generated connector for [eBay Metadata API v1.4.1](https://developer.ebay.com) OpenAPI specification. '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.'
This is a generated connector for [eBay Listing API v1_beta.3.0](https://developer.ebay.com) OpenAPI specification. '<span class="tablenote"><b>Note:</b> This is a <a href="https://developer.ebay.com/api-docs/static/versioning.html#limited" target="_blank"> <img src="/cms/img/docs/partners-api.svg" class="legend-icon partners-icon" title="Limited Release" alt="Limited Release" />(Limited Release)</a> API available only to select developers approved by business units.</span><br /><br />Enables a seller adding an ad or item on a Partner''s site to automatically create an eBay listing draft using the item details from the Partner''s site.'
This is a generated connector for [eBay Compliance API v1.4.1](https://developer.ebay.com) OpenAPI specification. Service for providing information to sellers about their listings being non-compliant, or at risk for becoming non-compliant, against eBay listing policies.
This is a generated connector for [eBay Inventory API v1.13.0](https://developer.ebay.com/api-docs/sell/inventory/overview.html) OpenAPI Specification. The Inventory API is used to create and manage inventory, and then to publish and manage this inventory on an eBay marketplace. There are also methods in this API that will convert eligible, active eBay listings into the Inventory API model.
This is a generated connector for [eBay finances API v1.9.0](https://developer.ebay.com/api-docs/sell/finances/overview.html) OpenAPI Specification. The eBay Developers Program is hosted on the eBay Developer Site. The program provides information and services for the eBay developer community. This API is used to retrieve seller payouts and monetary transaction details related to those payouts. The finances API is used by sellers in eBay's managed payments program to retrieve seller payout information. The data provided through this public API is similar to the data that the seller will see under the Payments tab of Seller Hub in My eBay. With eBay's managed payments program, eBay manages the entire payments process, including the available payment methods, and shortly after a buyer's payment clears, eBay distributes payouts directly to the seller's preferred bank account.
This is a generated connector for [eBay Browse API v1.6.0](https://developer.ebay.com/api-docs/buy/browse/overview.html) OpenAPI Specification. The Browse API lets shoppers search for specific items by keyword, GTIN, category, charity, product, or item aspects and refine the results by using filters, such as aspects, compatibility, and fields values.
This is a generated connector for [eBay Account API v1.6.3](https://developer.ebay.com/api-docs/sell/account/overview.html) OpenAPI Specification. The Account API provide capability to access configure their eBay seller accounts, including the seller''s policies (the Fulfillment Policy, Payment Policy, and Return Policy), opt in and out of eBay seller programs, configure sales tax tables, and get account information.
The eBay platform offers an unprecedented opportunity to build a new eBay business or expand your current business, reach new customers, and create a potential new stream of revenue. Leverage the resources of the eBay Developers Program to tap into the eBay Marketplace with millions of active users globally, with tools and services that meet the diverse needs of buyers and sellers. Contact Support: Name: No Contact Email: email@example.com
This Open API specification serves as a standardized framework for describing and defining the capabilities of the EasyMetal API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
The eBay platform offers an unprecedented opportunity to build a new eBay business or expand your current business, reach new customers, and create a potential new stream of revenue. Leverage the resources of the eBay Developers Program to tap into the eBay Marketplace with millions of active users globally, with tools and services that meet the diverse needs of buyers and sellers. Contact Support: Name: No Contact Email: email@example.com
This is a generated connector for [EarthRef.org's FIESTA API v1.2.0](https://api.earthref.org/v1) OpenAPI Specification. [EarthRef.org](https://earthref.org) is a geoscience umbrella website for several data repositories. These repositories, unified under the mandate to preserve their respective data and promote scientific collaboration in their fields, are also disparate in their schemata. The Framework for Integrated Earth Science and Technology Applications (FIESTA) project is creating the tools to easily customize and manage these geoscience repositories and the FIESTA API is a core component of that solution. # Authentication The API is served over HTTPS thereby making HTTP Basic Authentication secure. The credentials are the username and password of an active EarthRef.org user account and provide access to that user's private workspace in any of EarthRef.org FIESTA repositories.
This collection is for the [Adding Extra Bags](https://duffel.com/docs/guides/adding-extra-bags) guide. # What do you need to start? This guide will go through the changes you need to make in the booking flow to be able to list and book services for any offer you want. It's important you know the basics of how to create a booking. If you are not familiar with how to create an order please heads over to our [Quick Start Guide](https://duffel.com/docs/guides/quick-start). This guide will start from an offer so make sure you grab an offer ID for a British Airways flight before we start. # Overview Baggages are a type of what we call available_services. Available services are specific to an offer but not surfaced through the API by default. The changes we'll make to work with available services are: 1. Retrieve an offer along with its available_services 2. Include services to order creation 3. See the services booked on an order
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Easy-connect. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
Administer eAdmin data through APIs
This Open API specification serves as a standardized framework for describing and defining the capabilities of the E-zlecenia. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
The DX Despatch Manager API provides access to create delivery and collection orders, print labels, view manifests, item tracking events and proof of delivery.
This collection is designed to pair with our [Getting Started with Stays integration guide](https://duffel.com/docs/guides/getting-started-with-stays) to walk you through how to integrate our search and book accommodation flow into your own product. In order to follow this guide, you'll need to: - [Sign up](https://app.duffel.com/join) for a Duffel Account (it takes about 1 minute!) - Create a test token from the "Access Tokens" page in your [Dashboard](https://app.duffel.com/) and paste it in the `Authorization` section of the Postman Collection (**Don't forget to hit save afterwards**) Our requests have a pre-defined sequence to replicate creating a booking in a real world scenario: - Searching for accommodation - Selecting an accommodation from the previous search to see available rates - Creating a quote to confirm rate & availability - Creating a booking from the selected quote **NOTE:** By running the requests in the sequence mentioned above, you'll get most fields automatically pre-filled for you.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the e-RS. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
Collection containing all the requests required to create a [Duffel Links](https://duffel.com/links) session for your users.
A walkthrough on how to go from nothing to your first booking using the Duffel API. In order to follow this guide, you'll need to: - [Sign up](https://app.duffel.com/join) for a Duffel Account (it takes about 1 minute!) - Create a test token from the "Access Tokens" page in your [Dashboard](https://app.duffel.com) and paste it in the `Authorization` section of the Postman Collection (**Don't forget to hit save afterwards**) Our requests have a pre-defined sequence to replicate creating a booking in a real world scenario: 1. Searching for Flights 2. Selecting an offer from the previous Search 3. Creating a booking from the selected offer **NOTE:** By running the requests in the sequence mentioned above, you'll get most fields automatically pre-filled for you.
This collection is for the [Cancelling an order](https://duffel.com/docs/guides/cancelling-an-order) guide. # Overview The order cancellation process happens in 3 steps: 1. You request a cancellation refund quote 2. You confirm your cancellation 3. You validate your order was cancelled
This collection is for the [Holding Orders and Paying Later](https://duffel.com/docs/guides/holding-orders-and-paying-later) guide. Holding an order allows you to hold space on a flight and pay for it at a later time. For example, perhaps your customer is booking a flight for a business trip and wants to hold their seat while they wait for their manager to approve the trip. In the industry, holding an order is sometimes referred to as deferred ticketing. We refer to orders that can be paid after booking as “Hold Orders”. You hold an order by creating an order without supplying payment, and then paying for it by a particular time indicated in the order.
A walkthrough on how to go from nothing to your first booking using the Duffel API. In order to follow this guide, you'll need to: \* [Sign up](https://app.duffel.com/join) for a Duffel Account (it takes about 1 minute!) \* Create a test token from the "Access Tokens" page in your [Dashboard](https://app.duffel.com/) and paste it in the `Authorization` section of the Postman Collection (**Don't forget to hit save afterwards**) ## Overview Multi-step search allows integrators to easily implement a flow that involves a traveller selecting one slice of their flight at a time as they build their whole flight itinerary. This enhances the search experience as the whole flow feels faster and intuitive. There will be significantly fewer offers returned overall, and at each stage. As an integrator with Duffel, this would simplify your job to process and display these offers and will aid the traveller in making a selection from the offers presented to them. ## How does the flow work? The entire flow takes 4 steps: 1. _**Outbound search**_: You pass the origin and destination `slices` and `passengers` and get back a list of partial offers for the outbound slice of your journey by [creating a partial offer request](https://duffel.com/docs/api/partial-offer-requests/create-partial-offer-request). A _**partial offer**_ is an offer that can’t be booked directly but can be passed to the next endpoint: show partial offer request. A partial offer contains only one slice, even if the search is for multiple slices. At the end of the flow (at fare selection), you pass in the partial offers for each of the slices in your journey to obtain a full offer that you can book. 2. _**Inbound search**_: You pass in the offer from the previous outbound search into the endpoint for the inbound search. This will be through the [partial offer request show endpoint](https://duffel.com/docs/api/partial-offer-requests/get-partial-offer-request-by-id). You’ll get back partial offers for the next slice of your journey. 3. _**Fare selection**_: You pass in the chosen partial offers obtained from the outbound and inbound search, to obtain a list of full offers. This will be through the [fares endpoint](https://duffel.com/docs/api/partial-offer-requests/get-partial-offer-request-fares-by-id). 4. _**Create order**_: Finally you make a booking by passing in the full offer ID obtained at fare selection while [creating an order](https://duffel.com/docs/api/orders/create-order). **NOTE:** By running the requests in the sequence mentioned above, you'll get most fields automatically pre-filled for you.
A walkthrough on how to make changes to an order using the Duffel API. In order to follow this guide, we recommend you go first through our _Duffel API Quick Start Collection_ where we cover how to make an order through our API. In order to follow this guide, you'll need to: - [Sign up](https://app.duffel.com/join) for a Duffel Account (it takes about 1 minute!) - Create a test token from the "Access Tokens" page in your [Dashboard](https://app.duffel.com) and paste it in the `Authorization` section of the Postman Collection (**Don't forget to hit save afterwards**) - Copy the `id` of the order you created in the _Quick Start_ guide, and paste it as value for `ORDER_ID` in the `Variables` section of the Postman Collection (**Don't forget to hit save afterwards**) Our requests have a pre-defined sequence to replicate creating a booking in a real world scenario: 1. Getting a single order 2. Creating an order change request 3. Reviewing the available order change request offers 4. Creating a pending order change 5. Confirming an order change **NOTE:** By running the requests in the sequence mentioned above, you'll get most fields automatically pre-filled for you.
This collection is for the [Adding seats](https://duffel.com/docs/guides/adding-seats) guide In this guide, we'll show you how to select free or paid seats for passengers when booking flights through the Duffel API. We'll explain how to interpret the seat map data returned in the API so you can build your own interactive seat map, allowing customers to pick their own seats.
This collection is for the [Adding Extra Bags](https://duffel.com/docs/guides/adding-extra-bags) guide. # What do you need to start? This guide will go through the changes you need to make in the booking flow to be able to list and book services for any offer you want. It's important you know the basics of how to create a booking. If you are not familiar with how to create an order please heads over to our [Quick Start Guide](https://duffel.com/docs/guides/quick-start). This guide will start from an offer so make sure you grab an offer ID for a British Airways flight before we start. # Overview Baggages are a type of what we call available_services. Available services are specific to an offer but not surfaced through the API by default. The changes we'll make to work with available services are: 1. Retrieve an offer along with its available_services 2. Include services to order creation 3. See the services booked on an order
This collection is for the [Adding Loyalty Programme Accounts](https://duffel.com/docs/guides/adding-loyalty-programme-accounts) guide. In the travel industry where differentiation is key, and the customer is king, travel sellers need to think about what elements of their business can be a big driver for customer retention and how to make money selling flights. There's no shortage of places to purchase flights from direct airline websites, to meta-search engines like Skyscanner. Thinking about ways to motivate your customers to return to your website time and time again to purchase flights is more important than ever before. This is where Loyalty Programmes come in. Travellers with Loyalty Programme Accounts can accrue points for flights taken. They then can access benefits such as discounted fares or included services such as additional baggage and seat selection. By providing travellers with the ability to supply their Loyalty Programme Accounts during searching for flights, you can significantly improve your travellers' shopping experience.
This is a generated connector for [Dropbox API v2](https://www.dropbox.com/developers/documentation/http/overview) OpenAPI specification. Dropbox is a modern workspace designed to reduce busywork-so you can focus on the things that matter. Sign in and put your creative energy to work.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the DriveriQ. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This is a generated connector from [Dracoon API v4.28.3](https://www.dracoon.com/en/home) OpenAPI specification. REST Web Services for DRACOON. <a title='Developer Information' href='https://developer.dracoon.com'>Developer Information</a>  <a title='Get SDKs on GitHub' href='https://github.com/dracoon'>Get SDKs on GitHub</a><br><br><a title='Terms of service' href='https://www.dracoon.com/terms/general-terms-and-conditions/'>Terms of service</a>
This Open API specification serves as a standardized framework for describing and defining the capabilities of the DONBEST. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Dossier. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
Dans cette documentation nous allons voir les cas d'utilisation les plus communs pour vous permettre d'intégrer la signature électronique de Docage à votre propre produit. En complément de cette documentation, vous pouvez également aller visiter notre page [Swagger](https://api.docage.com/swagger) pour découvrir toutes les entités et les routes de notre API. #### **Prérequis** La plupart des routes de l'API nécessitent une authentification. Pour rajouter une authentification à votre requête vous devez posséder un compte Docage, que vous pouvez tester gratuitement [ici](https://api.docage.com/Identity/Account/Register). Votre compte sera créé en mode démo, les comptes dans ce mode n'ont pas de date d'expiration et vous sera utile pour tester Docage ainsi que votre intégration de Docage de manière gratuite. Une fois votre compte créé accédez à votre profile utilisateur et sélectionnez l'onglet "Clé d'API" et cliquez sur le bouton de génération de votre clé d'API. Cette clé servira à vous authentifier à notre API, ce qui permettra d'accéder à toutes les données qui vous appartiennent sur notre application, pour cette raison, veuillez garder cette clé de manière personnelle et ne la partagez pas. Nous utilisons [Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) pour nous authentifier à l'API lors d'appel à celle-ci. Vous devez donc renseigner le **username** qui correspond à votre email d'utilisateur Docage et le **password** qui correspond à votre clé API, séparé par le caractère `:`. **Le tout encodé en base 64**. Exemple de ce à quoi votre header Authorization doit ressembler avec un encodage en base 64 du couple username:apikey. Notez qu'il faut laisser un espave entre Basic et les identifiants encodé en base 64. Le code est présenté pour la compréhension, il est à adapter dans votre language de programmation : ``` javascript let username = "abc@dom.com"; let apikey = "123"; let headers = new Headers(); let encodedCredentials = btoa(username + ":" + apikey); headers.set('Authorization', 'Basic ' + encodedCredentials); ``` #### **Notes** - Si vous souhaitez tester notre API sans écrire de ligne de code dans un premier temps, vous pouvez utiliser [Postman](https://www.postman.com) (ou une application similaire) pour vous familiariser avec les informations que vous envoyez/recevez. - Les DateTime doivent être en format ISO 8601, par exemple "2012-04-23T18:25:43.511Z"
This is a generated connector for [DocuSign Click API](https://developers.docusign.com/docs/click-api/) OpenAPI specification. DocuSign Click lets you capture consent to standard agreement terms with a single click terms and conditions, terms of service, terms of use, privacy policies, and more. The Click API lets you include this customizable clickwrap solution in your DocuSign integrations.
Docker Hub is a service provided by Docker for finding and sharing container images with your team. It is the world's largest library and community for container images. In addition to the [Docker Hub UI](https://docs.docker.com/docker-hub/) and [Docker Hub CLI tool](https://github.com/docker/hub-tool#readme) (currently experimental), Docker provides an API that allows you to interact with Docker Hub. Browse through the Docker Hub API documentation to explore the supported endpoints.
An API for an organization administrator to manage organizations, accounts and users
This is a generated connector for [DocuSign Rooms API](https://developers.docusign.com/docs/rooms-api/) OpenAPI specification. DocuSign Rooms streamlines real estate and mortgage workflows by connecting all parties in a digital, secure, and central workspace. With the DocuSign Rooms API, it’s easy to integrate Rooms functionality into your own solutions.
This is a generated connector for [DocuSign Admin API](https://developers.docusign.com/docs/admin-api/) OpenAPI specification. An API for an organization administrator to manage organizations, accounts and users which enables you to automate user management with your existing systems while ensuring governance and compliance.
This is a generated connector for [Disqus API v1](https://disqus.com/api/docs) OpenAPI specification. Disqus is a service for web comments and discussions. Disqus makes commenting easier and more interactive, helping publishers power online discussions.
A one-stop shop for businesses to discover, integrate, and manage APIs, helping developers everywhere find the right app instantly and opening new revenue streams through API monetization.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the digitap validation springbootn. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Diligentsia. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.