XMLDationManagmentAPI
## Endpoints for Connectivity Mainly meant to be used to confirm connectivity. ## Endpoints for Registration Mainly meant to be used from BMO Onboarding Application ### Registration use cases: - Onboarding a new client (POST) - Updating an existing client (GET/PUT) - Offboarding a client (DELETE) ## Endpoints for Management Mainly meant to be used from BMO Dev Portal ### Management use cases: - Get sandbox details - BMO Client accounts (same as Account Information Reporting API accounts) - Sandbox accounts/objects (test cases) - Update BMO Client accounts balance - Get Sandbox documentation - Provides listing of payment rail and consent/entitlement based data for test cases - Filters to retrieve only specific payment rail data for ease of use
Endpoints Summary
getHello
postHello
putHello
deleteHello
getRegistrations
postRegistration
Creates a new sandbox instance with the requested client details.
getRegistration
Request
putRegistration
Updates an existing sandbox instance with the requested client details.
Request
deleteRegistration
Deletes a sandbox instance with completely and wipes the stored data.
Request
postSandboxBaselines
Client is identified via the Sandbox ID provided in the headers. The Sandbox ID is defined in the registration endpoints.
Request
getSandboxBaselines
Client is identified via the Sandbox ID provided in the headers. The Sandbox ID is defined in the registration endpoints.
Request
rollbackSandboxBaseline
Client is identified via the Sandbox ID provided in the headers. The Sandbox ID is defined in the registration endpoints.
Request
getAccounts
Client is identified via the Sandbox ID provided in the headers. The Sandbox ID is defined in the registration endpoints.
Request
putAccountBalance
Client is identified via the Sandbox ID provided in the headers. The Sandbox ID is defined in the registration endpoints.