0x7466

{
  "openapi": "3.1.1",
  "info": {
    "title": "YNAB API Endpoints",
    "description": "Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com",
    "version": "1.82.0"
  },
  "servers": [
    {
      "url": "https://api.ynab.com/v1"

0x7466

{
    "swagger": "2.0",
    "info": {
        "title": "hellocashAPI v1",
        "version": "",
        "description": "## Authentication\n\nTo authenticate your requests with the helloCash API, you have to use your bearer token.\n\n###### Bearer Token Authentication\n\n- register for a helloCash account at https://myhellocash.com/start-now-blue\n\n- navigate to > Cash Register > Settings > General > helloCash API\n\n- generate a token\n\n- include the token in the authorization header of your API requests\n\n- Note: API is only available in DEMO, PREMIUM and GASTRO mode.\n\n- Example Header:\n    + Request\n\n        + Headers\n\n                Authorization: Bearer YOURTOKEN\n\n## Character encoding\n\nOnly unescaped unicode should be sent to the API, otherwise it may be that our firewall is blocking the request (403).\nThe API itself returns the data in escaped form (e.g. ü => \\u00fc)"
    },
    "host": "api.hellocash.business",
    "basePath": "/api/v1",
    "schemes": [

0x7466

{
  "openapi": "3.1.0",
  "info": {
    "title": "Hub API Endpoints",
    "version": "0.0.1",
    "description": "We have open endpoints that you can use to retrieve information from the Hub as well as perform certain actions such as creating model, dataset or Space repos. We offer a wrapper Python client, [`huggingface_hub`](https://github.com/huggingface/huggingface_hub), and a JS client, [`huggingface.js`](https://github.com/huggingface/huggingface.js), that allow easy access to these endpoints. We also provide [webhooks](https://huggingface.co/docs/hub/webhooks) to receive real-time incremental info about repos. Enjoy!\n\nThe base URL for those endpoints below is `https://huggingface.co`. For example, to construct the `/api/models` call below, one can call the URL [https://huggingface.co/api/models](https://huggingface.co/api/models).\n\nIf you're an Agent, you might prefer the [markdown version OpenAPI spec](https://huggingface.co/.well-known/openapi.md).\n"
  },
  "servers": [
    {
      "url": "https:

0x7466

{
  "openapi": "3.1.0",
  "info": { "title": "Anthropic API" },
  "paths": {
    "/v1/messages": {
      "post": {
        "summary": "Create a Message",
        "description": "Send a structured list of input messages with text and/or image content, and the model will generate the next message in the conversation.\n\nThe Messages API can be used for either single queries or stateless multi-turn conversations.\n\nLearn more about the Messages API in our [user guide](https://docs.claude.com/en/docs/initial-setup)",
        "operationId": "messages_post",
        "parameters": [

0x7466

{
  "openapi": "3.1.0",
  "info": {
    "title": "Perplexity AI API",
    "description": "Perplexity AI API",
    "version": "0.1.0"
  },
  "paths": {
    "/chat/completions": {
      "post": {

0x7466

{
  "openapi": "3.1.0",
  "info": {
    "title": "Svix API",
    "description": "Welcome to the Svix API documentation!\n\nUseful links: [Homepage](https://www.svix.com) | [Support email](mailto:support+docs@svix.com) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/)\n\n# Introduction\n\nThis is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com).\n\n## Main concepts\n\nIn Svix you have four important entities you will be interacting with:\n\n- `messages`: these are the webhooks being sent. They can have contents and a few other properties.\n- `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform.\n- `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent t

0x7466

{
  "openapi": "3.0.0",
  "tags": [
    {
      "name": "Bundle Offers"
    },
    {
      "name": "Orders"
    }
  ],

0x7466

{
  "basePath": "/api/v2",
  "consumes": [
    "application/json"
  ],
  "definitions": {
    "Bndbox": {
      "example": {
        "xmax": 100,
        "xmin": 1,

0x7466

openapi: 3.1.1
info:
  title: Unsplash API (Unofficial OpenAPI)
  version: "1.0.0"
  description: >
    OpenAPI 3.1 specification for the Unsplash JSON API (v1). This spec covers the major
    public endpoints (photos, users, collections, search, current user) and models
    based on the provided Unsplash documentation.
    Note: auth options include Client-ID (header or query) and user Bearer tokens.
servers:

0x7466

{
  "openapi": "3.0.3",
  "info": {
    "title": "Postal Server API",
    "description": "API for interacting with the Postal mail delivery server.",
    "version": "1.0.0"
  },
  "servers": [
    {
      "url": "https://your-postal-server.com/api/v1",