subotiz-com

subotiz-com Customer API

顾客

GitHub OpenAPI

Operations 5

POST /api/v1/front/customer/create Create Customer #
POST /api/v1/front/customer/update Update Customer #
GET /api/v1/front/customer/{customer_id} Get Customer #
GET /api/v1/front/customer List Customer #
POST /api/v1/front/customer/delete Delete Customer #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/subotiz-com/openapi/subotiz-com-customer-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/subotiz-com/json-schema/subotiz-com-create-checkout-session-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/subotiz-com/json-schema/subotiz-com-create-price-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/subotiz-com/json-schema/subotiz-com-create-trade-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/subotiz-com/json-schema/subotiz-com-product-version-schema.json
📊
JSONSchema
https://artifacts.apis.io/subotiz-com/json-schema/subotiz-com-product-schema.json
📊
JSONSchema
https://artifacts.apis.io/subotiz-com/json-schema/subotiz-com-update-subscription-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/subotiz-com:subotiz-com-customer-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

subotiz-com-customer-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Subotiz Com Customer API
  version: 1.0.0
  description: 'Operations tagged Customer across 2 of this provider''s published API definitions: subotiz-com-openapi.yml, v1-en.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://{api}.subotiz.com
  variables:
    api:
      default: api
security:
- sec0: []
tags:
- name: Customer
  description: 顾客
paths:
  /api/v1/front/customer/create:
    post:
      tags:
      - Customer
      summary: Create Customer
      operationId: v1-customer-create-customer
      parameters:
      - $ref: '#/components/parameters/HeaderRequestID'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateCustomerRequest'
        required: true
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateCustomerResponse'
    servers:
    - url: https://{api}.subotiz.com
      variables:
        api:
          default: api
  /api/v1/front/customer/update:
    post:
      tags:
      - Customer
      summary: Update Customer
      operationId: v1-customer-update-customer
      parameters:
      - $ref: '#/components/parameters/HeaderRequestID'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdateCustomerRequest'
        required: true
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UpdateCustomerResponse'
    servers:
    - url: https://{api}.subotiz.com
      variables:
        api:
          default: api
  /api/v1/front/customer/{customer_id}:
    get:
      tags:
      - Customer
      summary: Get Customer
      operationId: v1-customer-Get-customer
      parameters:
      - name: customer_id
        in: path
        description: Customer unique identifier on Subotiz
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/HeaderRequestID'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetCustomerResponse'
    servers:
    - url: https://{api}.subotiz.com
      variables:
        api:
          default: api
  /api/v1/front/customer:
    get:
      tags:
      - Customer
      summary: List Customer
      operationId: v1-customer-list-customer
      parameters:
      - name: search_customer_ids
        in: query
        description: 'Filter by customer IDs. Array size limit: [0,10]'
        schema:
          type: array
          items:
            type: string
      - name: search_email
        in: query
        description: 'Filter by emails. Array size limit: [0,10]'
        schema:
          type: array
          items:
            type: string
      - name: search_payer_id
        in: query
        description: 'Filter by integration-side customer IDs.  Array size limit: [0,10]'
        schema:
          type: array
          items:
            type: string
      - name: customer_type
        in: query
        description: "Filter type\n - customer: member\n - guest: visitor"
        schema:
          type: string
      - name: starting_after
        in: query
        description: Cursor for pagination. starting_after is the object ID that defines your position in the list. For example, if you want to get the next page, you can use the last object's ID as the parameter value after getting the object list for the first time. Cannot be used together with ending_before
        schema:
          type: string
      - name: ending_before
        in: query
        description: Cursor for pagination. ending_before is the object ID that defines your position in the list. For example, if you want to get the previous page, you can use the first object's ID as the parameter value after getting the object list for the first time. Cannot be used together with starting_after
        schema:
          type: string
      - name: limit
        in: query
        description: 'Pagination parameter, number of items per page, default: 10, interface defaults to sorting by creation time in descending order. Limit: [1, 100]'
        schema:
          type: integer
          format: int32
      - name: created_at.gt
        in: query
        description: Minimum value to filter by (exclusive, UTC time in RFC3339 format, such as '2025-01-01T00:00:00Z')
        schema:
          type: string
      - name: created_at.gte
        in: query
        description: Minimum value to filter by (inclusive, UTC time in RFC3339 format, such as '2025-01-01T00:00:00Z')
        schema:
          type: string
      - name: created_at.lt
        in: query
        description: Maximum value to filter by (exclusive, UTC time in RFC3339 format, such as '2025-01-01T00:00:00Z')
        schema:
          type: string
      - name: created_at.lte
        in: query
        description: Maximum value to filter by (inclusive, UTC time in RFC3339 format, such as '2025-01-01T00:00:00Z')
        schema:
          type: string
      - $ref: '#/components/parameters/HeaderRequestID'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListCustomerResponse'
    servers:
    - url: https://{api}.subotiz.com
      variables:
        api:
          default: api
  /api/v1/front/customer/delete:
    post:
      tags:
      - Customer
      summary: Delete Customer
      operationId: v1-customer-delete-customer
      parameters:
      - $ref: '#/components/parameters/HeaderRequestID'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DeleteCustomerRequest'
        required: true
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeleteCustomerResponse'
    servers:
    - url: https://{api}.subotiz.com
      variables:
        api:
          default: api
