Submit a customer's sender profile for review
Submits the SWIFT sender profile written with PUT /api/customers/. From not_submitted, or rejected before any approval, a complete profile goes to pending and enters Bitnob’s compliance review; any other state returns the customer unchanged (after an approval, a PUT that changes identity resubmits by itself). Bitnob sends customers.sender.approved or customers.sender.rejected when the version is decided. In sandbox the submission is decided at once, and sandbox.reject_with rejects it with that reason code. The response is the customer with its sender block. An expiry date already in the past is refused.
Authorizations
Response
OK
Successful responses are wrapped in this envelope, and so are errors a handler answers itself (request body and field validation, some not-found and conflict cases, ORG_NOT_ACTIVE): success is false and error carries a code and message. Errors raised by authentication and by the services behind a handler are a Problem instead.