The current industry and its policy consequence
Authorization
OAuth2PasswordBearer In: header
Cookie Parameters
Response Body
application/json
application/json
curl -X GET "https://example.com/api/b/v1/kyb/industry"{ "industry": "agriculture", "restricted": true, "policy_action": "allow", "verification": { "status": "created", "tier": "tier_0", "person_count": 0, "persons_verified": 0, "persons_clean": 0, "open_cases": 0 }}Send a rejected application back for review POST
Put a rejected application back in the compliance review queue — IN-367. Refiling a document resets that document only; the application stays rejected, and out of the reviewer's queue, until this is called. It moves the verification to `in_review` and the business to `pending`, the state a reviewer's request for more information leaves, and records when it came back. The tier stays where rejection left it until a reviewer approves. Answers with the verification record, as `GET /kyb/verification` does.
Select the business's industry and apply the industry policy POST
Record the industry and re-evaluate the application. A restricted industry flags the application `requires_underwriting` and opens an underwriting case record in the same transaction; an allowed industry leaves the application where it stands. The evaluation is idempotent: re-selecting the same industry does not stack cases.