AnyTax Partner platform API

Server-side endpoints to provision and authenticate your end users against your AnyTax partner tenant. Use these to embed tax filing capabilities into your product; all other public APIs are called with the JWT returned here.

GitHub OpenAPI

Operations 3

POST /api/v1/partner/users/login Authenticate an end user (partner login) #
POST /api/v1/partner/users/register Provision a new end user (partner registration) #
POST /api/v1/partner/sso/token Mint a single-use SSO code (partner-initiated login) #

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/anytax:anytax-partner-platform-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

anytax-partner-platform-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Anytax Public API v1 Partner platform API
  description: '## Machine-readable resources


    | Resource | URL | Use for |

    |---|---|---|

    | OpenAPI JSON | `/v1-json` | Import into Cursor / Copilot / Claude Projects as a spec file |

    | OpenAPI YAML | `/v1-yaml` | Same spec in YAML for tools that prefer `.yaml` |

    | LLM guide | `/llms.txt` | AI agents that fetch `llms.txt` for narrative docs |


    ---


    # AnyTax Partner Integration Guide


    This guide is written for **integration teams** embedding AnyTax into an existing product. It explains how to authenticate your end users, call our public REST APIs from your backend, and follow security expectations for a production SaaS integration. You will find authentication flows, endpoint reference, sequence diagrams, and reference implementations in **TypeScript**, **Java**, and **Python**. ---


    ### Table of contents


    1. Overview

    2. Prerequisites

    3. Authentication Endpoints

    - Register a User

    - Login a User

    4. Protected API Endpoints

    - Get User Profile

    - List Scenarios

    - List Filings

    - Create a Filing

    - Prefill a Filing

    - Refresh Token

    5. Partner-Initiated SSO (Silent Login)

    - SSO quickstart (step by step)

    - Mint an SSO code

    - Exchange the code

    6. Integration Architecture

    - Option A — Server Proxy

    - Option B — Client Direct

    7. Sequence Diagrams

    8. Complete Code Examples

    - TypeScript / Node.js

    - Java

    - Python

    9. Error Handling

    10. Security Best Practices

    11. Import from ELSTER


    ---


    ## Overview


    AnyTax is a multi-tenant platform. As a **partner**, you integrate your application so your customers can complete German tax filings without leaving your product experience. At a high level you will:


    - **Provision** end-user accounts under your partner tenant using server-to-server calls (no OTP in this flow). - **Authenticate** returning users and obtain JWT access tokens for API access. - **Orchestrate** tax scenarios, filings, answers, and related flows through the same public APIs your users would use in our first-party experience. End users are scoped by **`(email + partner)`**: the same email may exist for different partners without collision. ### How the integration works


    1. During onboarding, AnyTax issues a **partner slug** and **client secret** for your environment. 2. Your **backend** calls register or login with those credentials plus the end user’s email. 3. AnyTax returns a **JWT access token** (RS256, short-lived; see Refresh Token). 4. Your services use that token in the `Authorization` header for all subsequent calls on behalf of that user. ---


    ## Prerequisites


    | Item | Description |

    | ----------------- | ------------------------------------------------------------------------------------ |

    | **Partner slug** | Stable identifier for your partner tenant (for example `my-partner`). |

    | **Client secret** | Rotatable credential issued with your slug. **Use only on trusted servers.** |

    | **Base URL** | Environment-specific API origin (for example `https://api.anytax.io` in production). |


    > **Security:** Treat the client secret like any other production API key. Register and login requests must originate from **your backend**—never from a browser bundle, mobile app, or public repository. ---


    ## Authentication Endpoints


    ### 1. Register a User


    Creates a new user under your partner and returns a JWT token.'
  version: 1.18.12
  contact: {}
servers: []
tags:
- name: Partner platform
  description: Server-side endpoints to provision and authenticate your end users against your AnyTax partner tenant. Use these to embed tax filing capabilities into your product; all other public APIs are called with the JWT returned here.