components:
  schemas:
    DeleteCustomerResponse:
      type: object
      properties:
        code:
          type: string
          description: error code
        message:
          type: string
          description: error message
        data:
          $ref: '#/components/schemas/DeleteCustomerResponse_Data'
    UpdateCustomerResponse:
      type: object
      properties:
        code:
          type: string
          description: error code
        message:
          type: string
          description: error message
        data:
          $ref: '#/components/schemas/UpdateCustomerResponse_Data'
    CreateCustomerResponse_Data:
      type: object
      properties:
        customer_id:
          type: string
          description: Subotiz customer unique identifier
    DeleteCustomerRequest:
      type: object
      properties:
        customer_id:
          type: string
          description: Subotiz platform `customer_id`, either `customer_id` or `payer_id` must exist to identify the customer to update, `customer_id` has higher priority
    UpdateCustomerRequest:
      required:
      - email
      type: object
      properties:
        customer_id:
          type: string
          description: Subotiz platform `customer_id`, either `customer_id` or `payer_id` must exist to identify the customer to update, `customer_id` has higher priority
        email:
          type: string
          description: Customer email
        phone:
          type: string
          description: Customer phone number
        name:
          type: string
          description: Customer name
        address:
          allOf:
          - $ref: '#/components/schemas/CustomerAddress'
          description: Customer address
        metadata:
          type: object
          description: A set of key-value pairs that can be attached to an object, allowing you to store additional information in a structured format.
        payer_id:
          type: string
          description: Third-party customer ID
        email_subscription:
          type: integer
          description: "Whether to subscribe to marketing email notifications\n - 1: Do not subscribe\n - 2: Subscribe"
          format: int32
    UpdateCustomerResponse_Data:
      type: object
      properties:
        customer_id:
          type: string
          description: Subotiz customer unique identifier
    CreateCustomerResponse:
      type: object
      properties:
        code:
          type: string
          description: error code
        message:
          type: string
          description: error message
        data:
          $ref: '#/components/schemas/CreateCustomerResponse_Data'
    CustomerAddress:
      type: object
      properties:
        line1:
          type: string
          description: Line 1
        line2:
          type: string
          description: Line 2
        city:
          type: string
          description: City
        province:
          type: string
          description: Province/State Code
        postal_code:
          type: string
          description: Postal code
        country:
          type: string
          description: Country/Region Code
    CustomerInfo:
      type: object
      properties:
        id:
          type: string
        email:
          type: string
        address:
          type: string
        phone:
          type: string
        name:
          type: string
        description:
          type: string
        payer_id:
          type: string
      description: Customer information
    GetCustomerResponse_Data:
      type: object
      properties:
        customer:
          allOf:
          - $ref: '#/components/schemas/CustomerInfo'
          description: Customer information
    GetCustomerResponse:
      type: object
      properties:
        code:
          type: string
          description: error code
        message:
          type: string
          description: error message
        data:
          $ref: '#/components/schemas/GetCustomerResponse_Data'
    CreateCustomerRequest:
      type: object
      properties:
        email:
          type: string
          description: Customer email, mutually exclusive with `payer_id`
        phone:
          type: string
          description: Customer phone number
        name:
          type: string
          description: Customer name
        address:
          allOf:
          - $ref: '#/components/schemas/CustomerAddress'
          description: Customer address
        metadata:
          type: object
          description: A set of key-value pairs that can be attached to an object, allowing you to store additional information in a structured format.
        payer_id:
          type: string
          description: Third-party customer ID
        email_subscription:
          type: integer
          description: "Whether to subscribe to marketing email notifications\n - 1: Do not subscribe\n - 2: Subscribe"
          format: int32
    ListCustomerResponse_Data:
      type: object
      properties:
        has_more:
          type: boolean
          description: Whether there is more data
        list:
          type: array
          items:
            $ref: '#/components/schemas/CustomerInfo'
          description: Customer information record list
    ListCustomerResponse:
      type: object
      properties:
        code:
          type: string
          description: error code
        message:
          type: string
          description: error message
        data:
          $ref: '#/components/schemas/ListCustomerResponse_Data'
    DeleteCustomerResponse_Data:
      type: object
      properties: {}
  parameters:
    HeaderRequestID:
      name: Request-Id
      in: header
      description: The unique identifier of the request
      required: true
      schema:
        type: string
        default: 008e3967-a1b5-48bb-be14-d5bff5092e61
  securitySchemes:
    sec0:
      type: http
      description: 'Bearer API Key authentication. Format: Authorization: Bearer {your_api_key}'
      scheme: bearer
x-refined-from:
- subotiz-com-openapi.yml
- v1-en.yaml