Account Actions
Review and provide feedback on accounts that are in the in_review status. You can either finalize the account to approve it, or request corrections with specific feedback.
Finalize Account
Approve an account that is currently in review. This marks the account as validated and advances the bundle lifecycle.
POST /bundles/:id/account/finalize
Requirements
- Bundle must have an account in
in_reviewstatus.
Example
curl -X POST https://app.tokportal.com/api/ext/bundles/bnd_abc123/account/finalize \
-H "X-API-Key: tok_live_xxx"
Response
{
"data": {
"id": "bnd_abc123",
"account": {
"status": "finalized",
"finalized_at": "2026-02-10T16:00:00Z"
}
}
}
Error Responses
| Status | Code | Description |
|---|---|---|
409 | invalid_status | Account is not in in_review status. |
404 | bundle_not_found | Bundle does not exist. |
Request Corrections
Request changes to an account that is in review. Provide a general comment and specify which fields need corrections.
POST /bundles/:id/account/corrections
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
comment | string | Yes | General feedback describing what needs to change. |
fields | object | Yes | Object specifying which fields need corrections and the feedback for each. |
Fields Object
Each key corresponds to an account field. The value is a string describing the required correction.
| Field | Type | Description |
|---|---|---|
username | string | Feedback on the username. |
visible_name | string | Feedback on the display name. |
biography | string | Feedback on the biography. |
profile_picture | string | Feedback on the profile picture. |
You only need to include the fields that require corrections.
Requirements
- Bundle must have an account in
in_reviewstatus. - At least one field must be specified in the
fieldsobject.
Example
curl -X POST https://app.tokportal.com/api/ext/bundles/bnd_abc123/account/corrections \
-H "X-API-Key: tok_live_xxx" \
-H "Content-Type: application/json" \
-d '{
"comment": "Username needs to be shorter and biography should mention the city.",
"fields": {
"username": "Please shorten to under 15 characters and remove special characters.",
"biography": "Add a mention of New York City to align with the niche."
}
}'
Response
{
"data": {
"id": "bnd_abc123",
"account": {
"status": "corrections_requested",
"corrections": {
"comment": "Username needs to be shorter and biography should mention the city.",
"fields": {
"username": "Please shorten to under 15 characters and remove special characters.",
"biography": "Add a mention of New York City to align with the niche."
},
"requested_at": "2026-02-10T16:30:00Z"
}
}
}
}
Error Responses
| Status | Code | Description |
|---|---|---|
400 | missing_comment | The comment field is required. |
400 | missing_fields | At least one field must be specified. |
400 | invalid_field | An unrecognized field was included. |
409 | invalid_status | Account is not in in_review status. |
404 | bundle_not_found | Bundle does not exist. |
Feedback History
Each correction request is recorded in the bundle's feedback history. You can retrieve the full history by fetching the bundle details.
curl -X GET https://app.tokportal.com/api/ext/bundles/bnd_abc123 \
-H "X-API-Key: tok_live_xxx"
The response includes a feedback_history array on the account object:
{
"data": {
"id": "bnd_abc123",
"account": {
"status": "in_review",
"feedback_history": [
{
"type": "corrections_requested",
"comment": "Username needs to be shorter and biography should mention the city.",
"fields": {
"username": "Please shorten to under 15 characters and remove special characters.",
"biography": "Add a mention of New York City to align with the niche."
},
"requested_at": "2026-02-10T16:30:00Z",
"requested_by": "api"
},
{
"type": "corrections_applied",
"applied_at": "2026-02-10T17:00:00Z",
"changes": {
"username": {
"from": "streetstyle.newyorkcity",
"to": "streetstyle.nyc"
},
"biography": {
"from": "Daily street fashion inspiration.",
"to": "Daily street fashion from New York City."
}
}
}
]
}
}
}
Feedback Types
| Type | Description |
|---|---|
corrections_requested | A correction was requested via the API. |
corrections_applied | The operator applied the requested corrections. |
finalized | The account was approved and finalized. |
Each entry in the history is immutable and includes a timestamp for auditability.