Weavr Authorised Signatories API
Verify the email of root users who act as authorised signatories of a Corporate or Consumer identity.
Verify the email of root users who act as authorised signatories of a Corporate or Consumer identity.
openapi: 3.1.0
info:
version: v3
title: Weavr Multi Product BackOffice Access Token Authorised Signatories API
x-logo:
url: https://storage.googleapis.com/weavr-cdn/weavr_logo-new.png
backgroundColor: '#FFFFFF'
altText: Weavr
description: 'Weavr Multi Back Office API allows you, as an innovator, to perform various back office operations concerning
identities and their instruments, without requiring the users to be logged in.
A token is to be obtained through the `access_token` method, and this will allow relevant operations
to be performed on behalf of this same identity.
'
contact:
name: Weavr
url: https://weavr.io
servers:
- description: Weavr Sandbox Environment
url: https://sandbox.weavr.io/multi/backoffice
tags:
- name: Authorised Signatories
description: Verify the email of root users who act as authorised signatories of a Corporate or Consumer identity.
paths:
/corporates/verification/email/send:
post:
tags:
- Authorised Signatories
description: 'The first step in verifying a root user''s email. The root user whose email address is to be verified is sent an email containing a randomly generated code.
This code must then be provided in the _corporateRootUserEmailVerify_ operation to verify the root user''s email address.
_Note that on the Sandbox Environment, the `verificationCode` is always set to \"123456\"._
'
summary: Send email verification code to Corporate root user
operationId: corporateRootUserEmailVerificationCodeSend
parameters:
- $ref: '#/components/parameters/idempotency-ref'
requestBody:
$ref: '#/components/requestBodies/EmailRequest'
responses:
'204':
$ref: '#/components/responses/NoContent'
'400':
$ref: '#/components/responses/BadRequestError'
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
'409':
$ref: '#/components/responses/EmailVerificationConflict'
'429':
$ref: '#/components/responses/TooManyRequests'
'500':
$ref: '#/components/responses/InternalServerError'
'503':
$ref: '#/components/responses/ServiceUnavailable'
default:
$ref: '#/components/responses/Error'
security:
- api-key: []
/corporates/verification/email/verify:
post:
tags:
- Authorised Signatories
description: 'The second step in verifying the root user''s email. The randomly generated code sent to the root user via
email, using the _corporateRootUserEmailVerificationCodeSend_ operation, is submitted here to verify the root user''s email.
This is needed as part of the verification process for basic due diligence.
_Note that on the Sandbox Environment, the `verificationCode` is always set to \"123456\"._
'
summary: Verify email of Corporate root user
operationId: corporateRootUserEmailVerify
requestBody:
$ref: '#/components/requestBodies/EmailVerifyRequest'
responses:
'204':
$ref: '#/components/responses/NoContent'
'400':
$ref: '#/components/responses/BadRequestError'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'409':
$ref: '#/components/responses/VerifyConflict'
'429':
$ref: '#/components/responses/TooManyRequests'
'500':
$ref: '#/components/responses/InternalServerError'
'503':
$ref: '#/components/responses/ServiceUnavailable'
default:
$ref: '#/components/responses/Error'
security:
- api-key: []
/consumers/verification/email/send:
post:
tags:
- Authorised Signatories
description: 'The first step in verifying a root user''s email. The root user whose email address is to be verified is sent an email containing a randomly generated code.
This code must then be provided in the _consumerRootUserEmailVerify_ operation to verify the root user''s email address.
Note that on the Sandbox Environment, the `verificationCode` is always set to \"123456\".
'
summary: Send email verification code to Consumer root user
operationId: consumerRootUserEmailVerificationCodeSend
requestBody:
$ref: '#/components/requestBodies/EmailRequest'
responses:
'204':
$ref: '#/components/responses/NoContent'
'400':
$ref: '#/components/responses/BadRequestError'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'409':
$ref: '#/components/responses/EmailVerificationConflict'
'429':
$ref: '#/components/responses/TooManyRequests'
'500':
$ref: '#/components/responses/InternalServerError'
'503':
$ref: '#/components/responses/ServiceUnavailable'
default:
$ref: '#/components/responses/Error'
security:
- api-key: []
/consumers/verification/email/verify:
post:
tags:
- Authorised Signatories
description: 'The second step in verifying the root user''s email. The randomly generated code sent to the root user via
email, using the _consumerRootUserEmailVerificationCodeSend_ operation, is submitted here to verify the root user''s email.
This is needed as part of the verification process for basic due diligence.
Note that on the Sandbox Environment, emails are not sent and the verification code is always set to \"123456\".
'
summary: Verify email of Consumer root user
operationId: consumerRootUserEmailVerify
requestBody:
$ref: '#/components/requestBodies/EmailVerifyRequest'
responses:
'204':
$ref: '#/components/responses/NoContent'
'400':
$ref: '#/components/responses/BadRequestError'
'401':
$ref: '#/components/responses/Unauthorized'
'403':
$ref: '#/components/responses/Forbidden'
'409':
$ref: '#/components/responses/VerifyConflict'
'429':
$ref: '#/components/responses/TooManyRequests'
'500':
$ref: '#/components/responses/InternalServerError'
'503':
$ref: '#/components/responses/ServiceUnavailable'
default:
$ref: '#/components/responses/Error'
security:
- api-key: []
components:
responses:
EmailVerificationConflict:
description: Conflict
content:
application/json:
schema:
type: object
properties:
errorCode:
type: string
enum:
- EMAIL_NOT_FOUND
- ALREADY_VERIFIED
- EMAIL_NOT_UNIQUE
InternalServerError:
description: Internal Server Error - There is a problem with the server. Please try again later.
headers:
request-ref:
$ref: '#/components/headers/request-ref'
BadRequestError:
description: Bad Request Error - Your request is invalid.
headers:
request-ref:
$ref: '#/components/headers/request-ref'
content:
application/json:
schema:
type: object
properties:
message:
maxLength: 255
type: string
description: When present helps to identify and fix the problem.
syntaxErrors:
$ref: '#/components/schemas/SyntaxError'
Error:
description: Error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
TooManyRequests:
description: Too many requests.
headers:
request-ref:
$ref: '#/components/headers/request-ref'
x-ratelimit-limit:
$ref: '#/components/headers/x-ratelimit-limit'
x-ratelimit-reset:
$ref: '#/components/headers/x-ratelimit-reset'
ServiceUnavailable:
description: Service Unavailable - The requested service is temporarily unavailable. Please try again later.
headers:
request-ref:
$ref: '#/components/headers/request-ref'
NotFound:
description: Not found - The requested resource couldn't be found.
headers:
request-ref:
$ref: '#/components/headers/request-ref'
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
Forbidden:
description: Forbidden - Access to the requested resource or action is forbidden.
headers:
request-ref:
$ref: '#/components/headers/request-ref'
content:
application/json:
schema:
type: object
properties:
errorCode:
type: string
enum:
- INSUFFICIENT_PERMISSIONS
Unauthorized:
description: Unauthorized - Your credentials or access token are invalid.
headers:
request-ref:
$ref: '#/components/headers/request-ref'
NoContent:
description: Success - No Content.
headers:
request-ref:
$ref: '#/components/headers/request-ref'
VerifyConflict:
description: Conflict
content:
application/json:
schema:
type: object
properties:
errorCode:
type: string
enum:
- VERIFICATION_CODE_INVALID
- EMAIL_NOT_UNIQUE
headers:
request-ref:
description: A request identifier. Providing this reference when contacting our support team will help us investigate your query.
required: true
schema:
type: string
x-ratelimit-reset:
description: The number of seconds until the window is reset.
required: true
schema:
minimum: 0
type: integer
format: int32
x-ratelimit-limit:
description: 'Example: `20, 10;w=60, 20;w=3600, 200;w=86400`
The first number (20) is the limit that has been exceeded.
The remaining numbers are the limits that are in force, with ''w'' meaning ''window in seconds''. In this example `20;w=3600` was exceeded. 20 calls in 3600secs (1hr)
'
required: true
schema:
type: string
schemas:
SyntaxError:
type: object
description: Is returned as part of an HTTP error response whenever a syntax error is detected. A list of the fields together with their syntax error will be provided.
properties:
invalidFields:
type: array
items:
type: object
properties:
params:
type: array
items:
type: string
fieldName:
type: string
error:
type: string
enum:
- REQUIRED
- HAS_TEXT
- REQUIRES
- SIZE
- RANGE
- IN
- NOT_IN
- REGEX
- EXACTLY
- AT_LEAST
- AT_MOST
- ALL_OR_NONE
VerificationCode:
type: string
description: A randomly generated one-time use code used to verify the user's email address or mobile number.
pattern: ^[0-9]{6}$
Email:
type: string
description: E-mail Address of the user
format: email
Error:
type: object
properties:
code:
type: string
message:
type: string
requestBodies:
EmailVerifyRequest:
required: true
content:
application/json:
schema:
required:
- email
- verificationCode
type: object
properties:
email:
$ref: '#/components/schemas/Email'
verificationCode:
$ref: '#/components/schemas/VerificationCode'
EmailRequest:
required: true
content:
application/json:
schema:
required:
- email
type: object
properties:
email:
$ref: '#/components/schemas/Email'
parameters:
idempotency-ref:
name: idempotency-ref
in: header
description: A unique call reference generated by the caller that, taking into consideration the payload as well as the operation itself, helps avoid duplicate operations. Idempotency reference uniqueness is maintained for at least 24 hours.
required: false
schema:
type: string
securitySchemes:
api_key:
type: apiKey
description: The API Key representing your Multi account.
name: api-key
in: header
auth_token:
type: http
description: The authentication token representing the user. This will be included in the login response object.
scheme: bearer
bearerFormat: JWT
x-tagGroups:
- name: Access
tags:
- Access Token
- User Impersonation
- Consent Request
- name: Identities
tags:
- Corporates
- Consumers
- name: User Management
tags:
- Authorised Users
- name: Instruments
tags:
- Managed Accounts
- Managed Cards
- name: Transactions
tags:
- Transfers
- name: Fees
tags:
- Fees
- name: Bulk Operations [Beta]
tags:
- Operations
- Manage