Armasourcing

Armasourcing Auth API

The Auth API from Armasourcing — 7 operation(s) for auth.

GitHub OpenAPI

Operations 8

POST /api/auth/send-code Send Login Code #
POST /api/auth/verify-code Verify Login Code #
POST /api/auth/sso Auth Sso #
POST /api/auth/exchange Auth Exchange #
GET /api/auth/me Auth Me #
GET /api/auth/activate Auth Activate Page #
POST /api/auth/activate Auth Activate #
PUT /api/auth/profile Update Profile #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/armasourcing-com/openapi/armasourcing-com-auth-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/armasourcing-com/json-schema/armasourcing-com-activate-request-schema.json

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/armasourcing-com:armasourcing-com-auth-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.

GitHub Google LinkedIn

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

OpenAPI Specification

armasourcing-com-auth-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Armasourcing Community Auth API
  version: 0.1.0
tags:
- name: Auth
paths:
  /api/auth/send-code:
    post:
      summary: Send Login Code
      description: Send a 6-digit login code to the user's email.
      operationId: send_login_code_api_auth_send_code_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Auth
  /api/auth/verify-code:
    post:
      summary: Verify Login Code
      description: Verify a login code and return the user's auth token.
      operationId: verify_login_code_api_auth_verify_code_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Auth
  /api/auth/sso:
    post:
      summary: Auth Sso
      description: 'Trade a central Arma Google session for a Townhall token. The

        arma_session cookie is scoped to .armasourcing.com and, via /_arma_xset,

        to .scalewitharma.com, so both Townhall hostnames can use this.'
      operationId: auth_sso_api_auth_sso_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Auth
  /api/auth/exchange:
    post:
      summary: Auth Exchange
      description: 'Cross-app SSO bridge for Arma Tracker integration.


        Trusted callers (currently: tracker.armasourcing.com backend) authenticate

        with a shared `BRIDGE_SECRET` env var and pass a verified email. We return

        the user''s existing community auth token so the agent''s Chat tab can sign

        in without going through the email-code flow again.


        Body: {"email": "...", "secret": "...", "name": "Optional Display Name"}

        Returns: {"ok": true, "token": "...", "user_id": int, "display_name": "..."}


        The secret check makes this only callable server-to-server. End users never

        see the BRIDGE_SECRET — the tracker backend holds it on their behalf.'
      operationId: auth_exchange_api_auth_exchange_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Auth
  /api/auth/me:
    get:
      summary: Auth Me
      operationId: auth_me_api_auth_me_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Auth
  /api/auth/activate:
    get:
      summary: Auth Activate Page
      operationId: auth_activate_page_api_auth_activate_get
      parameters:
      - name: invite
        in: query
        required: false
        schema:
          type: string
          title: Invite
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Auth
    post:
      summary: Auth Activate
      operationId: auth_activate_api_auth_activate_post
      parameters:
      - name: invite
        in: query
        required: true
        schema:
          type: string
          title: Invite
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ActivateRequest'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Auth
  /api/auth/profile:
    put:
      summary: Update Profile
      operationId: update_profile_api_auth_profile_put
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Auth
components:
  schemas:
    HTTPValidationError:
      type: object
      description: Referenced by this document but never defined in it. API Evangelist added this empty placeholder so the document resolves; the shape is unknown and is NOT a claim about the API.
      x-ae-placeholder: true
    ActivateRequest:
      type: object
      description: Referenced by this document but never defined in it. API Evangelist added this empty placeholder so the document resolves; the shape is unknown and is NOT a claim about the API.
      x-ae-placeholder: true