paths:
  /api/v1/partner/users/login:
    post:
      description: 'Use this endpoint from your backend to sign in a user who already exists in your AnyTax partner tenant. Supply your partner credentials together with the user’s email. On success you receive a short-lived JWT you can use for subsequent API calls on behalf of that user. Call this from server-side code only; never expose your client secret to browsers or mobile clients.


        **Request body**


        | Field | Type | Required | Constraints |

        | ----- | ---- | -------- | ----------- |

        | `slug` | string | Yes | 1–64 characters |

        | `clientSecret` | string | Yes | 1–512 characters |

        | `email` | string | Yes | Email of the end user you previously registered under this partner account. |


        **Responses**


        | Status | Meaning |

        | ------ | ------- |

        | `200` | Authentication succeeded. The response includes an access token and basic user profile fields. |

        | `401` | Partner credentials are invalid, or the user account is not active. |

        | `404` | No user is registered for this email address under your partner account. |'
      operationId: PartnerApiController_partnerUserLogin
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PartnerUserLoginDto'
      responses:
        '200':
          description: Authentication succeeded. The response includes an access token and basic user profile fields.
        '401':
          description: Partner credentials are invalid, or the user account is not active.
        '404':
          description: No user is registered for this email address under your partner account.
      summary: Authenticate an end user (partner login)
      tags:
      - Partner platform
      security:
      - bearer: []
      x-anytax-docs-enriched: true
  /api/v1/partner/users/register:
    post:
      description: 'Creates a new end-user account scoped to your partner tenant and returns a JWT so they can start using AnyTax APIs immediately—no separate email verification step for this flow. Users are unique per partner by email: the same address may exist under different partners. Invoke this from your backend only; keep your client secret off the client.


        **Request body**


        | Field | Type | Required | Constraints |

        | ----- | ---- | -------- | ----------- |

        | `slug` | string | Yes | 1–64 characters |

        | `clientSecret` | string | Yes | 1–512 characters |

        | `email` | string | Yes | End user’s email. Together with your partner account, this uniquely identifies the user. |

        | `name` | string | Yes | min length: 2 |

        | `surname` | string | Yes | min length: 2 |


        **Responses**


        | Status | Meaning |

        | ------ | ------- |

        | `201` | The user was created. The response includes an access token and basic user profile fields. |

        | `401` | Partner credentials are invalid or the partner account is inactive. |

        | `409` | A user with this email is already registered under your partner account. |

        | `422` | The request body did not pass validation (missing fields, invalid email, or length constraints). |'
      operationId: PartnerApiController_partnerUserRegister
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PartnerUserRegisterDto'
      responses:
        '201':
          description: The user was created. The response includes an access token and basic user profile fields.
        '401':
          description: Partner credentials are invalid or the partner account is inactive.
        '409':
          description: A user with this email is already registered under your partner account.
        '422':
          description: The request body did not pass validation (missing fields, invalid email, or length constraints).
      summary: Provision a new end user (partner registration)
      tags:
      - Partner platform
      security:
      - bearer: []
      x-anytax-docs-enriched: true
  /api/v1/partner/sso/token:
    post:
      description: 'Call this from your backend to obtain a single-use, short-lived code that logs one of your end users into their white-label instance without a second login. Supply your partner credentials and the id of a user you have already provisioned (via users/register or users/login). Redirect the user’s browser to the returned exchange URL immediately — the code expires in 60 seconds and can be used only once. Invoke this from server-side code only; never expose your client secret to browsers.


        **Request body**


        | Field | Type | Required | Constraints |

        | ----- | ---- | -------- | ----------- |

        | `slug` | string | Yes | 1–64 characters |

        | `clientSecret` | string | Yes | 1–512 characters |

        | `userId` | number | Yes | Id of the end user (as returned by users/register or users/login) to establish a session for. The user must belong to this partner. |

        | `returnPath` | string | No | max length: 512 |


        **Responses**


        | Status | Meaning |

        | ------ | ------- |

        | `201` | An SSO code was minted. Redirect the browser to GET /api/v1/partner/sso/exchange?code= to establish the session. |

        | `401` | Partner credentials are invalid, or the user account is not active. |

        | `404` | No user with this id is registered under your partner account. |'
      operationId: PartnerApiController_createSsoCode
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PartnerSsoTokenDto'
      responses:
        '201':
          description: An SSO code was minted. Redirect the browser to GET /api/v1/partner/sso/exchange?code=<ssoCode> to establish the session.
        '401':
          description: Partner credentials are invalid, or the user account is not active.
        '404':
          description: No user with this id is registered under your partner account.
      summary: Mint a single-use SSO code (partner-initiated login)
      tags:
      - Partner platform
      security:
      - bearer: []
      x-anytax-docs-enriched: true
