Force a KYC Process outcome (testing and sandbox ONLY).

post https://example.com/kycs/{id}/force-outcome

A POST request sent to force a KYC outcome.

Responses

400

The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

401

Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.

403

The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.

429

The user has sent too many requests in a given amount of time ("rate limiting").

500

The server has encountered a situation it does not know how to handle.

502

This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.

503

The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded.

504

This error response is given when the server is acting as a gateway and cannot get a response in time.

Language

Credentials

Header


xxxxxxxxxx
1
const options = {
2
  method: 'POST',
3
  headers: {accept: 'application/json', 'content-type': 'application/json'}
4
};
5
6
fetch('https://example.com/kycs/id/force-outcome', options)
7
  .then(res => res.json())
8
  .then(res => console.log(res))
9
  .catch(err => console.error(err));

Choose an example:

application/json

200Updated verification for a KYC successfully