This is a generated connector for [GoDaddy Certificates API v1](https://developer.godaddy.com/doc/endpoint/certificates) OpenAPI specification. The GoDaddy Certificates API provides capability to access GoDaddy operations related to certificates.
This is a generated connector for [GoDaddy Agreements API v1](https://developer.godaddy.com/doc/endpoint/agreements) OpenAPI specification. The GoDaddy Agreements API provides capability to access GoDaddy operations related to agreements.
# Introduction This Gleap API documentation is provided based on the customer needs. We are currently migrating our full documentation to docusaurus and will share it with you as soon as it's available. If you are missing some functionality, don't hesitate to contact us on gleap.io or by email to hello@gleap.io
This is a generated connector for [GoDaddy Aftermarket API v1](https://developer.godaddy.com/doc/endpoint/aftermarket) OpenAPI specification. The GoDaddy Aftermarket API provides capability to access GoDaddy operations related to GoDaddy Auctions.
This is a generated connector for [GoDaddy Certificates API v1](https://developer.godaddy.com/doc/endpoint/certificates) OpenAPI specification. <strong>GoDaddy Abuse API Terms of Use:</strong><p>GoDaddy’s Abuse API is provided to simplify and standardize the abuse reporting experience. To help us streamline the review of abuse reports, you acknowledge and agree that your use of GoDaddy’s Abuse API is subject to the following quality metrics and terms of use.</p><p>GoDaddy may, in its sole and absolute discretion, change or modify these terms, and such changes or modifications shall be effective immediately upon notice to you. Your use of GoDaddy’s Abuse API after such changes or modifications shall constitute your acceptance of these terms as last revised. If you do not agree to be bound by these terms as last revised, do not use (or continue to use) our Abuse API.</p><p>As an Abuse API user, you must only submit abuse reports via the API portal and cease all email submissions, including but not limited, to phishing@godaddy.com, netabuse@godaddy.com, malware@godaddy.com, or spam@godaddy.com, etc. Any additional or duplicate submission outside of the API portal will be deprioritized for review. Submissions related to trademark, copyright or content issues may still be sent to trademarkclaims@godaddy.com, coyprightclaims@godaddy.com, and contentcomplaints@godaddy.com, respectively. Our [Front of Site](https://supportcenter.godaddy.com/AbuseReport) also describes other scenarios not covered by the API.</p><p>When you submit abuse reports via GoDaddy’s Abuse API, you must ensure that you accurately categorize the abuse type of each report to match our definitions in the API documentations provided to you. Any submission that fails to match our definitions or is miscategorized will be marked as a false positive. Examples include, but are not limited to, submissions of trademark complaints marked as phishing or malware, or submissions of copyright complaints marked as phishing or malware, etc.</p><p>If, at any time, the false positive rate of submissions exceeds 40% of your total submissions, as determined by GoDaddy, GoDaddy may in its sole discretion deprioritize any subsequent reports submitted by you and/or your organization.</p><p>You acknowledge and agree that submitting every URL for a single domain is not necessary and will not expedite the review process. If your submissions exceed five (5) URLs for a single domain, your report will be marked as a duplicate submission taking into account that the final outcome of such submissions would yield the same result as the original report. GoDaddy may in its sole discretion deprioritize reports submitted by you and/or your organization in the event more than 20% of your submissions are classified as duplicate submissions.</p><p>You further acknowledge and agree that our Customer Support lines are not intended to address abuse reporting matters or your use of GoDaddy’s Abuse API. Contacting Customer Support will not expedite the review process and may result in abuse reports being deprioritized, to be determined in our sole discretion.</p><p>Should you have any questions about GoDaddy’s Abuse API or any of the terms and conditions set forth above, please contact abuseapisupport@godaddy.com.</p>
This is a generated connector for [GoDaddy Subscriptions API v1](https://developer.godaddy.com/doc/endpoint/subscriptions) OpenAPI specification. The GoDaddy Subscriptions API provides capability to access GoDaddy operations related to subscriptions.
This is a postman collection covering the GoCardless API. See [https://developer.gocardless.com/api-reference/](https://developer.gocardless.com/api-reference/) for more details. ## Prerequisites [Postman](https://www.getpostman.com/downloads/) [GoCardless Account](https://manage-sandbox.gocardless.com/) ## Getting Started 1\. Create a GoCardless Sandbox account [here](https://manage-sandbox.gocardless.com/sign-up): the sandbox is our dedicated testing environment where you can build and test your integration without touching real money. 2\. Go to [Developers > Create > Access Token](https://manage-sandbox.gocardless.com/developers/access-tokens/create) to generate an API access token. Give it a memorable name, with read-write access. <img src="https://content.pstmn.io/0dfaf33e-fbff-4ba9-836a-3ba2da42734f/MjAyMy4wNy4yMSBhdCAxNC40Ny4wOEAyeC5wbmc=" width="270" height="163"> 3\. [Run in Postman](https://god.gw.postman.com/run-collection/22460459-bae9db02-4aec-428e-bbe4-c36d6d199fd0?action=collection/fork&collection-url=entityId=22460459-bae9db02-4aec-428e-bbe4-c36d6d199fd0&entityType=collection&workspaceId=ce43bf2d-b88c-4427-8757-fd33279fc1df) to [fork](https://www.postman.com/gocardlessapi/workspace/gocardless-api/collection/22460459-bae9db02-4aec-428e-bbe4-c36d6d199fd0/fork?origin=tab) the collection into Postman to synchronize with future updates. Do this whilst logged into your Postman account (sign up [here](https://identity.getpostman.com/signup)). <img src="https://content.pstmn.io/6fe085d7-eee3-4af4-9090-3aa7e15a9e09/MjAyMy4wMS4xNyBhdCAxNi4xOS40M0AyeC5wbmc=" width="422" height="458"> 4\. Set up a [Postman Environment](https://learning.postman.com/docs/sending-requests/managing-environments/) for the GoCardless API collection by navigating to Environments and selecting the + icon to create a new environment. 5\. Copy the access token from step 2. and add it to your [Postman Environment](https://learning.postman.com/docs/sending-requests/managing-environments/) as a secret variable named `ACCESS_TOKEN` 6\. Make sure the GC Sandbox environment is selected in the Environment drop-down in the top right corner of Postman when making requests from the imported collection. # Things to Note 1. There are additional URL parameters that can be passed, we recommended going through our API Developer Guide [here](https://developer.gocardless.com/api-reference/#core-endpoints) and amending the requests as necessary. 2. The Bank Account field requirements will vary depending on the scheme and payment method - please update the relevant requests accordingly. See more info [here](https://developer.gocardless.com/api-reference/#appendix-local-bank-details). 3. Our requests are chained together automatically via Environment variables, so there is no need to copy & paste IDs across requests. 4. Enjoy!
This Open API specification serves as a standardized framework for describing and defining the capabilities of the GlassHive. 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 [GitLab GitLab REST API v4](https://about.gitlab.com/) OpenAPI specification. Client endpoint for GitLab API currently supports operations related to access requests and access tokens in GitLab.
The platform for modern developers. GitLab unifies issues, code review, CI and CD into a single experience. Contact Support: Name: No Contact Email: email@example.com
This is a simple question for managing my GitHub issue searches.
This is generated documentation using [the GitHubs OpenAPI](https://github.blog/2020-07-27-introducing-githubs-openapi-description/), providing portable documentation that can be used as part of the API integration process.
This is a simple collection to help onboard with the GitHub Web API without being overhwelmed by all of the available API methods.
This is a Postman collection that helps me pull, change, and publish the READCME for a project.
Search for code on GitHub using the GitHub API.
This is a simple collection for searching for GitHub users.
List all of the public events using the GitHub API.
Lists the events for a GitHub organization using the GitHub API.
Working with the GitHub issues API.
Lists the members of a GitHub organization using the GitHub API.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the GitHub GraphQL. 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.
Access the Github API.
Working with the GitHub issues API.
This is a reference collection for the GitHub GraphQL API. More work is needed to help visualize the surface area of the GitHub GraphQL API schema.
This is a collection dedicated to helping people begin making their first call to the GitHub GraphQL API, before they learn how GraphQL works.
This is a generated connector for [Giphy API v1](https://developers.giphy.com/docs/api/) OpenAPI Specification. Giphy API provides functions to get GIFs and stickers.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the giftTech. 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 Geodipa. 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.
Build applications using the world's most powerful imagery 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 GetFit. 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 [Google Vault API v1](https://developers.google.com/vault/reference/rest) OpenAPI specification. The Google Vault API provides the capability to do Retention and eDiscovery for Google Workspace. To work with Vault resources, the account must have the [required Vault privileges](https://support.google.com/vault/answer/2799699) and access to the matter. To access a matter, the account must have created the matter, have the matter shared with them, or have the **View All Matters** privilege. For example, to download an export, an account needs the **Manage Exports** privilege and the matter shared with them.
This is a generated connector for [fungenerators BarCode API v1](http://fungenerators.com/api/barcode/) OpenAPI specification. The fungenerators.barcode API provides capability to generate Barcode images for a given barcode number. You can decode Barcode images and get the barcodes in a numberic form as well. Many industry standard barcode types are supported. The best and complete Barcode API on the cloud.
Welcome to Fuze’s API docs. ## 👋 Onboarding To get started, your organization should have been onboarded with Fuze. As a part of the process, the following three fields would have been generated and passed on to key stakeholders in your organization: - Organization Id (orgId): See [details](https://docs.fuze.finance/docs/intro#organization-user-id-orguserid). - API key (apiKey) - API secret (apiSecret) ## 🚀 Getting started with this workspace Indepth documentation about the APIs can be found [here](https://docs.fuze.finance/). ## 🚀 Authentication Information about how to make authorized requests to the Fuze API can be found [here](https://docs.fuze.finance/authentication). ## 🐞 API Status We track the status of the core services of Fuze [here](https://status.fuze.finance/). ## 🛟 Help and support If you have any questions or suggestions, please don't hesitate to reach out to your manager or any member of the Quality Engineering team.
This is a generated connector for [Freshdesk API v2.0](https://developers.freshdesk.com/api/#intro) OpenAPI specification. Freshdesk is a cloud-based customer service software that enables businesses of all sizes to deliver stellar customer support.
This is a generated connector for [FreshBooks API v1](https://www.freshbooks.com/api/start) OpenAPI specification. FreshBooks lets you create professional looking invoices in seconds, automatically record expenses with ease and track your time quickly and efficiently so you can focus on what matters most - serving the needs of your clients. The FreshBooks API is an interface for accessing your FreshBooks data using JSON.
This is a generated connector for [FraudLabsPro SMS Verification API v1.0](https://www.fraudlabspro.com/developer/api/send-verification) OpenAPI specification. 'Send an SMS with verification code and a custom message for authentication purpose. It helps merchants to minimize chargebacks and fraud for various kinds of payment method, such as credit card, paypal, cod and so on. Please visit https://www.fraudlabspro.com to learn more.'
This is a generated connector for [Flat API v2.13.0](https://flat.io/developers/docs/api/) OpenAPI specification. The Flat API allows you to easily extend the abilities of the [Flat Platform](https://flat.io), with a wide range of use cases including the following: * Creating and importing new music scores using MusicXML, MIDI, Guitar Pro (GP3, GP4, GP5, GPX, GP), PowerTab, TuxGuitar and MuseScore files * Browsing, updating, copying, exporting the user's scores (for example in MP3, WAV or MIDI) * Managing educational resources with Flat for Education: creating & updating the organization accounts, the classes, rosters and assignments. The Flat API is built on HTTP. Our API is RESTful It has predictable resource URLs. It returns HTTP response codes to indicate errors. It also accepts and returns JSON in the HTTP body. The [schema](/swagger.yaml) of this API follows the [OpenAPI Initiative (OAI) specification](https://www.openapis.org/), you can use and work with [compatible Swagger tools](http://swagger.io/open-source-integrations/). This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). You can use your favorite HTTP/REST library for your programming language to use Flat's API. This specification and reference is [available on Github](https://github.com/FlatIO/api-reference). Getting Started and learn more: * [API Overview and introduction](https://flat.io/developers/docs/api/) * [Authentication (Personal Access Tokens or OAuth2)](https://flat.io/developers/docs/api/authentication.html) * [SDKs](https://flat.io/developers/docs/api/sdks.html) * [Rate Limits](https://flat.io/developers/docs/api/rate-limits.html) * [Changelog](https://flat.io/developers/docs/api/changelog.html)
This is a generated connector for [FraudLabsPro Fraud Detection API v1.1](https://www.fraudlabspro.com/developer/api/screen-order) OpenAPI specification. Online payment fraud detection service. It helps merchants to minimize chargebacks and therefore maximize the revenue. It can be used to detect fraud for various kinds of payment method, such as credit card, paypal, cod and so on. Please visit https://www.fraudlabspro.com to learn more.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Flutterwave. 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.
Foodics API (Application Programming Interface) is built around REST. The API allows external applications to integrate with Foodics on different levels to achieve various integrations goals Foodics API returns `JSON-encoded` responses and uses standard HTTP response codes and authentication Each endpoint has full description with sample responses
This is a generated connector for [Formstack REST API v2.0](https://formstack.readme.io/docs/api-overview) OpenAPI specification. The [Formstack REST API](https://formstack.readme.io/docs/api-overview) provides a way that helps organizations streamline digital work through no-code online forms, documents, and signatures.
This is a generated connector for [Amadeus Flight Offers Search API](https://developers.amadeus.com/self-service/category/air/api-doc/flight-offers-search) OpenAPI specification. This [Amadeus Flight Offers Search API](https://developers.amadeus.com/) provides the capability to search for the cheapest flight for a given itinerary.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the flixbeton. 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 [Amadeus Flight Offers Price API](https://developers.amadeus.com/self-service/category/air/api-doc/flight-offers-price) OpenAPI specification. This [Amadeus Flight Offers Price API](https://developers.amadeus.com/) provides the capability to confirm the availability and final price (including taxes and fees) of flights returned by the Flight Offers Search API.
This is a generated connector for [Amadeus Flight Create Orders API](https://developers.amadeus.com/self-service/category/air/api-doc/flight-create-orders) OpenAPI specification. This [Amadeus Flight Create Orders API](https://developers.amadeus.com/) provides the capability to perform the final booking for a chosen flight. Use this after completing a flight search with Flight Offers Search and confirming real-time price and availability with Flight Offers Price.
Explore, upload and organize photos on Flickr Contact Support: Name: No Contact Email: email@example.com
This API provides access to the Compliance server to manage audit processing, schedule services, enter resolutions, view findings, and other processing needed. It also allows an application to access the SUITS data and to get updated suits information directly from the compliance server.
# Finix Core API Collection This Postman Collection includes the following collections: - [Getting Started Guide](https://developers.finixpayments.com/#getting-started) - [Onboard a merchant](https://developers.finixpayments.com/#step-1-create-an-identity-for-a-merchant) - [Create a card sale](https://developers.finixpayments.com/#step-4-create-an-identity-for-a-buyer) - [Subscription Billing](https://finix.admin.payments-docs.com/#subscription-billing) Use the __Finix Core API Environment__ to set the appropriate credentials. If you are facing any issues with the credentials, you can reach out to your Sales Engineer or use the credentials available [here](https://developers.finixpayments.com/#authentication). For Subscription Billing, you will require __ROLE_PLATFORM__ credentials. You can use the ones that are available in the Environment Variables file or use the credentials provided in the Curl command for Subscription Billing [here](https://finix.admin.payments-docs.com/#subscription-billing).
This Open API specification serves as a standardized framework for describing and defining the capabilities of the FIS. 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 Fleet-KE. 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.