BanQu Attachments API

The Attachments API from BanQu — 1 operation(s) for attachments.

Operations 1

GET /aws/upload-url

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/banqu-attachments-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

banqu-attachments-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: BanQu Attachments API
  version: 3.3.4
  description: The BanQu API is organized around [REST](http://en.wikipedia.org/wiki/Representational_State_Transfer). 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 verbs, which can be understood by off-the-shelf HTTP clients, and [JSON](http://www.json.org) for input and output.
servers:
- url: https://banqu.app:443/api/v1
security:
- Bearer: []
tags:
- name: Attachments
paths:
  /aws/upload-url:
    get:
      tags:
      - Attachments
      description: Pre-signed URL
      parameters:
      - name: contentType
        description: type of content for file that is going to be uploaded
        in: query
        schema:
          type: string
        required: true
      - name: fileName
        description: fileName
        in: query
        schema:
          type: string
        required: true
      responses:
        '200':
          description: reSignedUrl Target url to upload user file
          content:
            application/json:
              schema:
                type: string
        '401':
          $ref: '#/components/responses/401'
components:
  responses:
    '401':
      description: "HTTP 401 - Unauthorized \nUser is not authenticated or session has expired"
  securitySchemes:
    Bearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Your authentication token