POST/reseller/accountOnboard a customer domain (third-party resellers)
This is the endpoint for third-party resellers. Authenticate with the OAuth 2.0 client-credentials grant and send the resulting access token - see the security scheme.
{
"domain": "<domain>",
"user": "<user>",
"org": "<org>",
"prefix": "secumailer",
"contact": "secumailer"
}prefix and contact are hard-coded server-side and are not taken from the request body.
Request body application/json
Voorbeeld
{
"domain": "example.nl",
"user": "info@example.nl",
"org": "Example B.V."
}Responses
- 201
The success status is
201, not200. The method declares201,400and500and no200at all. A client that treats only200as success will misread every successful call. - 400
The request body was absent, could not be parsed, carried no attributes at all, or a mandatory attribute (
domain,user,org) was absent or empty.errorMessagenames the offending attribute, or the body itself.Produced by the method's
.*\[Bad Request\].*integration response. Verified live on acceptance. - 401
- 403
Authenticated but not permitted: a WAF block, a resource-policy denial, or - on
/reseller/account- a token whosescopeclaim does not include the scope the method requires. - 415
- 429
* production -
api.secumail.nl, stageprd: 100 requests/second sustained, 500 burst * acceptance -test-api.secumail.nl, stageacc: 10 requests/second sustained, 50 burstNeither stage configures a quota, so
QUOTA_EXCEEDEDdoes not arise. A429here is always a rate or burst breach. - 500
- 504