Actionstep Gender Types API

The Gender Types API from Actionstep — 2 operation(s) for gender types.

Operations 5

GET /gendertypes
POST /gendertypes
GET /gendertypes/{genderTypeName}
PUT /gendertypes/{genderTypeName}
DELETE /gendertypes/{genderTypeName}

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/actionstep-gender-types-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

actionstep-gender-types-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Action (Matter) Bill Settings Action Bill Settings Gender Types API
  description: For retrieving Action Bill Settings. For historical reasons Matters are referred to as *actions* in this version of the API. For information of how to construct requests utilising fieldsets, sorting, paging, filters, and '*includes*', please refer to the API Developer Portal. E&OE.
  version: '1.0'
servers:
- url: https://api.actionstep.com
  description: Base URL reconciled from apis.yml
tags:
- name: Gender Types
paths:
  /gendertypes:
    get:
      description: Returns a list of custom gender types.
      tags:
      - Gender Types
      responses:
        '200':
          description: OK.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PagedGenderTypes'
    post:
      description: Create a new custom gender type.
      tags:
      - Gender Types
      requestBody:
        $ref: '#/components/requestBodies/CreateGenderType'
      responses:
        '200':
          description: OK.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GenderType'
  /gendertypes/{genderTypeName}:
    get:
      description: Returns a single custom gender type.
      tags:
      - Gender Types
      parameters:
      - name: genderTypeName
        in: path
        description: Name of the custom gender type.
        required: true
        schema:
          type: string
        example: Transgender
      responses:
        '200':
          description: OK.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GenderType'
    put:
      description: Update a single custom gender type.
      tags:
      - Gender Types
      parameters:
      - name: genderTypeName
        in: path
        description: Name of the custom gender type.
        required: true
        schema:
          type: string
        example: Transgender
      requestBody:
        $ref: '#/components/requestBodies/UpdateGenderType'
      responses:
        '200':
          description: OK.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GenderType'
    delete:
      description: Delete a custom gender type. Please note - you cannot delete a custom gender type if it is already assigned to an existing participant record.
      tags:
      - Gender Types
      parameters:
      - name: genderTypeName
        in: path
        description: Name of the custom gender type.
        required: true
        schema:
          type: string
        example: Transgender
      responses:
        '204':
          description: Success, No content.
components:
  schemas:
    CreateGenderType:
      type: object
      required:
      - genderTypeName
      - pronounType
      properties:
        genderTypeName:
          description: Name of the custom gender type.
          example: Transgender
          type: string
        pronounType:
          description: One of 'Male', 'Female', 'Neutral', or 'Company'.
          enum:
          - Male
          - Female
          - Neutral
          - Company
          example: Neutral
          type: string
    UpdateGenderType:
      type: object
      required:
      - pronounType
      properties:
        pronounType:
          description: One of 'Male', 'Female', 'Neutral', or 'Company'.
          enum:
          - Male
          - Female
          - Neutral
          - Company
          example: Neutral
          type: string
    GenderType:
      type: object
      properties:
        genderTypeName:
          description: Name of the custom gender type.
          example: Transgender
          type: string
        pronounType:
          description: One of 'Male', 'Female', 'Neutral', or 'Company'.
          enum:
          - Male
          - Female
          - Neutral
          - Company
          example: Neutral
          type: string
    PagedGenderTypes:
      type: object
      properties:
        gendertypes:
          type: array
          items:
            $ref: '#/components/schemas/GenderType'
        meta:
          $ref: '#/components/schemas/PageMetaData'
    GenderTypesPageData:
      type: object
      properties:
        recordCount:
          description: The total number of custom gender types returned by the underlying query.
          type: integer
          example: 4
        pageCount:
          description: The total number of pages generated by the underlying query.
          type: integer
          example: 8
        page:
          description: The page number for this page of custom gender types.
          type: integer
          example: 2
        pageSize:
          description: Page size.
          type: integer
          example: 50
        prevPage:
          description: A URL to the previous page of custom gender types.
          type: string
          example: https://ap-southeast-2.actionstep.com/api/rest/gendertypes?page=1
        nextPage:
          description: A URL to the next page of custom gender types.
          type: string
          example: https://ap-southeast-2.actionstep.com/api/rest/gendertypes?page=3
    PageMetaData:
      type: object
      properties:
        paging:
          $ref: '#/components/schemas/PagingData'
    PagingData:
      type: object
      properties:
        gendertypes:
          $ref: '#/components/schemas/GenderTypesPageData'
  requestBodies:
    CreateGenderType:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/CreateGenderType'
    UpdateGenderType:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/UpdateGenderType'
externalDocs:
  description: API Developer Portal - Constructing API Requests
  url: https://docs.actionstep.com/api-requests/