QBE Australia CTP Switch Service

A small QBE Australia service published in the same API Hub as the "ANZO CTP Service" product, supporting the compulsory third party (CTP) motor insurance switching flow. Two documented operations append data to and retrieve saved data for a CTP document, keyed by a code parameter. Like every product in the hub it requires an approved subscription key and is partner-gated rather than self-serve.

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-service-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

qbe-ctp-switch-service-openapi.yml Raw ↑
openapi: 3.0.1
info:
  title: CTP Switch Service
  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
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
  schemas:
    Ctp-documentsAppenddataPostRequest:
      type: string
      x-apim-inline: true
    Ctp-documentsSaveddataGetRequest:
      type: string
      x-apim-inline: true
    Ctp-documentsSaveddataGetRequest-1:
      type: string
      x-apim-inline: true
security:
- {}
- apiKeyHeader: []
- apiKeyQuery: []