QBE Insurance CTP Switch API

The CTP Switch API from QBE Insurance — 2 operation(s) for ctp switch.

Operations 2

POST /ctp-documents/appenddata Append data #
GET /ctp-documents/saveddata Get saved data #

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/qbe-ctp-switch-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 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

qbe-ctp-switch-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Service CTP Switch API
  description: ''
  version: v1
  x-provenance:
    harvestedBy: API Evangelist
    harvestDate: '2026-07-25'
    portal: https://connect.api-au.qbe.com/apis
    method: Assembled from QBE's own anonymously-published Azure API Management developer-portal data endpoints. info/servers/securitySchemes come verbatim from GET https://connect.api-au.qbe.com/developer/apis/ctp-switch-service?export=true&format=openapi+json (HTTP 200), which QBE returns with an empty paths object to anonymous callers. Paths, parameters, request/response bodies and examples come verbatim from GET https://connect.api-au.qbe.com/developer/apis/ctp-switch-service/operations and .../operations/{operationId} (HTTP 200). components.schemas come verbatim from GET https://connect.api-au.qbe.com/developer/apis/ctp-switch-service/schemas/{schemaId} (HTTP 200). No endpoint, schema or scope was invented.
servers:
- url: https://gateway.api-au.qbe.com/ctp-service
security:
- {}
- apiKeyHeader: []
- apiKeyQuery: []
tags:
- name: CTP Switch
paths:
  /ctp-documents/appenddata:
    post:
      operationId: append-data
      summary: Append data
      tags:
      - CTP Switch
      description: Append data
      parameters:
      - name: code
        in: query
        required: true
        schema:
          type: string
      responses:
        '200':
          description: ''
  /ctp-documents/saveddata:
    get:
      operationId: get-saved-data
      summary: Get saved data
      tags:
      - CTP Switch
      description: Get saved data
      parameters:
      - name: code
        in: query
        required: true
        schema:
          type: string
      - name: Referer
        in: header
        required: true
        schema:
          type: string
      responses:
        '200':
          description: ''
components:
  securitySchemes:
    apiKeyHeader:
      type: apiKey
      name: Ocp-Apim-Subscription-Key
      in: header
    apiKeyQuery:
      type: apiKey
      name: subscription-key
      in: query