Bloss Docs

Reject a submission

Developers
POST
/brands/{brandId}/onboarding/submissions/{submissionId}/reject

Reject an open submission (in progress or awaiting approval). The creator doesn't join, and is emailed, with the reason if you give one. A closed or decided submission answers 409 conflict.

Authorization

bearerAuth onboarding:write
headerAuthorizationBearer <token>

Personal access token. Scopes: account:read, creator:read, creator:earnings, managed:read, coach:read, brand:read, creators:read, videos:read, analytics:read, onboarding:read, onboarding:signatures, engagement:read, support:read, integrations:read, payouts:read, funds:read, billing:read, groups:write, videos:write, onboarding:write, sync:write, payouts:write.

Scope: onboarding:write

Path Parameters

brandId*string

A brand id from GET /me or GET /creator/brands.

Length1 <= length
submissionId*string

An id from GET /brands/{brandId}/onboarding/submissions.

Length1 <= length

Request Body

application/json
  1. body
reason?|

Up to 1,000 characters. The creator sees it in their email.

Response Body

Success.

application/json
  1. response
id*string
status*string
curl -X POST 'https://example.com/api/v1/brands/string/onboarding/submissions/string/reject' \  -H 'Content-Type: application/json' \  -d '{}'
{  "id": "string",  "status": "rejected"}

Was this page helpful?

Get an onboarding submission GET

One creator's onboarding: every task with its answers as text (labelled as the creator saw them; answers on open tasks are autosaved drafts), agreement signatures (who signed, when, the document hash), and any rejection or close reason. The signature image and signed PDF are at GET .../signatures, with the Signed agreements permission.

Email a creator a reminder POST

Email the creator of a submission in progress a reminder to finish, now. One per submission every 12 hours: another within that answers 409 conflict (`details.reason` rate_limited).