Rotageek Auth API

The Auth API from Rotageek — 1 operation(s) for auth.

Operations 1

POST /api/v1/auth Authentication with the Rotageek API is via oAuth bearer tokens, so for all… #

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/rotageek:rotageek-auth-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

rotageek-auth-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Rotageek Auth API
  version: '2026-10-13'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-13: 4 operation(s) read from 2 public documentation page(s) (each operation names its page in x-source). This is not the provider''s published contract; Rotageek has published no machine-readable contract that the pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 1
    documentation: 3
    pages-with-code: 1
    pages-read: 2
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-13'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://support.rotageek.com/en/articles/11514191-api-authenticating.md
  - https://support.rotageek.com/en/articles/11513937-reading-schedules-via-the-api.md
servers:
- url: https://<rotageekapiurl>
tags:
- name: Auth
paths:
  /api/v1/auth:
    post:
      operationId: post_api_v1_auth
      tags:
      - Auth
      summary: Authentication with the Rotageek API is via oAuth bearer tokens, so for all…
      x-source: https://support.rotageek.com/en/articles/11514191-api-authenticating.md
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostApiV1AuthRequest'
      responses:
        '201':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PostApiV1AuthResponse'
      x-evidence:
        kind: documentation
components:
  schemas:
    PostApiV1AuthResponse:
      type: object
      properties:
        access_token:
          type: string
          description: The access token you need to use in http Authorization header for subsequent calls
        token_type:
          type: string
          description: Bearer token type
        expires_in:
          type: integer
          description: Number of seconds until the access token expires
        refresh_token:
          type: string
          description: The refresh token you can use to get new Access Tokens when using the refresh_token grant_type in subsequent Auth requests
    PostApiV1AuthRequest:
      type: object
      properties:
        grant_type:
          type: string
          description: Either "password" or "refresh_token" depending on the authentication flow.
        username:
          type: string
          description: The username of your API user (required when grant_type is "password").
        password:
          type: string
          description: The password of your API user (required when grant_type is "password").
        refresh_token:
          type: string
          description: The refresh token from a previous Auth request (required when grant_type is "refresh_token").
      required:
      - grant_type