LayUp Technologies UserService API
The UserService API from LayUp Technologies — 2 operation(s) for userservice.
The UserService API from LayUp Technologies — 2 operation(s) for userservice.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/layup-technologies-userservice-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
title: Layup endpoints AbsaDebiCheckService User Service API
version: 1.4.16
description: 'Welcome to The Layup Swagger page. This page allows developers to interactively explore the API. For more detailed documentation see [The Layup documentation page](https://documentation.layup.co.za/).
# Introduction
## What is LayUp
LayUp is a lay-by payment solution. LayUp Schedules payments and ensures that your clients pay securely, effectively and on time. Depending on your parameters LayUp schedules a payment plan for your clients. Once a payment plan has been completed we notify you. There are 3 stories that are of importance to a merchant:
1. Order Creation
2. Deposit Received (and holding Stock for your client)
3. Order Completion.
LayUp allows you to take full control over the entire payment process if you wish to do so. We also provide a convenient front-end for users to use. The front-end should significantly reduce the time to integrate and get you started using LayUp as soon as possible.
Once an order is completed a notification will be sent to the merchant so that you can provide the client with their product.
## How to use LayUp
As a merchant who wants to place an order through LayUp, you want to send the relevant information to the LayUp API to create the order. The API will return an order ID. Unless your integration is using a custom user interface, you want to send the user to the LayUp customer payment widget. The URL for this widget is <u>https://shopper.layup.co.za/order/{orderId}</u> for production and <u>https://sandbox.layup.co.za/order/{orderId}</u> for sandbox.
'
servers:
- url: http://localhost:3000
- url: https://localhost:3000
- url: wss://localhost:3000
security:
- apiKey:
- read
- write
tags:
- name: UserService
paths:
/v1/users:
get:
operationId: UserService_GetMany
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/modelUserResponseMany'
'204':
description: Successfully processed the request, no content.
'403':
description: Returned when the user does not have permission to access the resource.
'404':
description: Returned when the resource does not exist.
parameters:
- name: limit
in: query
required: false
schema:
type: integer
format: int32
- name: orderId
in: query
required: false
schema:
type: string
tags:
- UserService
post:
summary: Description
operationId: UserService_Create
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/modelUserResponse'
'204':
description: Successfully processed the request, no content.
'403':
description: Returned when the user does not have permission to access the resource.
'404':
description: Returned when the resource does not exist.
parameters:
- name: _id
in: query
required: false
schema:
type: string
- name: avs
in: query
required: false
schema:
type: string
- name: isRealtimeVerification
in: query
required: false
schema:
type: boolean
tags:
- UserService
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/modelUserRequest'
required: true
/v1/users/{_id}:
get:
operationId: UserService_Get
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/modelUserResponse'
'204':
description: Successfully processed the request, no content.
'403':
description: Returned when the user does not have permission to access the resource.
'404':
description: Returned when the resource does not exist.
parameters:
- name: _id
in: path
required: true
schema:
type: string
tags:
- UserService
delete:
summary: Description
operationId: UserService_Del
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/modelUserResponse'
'204':
description: Successfully processed the request, no content.
'403':
description: Returned when the user does not have permission to access the resource.
'404':
description: Returned when the resource does not exist.
parameters:
- name: _id
in: path
required: true
schema:
type: string
tags:
- UserService
put:
operationId: UserService_Update
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/modelUserResponse'
'204':
description: Successfully processed the request, no content.
'403':
description: Returned when the user does not have permission to access the resource.
'404':
description: Returned when the resource does not exist.
parameters:
- name: _id
in: path
required: true
schema:
type: string
- name: avs
in: query
required: false
schema:
type: string
- name: isRealtimeVerification
in: query
required: false
schema:
type: boolean
tags:
- UserService
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/modelUserRequest'
required: true
components:
schemas:
modelMerchants:
type: object
properties:
_id:
type: string
name:
type: string
modelBillingAddress:
type: object
properties:
country:
type: string
province:
type: string
streetAddress:
type: string
city:
type: string
postalCode:
type: string
modelBankInfo:
type: object
properties:
bankName:
$ref: '#/components/schemas/modelBankValidation'
account:
$ref: '#/components/schemas/modelBankValidation'
accountType:
$ref: '#/components/schemas/modelBankValidation'
branchCode:
$ref: '#/components/schemas/modelBankValidation'
idNumber:
$ref: '#/components/schemas/modelBankValidation'
verified:
type: boolean
clientName:
$ref: '#/components/schemas/modelBankValidation'
cellNumber:
$ref: '#/components/schemas/modelBankValidation'
initials:
$ref: '#/components/schemas/modelBankValidation'
email:
$ref: '#/components/schemas/modelBankValidation'
validationResponseErrors:
type: array
items:
type: string
modelUserResponse:
type: object
properties:
_id:
type: string
username:
type: string
email:
type: string
format: email
idNumber:
type: string
address:
type: string
postalCode:
type: string
city:
type: string
province:
type: string
country:
type: string
role:
type: string
enum:
- CLIENT
- MERCHANT
- ADMIN
default: CLIENT
active:
type: boolean
merchantId:
type: string
cellNumber:
type: string
dateOfBirth:
type: string
name:
type: string
verified:
type: boolean
timestamp:
type: number
format: double
hasPassword:
type: boolean
verifiedEmail:
type: boolean
verifiedMobile:
type: boolean
merchantRole:
type: string
bankDetails:
$ref: '#/components/schemas/modelBankInfo'
merchantOnboarding:
$ref: '#/components/schemas/modelMerchantOnboarding'
bankValidationPendingReference:
type: string
oneTimePass:
type: string
passportState:
type: string
passportNumber:
type: string
profileImage:
type: string
merchantIds:
type: array
items:
type: string
merchants:
type: array
items:
type: object
$ref: '#/components/schemas/modelMerchants'
isMerchantOwner:
type: boolean
twoFactorAuthenticationRequired:
type: boolean
modelMerchantOnboarding:
type: object
properties:
name:
type: string
physicalAddress:
$ref: '#/components/schemas/modelBillingAddress'
modelBankValidation:
type: object
properties:
verified:
type: boolean
value:
type: string
modelUserRequest:
type: object
properties:
username:
type: string
email:
type: string
format: email
idNumber:
type: string
address:
type: string
postalCode:
type: string
city:
type: string
province:
type: string
country:
type: string
role:
type: string
enum:
- CLIENT
- MERCHANT
- ADMIN
default: CLIENT
password:
type: string
active:
type: boolean
name:
type: string
dateOfBirth:
type: string
cellNumber:
type: string
pattern: ^\+27\d{9}$
redirectTo:
type: string
apikey:
type: string
shouldWelcome:
type: boolean
merchantCreatePlan:
type: boolean
merchantId:
type: string
merchantRole:
type: string
bankDetails:
$ref: '#/components/schemas/modelBankInfo'
merchantOnboarding:
$ref: '#/components/schemas/modelMerchantOnboarding'
bankValidationPendingReference:
type: string
passportState:
type: string
passportNumber:
type: string
profileImage:
type: string
merchantIds:
type: array
items:
type: string
isMerchantOwner:
type: boolean
modelUserResponseMany:
type: object
properties:
users:
type: array
items:
type: object
$ref: '#/components/schemas/modelUserResponse'
securitySchemes:
apiKey:
type: apiKey
name: apikey
in: header