Stamp Remove API

The Stamp Remove API decrements the stamp count of an existing record by one.

It is not part of the standard accumulation flow, but is used for corrective scenarios such as fixing incorrect accruals, updating campaign rules, or handling user claims.
The stamp count will never drop below zero.

This API is available on the Personal plan or higher.

PUT

/api/stamp/v1/remove 

{
    "stampIdx": 394
}

Request Parameters

stampIdx integer required
Stamp IDX. 
{
    "code": 0,
    "message": "",
    "result": null
}

Response Parameters

code integer
Response code: 0 = Success, other values = Error
message string
Response message. If the response code is not 0, an error message is returned.
result null

When to Use Stamp Deduction

This API is not intended for frequent use. It is an administrative tool designed to resolve data issues.
It is typically used in the following scenarios:

  • Duplicate event processing results in stamps being added twice
  • System errors cause incorrect stamp increases
  • Campaign rule changes require adjustment of existing data
  • Incorrect accruals need to be rolled back

Leaving incorrect data uncorrected can increase reward costs and reduce campaign trust.
The Deduction API provides a direct way to fix these issues immediately.

Relationship with the Add Stamp API

These two APIs operate in opposite directions, but their roles are clearly defined.

  1. Add Stamp → Records user actions in the normal campaign flow
  2. Remove Stamp → Adjusts or rolls back data in exceptional scenarios

In every scenario where the Add Stamp API is used, cancellation and failure cases should also be designed.
Integrating the Remove Stamp API into those flows is a best practice for building a reliable stamp system.

Operational Considerations

The Stamp Deduction API is not used frequently. It is a critical administrative API for resolving data issues.

  • Uncorrected data reduces campaign trust
  • Over-accumulation increases reward costs
  • Negative impact on user experience

Use this API with audit logging and strict admin-level access control.

Things to consider

  • Stamp count never goes below 0. Check stamps via the Validation API before deducting
  • Repeated calls can cause unintended excessive deductions
  • Do not call this API directly from the client. Enforce validation and limits on the server
  • Record deduction history and protect it with proper admin access control