components:
  schemas:
    PartnerSsoTokenDto:
      type: object
      properties:
        slug:
          type: string
          example: my-partner
          description: Partner identifier issued during onboarding. It scopes all requests to your integration.
          minLength: 1
          maxLength: 64
        clientSecret:
          type: string
          example: your-secret-here
          description: Confidential credential paired with your slug. Must be used only on your servers; never ship it to browsers or native apps.
          minLength: 1
          maxLength: 512
        userId:
          type: number
          example: 42
          description: Id of the end user (as returned by users/register or users/login) to establish a session for. The user must belong to this partner.
        returnPath:
          type: string
          example: /filing/550e8400-e29b-41d4-a716-446655440001
          description: Same-origin relative path the user lands on after login. Must start with a single "/". Defaults to "/dashboard". Anything that is not a safe relative path is ignored and replaced with the default.
          maxLength: 512
      required:
      - slug
      - clientSecret
      - userId
    PartnerUserLoginDto:
      type: object
      properties:
        slug:
          type: string
          example: my-partner
          description: Partner identifier issued during onboarding. It scopes all requests to your integration.
          minLength: 1
          maxLength: 64
        clientSecret:
          type: string
          example: your-secret-here
          description: Confidential credential paired with your slug. Must be used only on your servers; never ship it to browsers or native apps.
          minLength: 1
          maxLength: 512
        email:
          type: string
          example: user@example.com
          description: Email of the end user you previously registered under this partner account.
      required:
      - slug
      - clientSecret
      - email
    PartnerUserRegisterDto:
      type: object
      properties:
        slug:
          type: string
          example: my-partner
          description: Partner identifier issued during onboarding. It scopes all requests to your integration.
          minLength: 1
          maxLength: 64
        clientSecret:
          type: string
          example: your-secret-here
          description: Confidential credential paired with your slug. Must be used only on your servers; never ship it to browsers or native apps.
          minLength: 1
          maxLength: 512
        email:
          type: string
          example: user@example.com
          description: End user’s email. Together with your partner account, this uniquely identifies the user.
        name:
          type: string
          example: Max
          description: Given name as you store it for this end user.
          minLength: 2
        surname:
          type: string
          example: Mustermann
          description: Family name as you store it for this end user.
          minLength: 2
      required:
      - slug
      - clientSecret
      - email
      - name
      - surname
  securitySchemes:
    bearer:
      scheme: bearer
      bearerFormat: JWT
      type: http
    api-key:
      type: apiKey
      in: header
      name: X-API-Key
      description: API key for programmatic authentication
x-tagGroups:
- name: Partner platform
  tags:
  - Partner platform
  - Filing Eligibility Check
- name: User Management
  tags:
  - Auth API
  - User API
- name: Tax Services
  tags:
  - Filing API
  - Scenario API
  - Question API
  - Answer API
  - Navigation API
  - Wage Tax API
  - Tax Saving Tip API
  - ELSTER Import API