The rows worth reading twice
Creating a sub-client works on both, and belongs on the API. The dashboard creates one from Customers, which is what you want for a handful onboarded by hand. Onboarding a customer is normally part of your product’s own flow, though, and that is the API. Webhook endpoints are the dashboard alone. Registering a URL, filtering its events, pausing it, rotating its secret and replaying a delivery all happen in the Developers section of the dashboard, and there is no/v1 endpoint for any of them.
API keys are the dashboard alone too. They live under Developers → API Keys, and there is no /v1 endpoint for them. API keys covers roles and rotation.
Roles are a dashboard matter. An administrator on your own team sets who on your team may do what, in the dashboard, and there is no /v1 endpoint for it either. Roles and permissions covers what each role grants.
A dashboard payout takes a one-time code, sent to the person making it, and an API payout does not. Same operation, same result, different check.
Choosing between them
The question is who is doing it and how often, not what is possible:- Every time, automatically, inside your product → the API.
- Occasionally, by a person, with judgement involved → the dashboard.
Whichever surface an operation happens on, the same webhooks fire, so you never have to reconcile the two. Answering an RFI item is the exception on both surfaces. It fires no event, and you learn the outcome from
rfi.resolved, rfi.item_returned or rfi.not_resolved.