APIClaw Amazon Transcribe Pass-through API

The Amazon Transcribe Pass-through API from APIClaw — 2 operation(s) for amazon transcribe pass-through.

Business capability
Speech & Voice AE-110.30

Operations 2

POST /transcribe/{operation} Transcribe Proxy Route #
POST /transcribe Transcribe Sdk Proxy Route #

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/apiclaw:apiclaw-amazon-transcribe-pass-through-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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

OpenAPI Specification

apiclaw-amazon-transcribe-pass-through-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: LiteLLM Amazon Transcribe Pass-through API
  description: 'Proxy Server to call 100+ LLMs in the OpenAI format. **Customize Swagger Docs**


    👉 ```LiteLLM Admin Panel on /ui```. Create, Edit Keys with SSO. Having issues? Try ```Fallback Login```


    💸 ```LiteLLM Model Cost Map```.


    🔎 ```LiteLLM Model Hub```. See available models on the proxy. **Docs**'
  version: 1.105.1
tags:
- name: Amazon Transcribe Pass-through
paths:
  /transcribe/{operation}:
    post:
      tags:
      - Amazon Transcribe Pass-through
      summary: Transcribe Proxy Route
      description: 'Pass-through for the Amazon Transcribe API, e.g. `POST /transcribe/StartTranscriptionJob`.


        The request body is forwarded to the AWS JSON 1.1 API and signed with SigV4 using the

        proxy''s AWS credentials. Standard jobs are tagged with the calling key''s owner so that

        only that owner (or a proxy admin) can read or delete them, and keys other than proxy

        admins may only read media from and write transcripts to the S3 buckets listed in

        `general_settings.transcribe_media_buckets`; account-wide operations

        such as ListTranscriptionJobs are limited to proxy admins. Streaming transcription

        (`transcribestreaming`) uses a separate HTTP/2 event-stream protocol and is not served

        by this route.


        Docs'
      operationId: transcribe_proxy_route_transcribe__operation__post
      security:
      - APIKeyHeader: []
      parameters:
      - name: operation
        in: path
        required: true
        schema:
          type: string
          title: Operation
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
  /transcribe:
    post:
      tags:
      - Amazon Transcribe Pass-through
      summary: Transcribe Sdk Proxy Route
      description: 'AWS-SDK-shaped pass-through for Amazon Transcribe: point the SDK''s `endpoint_url`

        at `/transcribe` and the operation is read from the `X-Amz-Target` header, per the

        AWS JSON 1.1 protocol.


        Docs'
      operationId: transcribe_sdk_proxy_route_transcribe_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      security:
      - APIKeyHeader: []
components:
  schemas:
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      description: Bearer token
      in: header
      name: x-litellm-api-key
    HTTPBearer:
      type: http
      scheme: bearer