Skip to main content
A member is a Voucherify customer enrolled in a specific loyalty program. Membership is program-scoped. The same customer can be a member of several programs at once, but only once in a given program. A second enrollment while that membership exists is rejected. The customer must already exist in Voucherify. The program must be ACTIVE and inside its validity window before it can accept new members.

Enrollment

Members can be created one at a time, or in bulk through a batch endpoint. A batch accepts up to 10 MB and processes entries asynchronously in batches of 100. The call returns an async action before each entry is checked. A failed entry is skipped and reported, and the rest of the batch continues. A body that is not a JSON array fails the async action. Enrollment stops when the organization has reached its loyalty members plan limit. In a batch, entries past that limit are skipped. When a member is created, Voucherify issues one loyalty card for every card definition assigned to the program, so a member can start with several point wallets at once. Card code generation happens asynchronously, so a newly created card’s code may briefly be null.

Member lifecycle

A member is created as ACTIVE unless status is set to INACTIVE. Use the activate and deactivate endpoints to move a member between these two states. An inactive member can’t earn or spend points. Updating a member merges the provided metadata keys into the stored object. Omitted keys stay. Setting metadata to null clears the stored metadata. The payload is checked against the vl_member metadata schema. Update cannot change status. Deleting a member sets status to DELETED and soft-deletes the member and its cards. Later calls for that member do not return it. The same customer can join the program again, and the new membership gets a new member ID. List program members returns the members of one program. Deleted members are omitted, and the list does not include cards. Member activities list the lifecycle and card-assignment records for one member.

Loyalty cards and points

Each of a member’s loyalty cards tracks its own balance, lifetime point counters, and upcoming activation or expiration events. Card activities list the records for one card. Beyond the automatic earning and spending flows, several endpoints change points on a specific card. The program and the member must be ACTIVE. Each change is accepted as PENDING and processed afterward.
  • Adjust points. A positive value is an admin credit. A negative value is an admin debit. A value of 0 creates no transaction.
  • List, and optionally activate or cancel, pending points buckets. The bucket must still be pending, and its date must be after the current project day.
  • List, and optionally expire, expiring points buckets that are still active and not yet expired.
  • List the transactions on a card.
Aggregated daily points and earning-rule usage for a member are covered in the Reports overview.

Rewards and payments

Members spend points in two ways, both scoped to a member’s card. The default mode creates a PENDING transaction and returns 202. A dry run returns 200, simulates the result, and stores nothing.
  • Purchasing a reward spends points from the card tied to the reward’s cost. An APPROVED purchase can later be refunded, which returns the points to the card. Returned points receive a new expiration date. List reward purchases returns the stored purchases. A purchase accepted with 202 that later fails is stored as REJECTED.
  • Paying for an order with points spends points using the card definition’s pay-with-points exchange ratio. The card definition must have pay-with-points enabled, and the order must already exist. The amount is limited by the order total, the card balance, the card’s spending caps, and the optional payment limit. The same order can be paid again, and each call creates a new transaction. List order payments returns the stored payments.
Member history is split across lists. Benefit transactions are fulfillments. Tier transactions are joins, leaves, upgrades, downgrades, expiration changes, and evaluation refreshes.

Member vs. membership

Related endpoints return a member’s data from different angles:
  • Get member returns the member and its cards in one program. Cards omit tier_progress.
  • Get program membership returns the member, the program, and the cards. A card includes tier_progress when its card definition has a tier structure and the member has a tier on that card. Otherwise tier_progress is omitted. Use it when the integration needs progress toward the next tier.
  • Get customer memberships returns the customer and each membership’s member, program, and cards. Cards omit tier_progress. customer_id and customer_source_id return every program. member_id returns only that member’s program. An existing customer with no memberships returns an empty list. An unknown customer or member is not found.
Both membership lookups read the path ID through identification_type. The values are customer_id (the default), customer_source_id, and member_id.
Last modified on November 18, 2026