N3XT

N3XT Users API

The Users API from N3XT — 2 operation(s) for users.

GitHub OpenAPI

Operations 2

GET /users/me Get Current User #
GET /users/{id} Get User by ID #

Documentation

📖
APIReference
https://openapi.n3xt.io/docs/
📖
GettingStarted
https://helpcenter.n3xt.io/en/articles/12118191-api-getting-started

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/n3xt/refs/heads/main/openapi/n3xt-users-api-openapi.yml

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/n3xt-users-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

n3xt-users-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: N3XT API Documentation Users API
  version: v1.0.1-3514-g824039216
  description: 'A holistic banking API for businesses.


    Find the swagger definition file at /docs/swagger.json.'
  license:
    name: ISC
  contact:
    name: N3XT Support
    url: https://helpcenter.n3xt.io/en/
  termsOfService: https://n3xt.io/legal/website-terms-of-use
servers:
- url: https://openapi.n3xt.io
security:
- bearerAuth: []
tags:
- name: Users
paths:
  /users/me:
    get:
      operationId: Me
      responses:
        '200':
          description: The user details were retrieved successfully.
          content:
            application/json:
              schema:
                anyOf:
                - $ref: '#/components/schemas/User'
                - $ref: '#/components/schemas/ErrorResponse'
              examples:
                Example 1:
                  value:
                    id: user123
                    stytchId: stytch-abc123
                    businessId: business456
                    discoverableId: discoverable789
                    applicationSettingsId: settings123
                    fireblocksMetadataId: metadata456
                    notifiableId: notifiable123
                    apiUserMetadataId: metadata789
                    createdAt: '2023-03-24T12:34:56.789Z'
                    updatedAt: '2023-03-24T12:34:56.789Z'
        '400':
          description: Bad Request - Invalid request parameters.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized - Invalid or missing authentication token.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: An unexpected server error occurred while trying to retrieve the user details.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      description: Retrieve the current authenticated user's details.
      summary: Get Current User
      tags:
      - Users
      security:
      - bearerAuth: []
      parameters: []
  /users/{id}:
    get:
      operationId: User
      responses:
        '200':
          description: The user details were retrieved successfully.
          content:
            application/json:
              schema: {}
              examples:
                Example 1:
                  value:
                    id: user123
                    stytchId: stytch-abc123
                    businessId: business456
                    discoverableId: discoverable789
                    applicationSettingsId: settings123
                    fireblocksMetadataId: metadata456
                    notifiableId: notifiable123
                    apiUserMetadataId: metadata789
                    createdAt: '2023-03-24T12:34:56.789Z'
                    updatedAt: '2023-03-24T12:34:56.789Z'
        '400':
          description: Bad Request - Invalid request parameters.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized - Invalid or missing authentication token.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden - Insufficient permissions to perform this action.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Not Found - Requested resource was not found.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '422':
          description: Unprocessable Entity - Validation failed for the request body.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Internal Server Error - An unexpected error occurred while processing the request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      description: Retrieve details for a specific user by ID.
      summary: Get User by ID
      tags:
      - Users
      security:
      - bearerAuth: []
      parameters:
      - description: The UUID of the user to retrieve.
        in: path
        name: id
        required: true
        schema:
          type: string
        example: user123
components:
  schemas:
    ErrorResponse:
      properties:
        error:
          type: string
      required:
      - error
      type: object
      additionalProperties: false
    User:
      properties:
        id:
          type: string
        stytchId:
          type: string
        businessId:
          type: string
        discoverableId:
          type: string
        applicationSettingsId:
          type: string
        fireblocksMetadataId:
          type: string
        notifiableId:
          type: string
        apiUserMetadataId:
          type: string
        createdAt:
          type: string
          format: date-time
        updatedAt:
          type: string
          format: date-time
      required:
      - id
      - stytchId
      - businessId
      - discoverableId
      - applicationSettingsId
      - fireblocksMetadataId
      - notifiableId
      - apiUserMetadataId
      - createdAt
      - updatedAt
      type: object
      additionalProperties: false
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      name: Authorization
      in: header
      description: Bearer auth -> insert ONLY the token (the word Bearer will automatically be added)