Verify the firm's customs account (API-driven; one attempt per call)
Firms
Verify a firm
API-driven verification of a client firm on ScripX: submit the firm’s customs-account credentials under its mandate, then complete with the one-time authorization code sent to the firm.
POST
Verify the firm's customs account (API-driven; one attempt per call)
Verifies the firm’s customs account. Your platform collects the firm’s credentials in its own UI under the firm’s explicit mandate (see API terms) and submits them here; ScripX runs the verification and returns only the outcome.
One verification attempt per call, deliberately: verification attempts are strictly rate-limited, so batch retries buy nothing. The password is handed straight through for the attempt; it is never stored and never echoed, on our side or in any response.
Two outcomes:
connected, done in one step.verification_pendingwithnext: "authorize", a one-time authorization code went to the firm’s registered email and mobile; finish with authorize.
Request example
Response example
In sandbox the flow simulates end to end: verify always returns
verification_pending, and any 6-digit code completes it. Same shapes as production, no real account touched.Errors
422 unprocessable, missingregistration_idorpassword.404 not_found, the firm is not registered on your desk (register first).- Wrong credentials surface as an error message; the state does not advance. Never loop retries, ask the firm to re-enter.
Next steps
- Authorize with the code the firm received.
- Get the firm any time for the current state.
Authorizations
Your API key, e.g. scripx_live_…. Bound to one firm; tenant isolation is enforced.
Path Parameters
Body
application/json