API Documentation

API DOCUMENTATION

Last Update: July 2025



Premiere Access Enterprise-Level API Calls API Calls Overview Clients (Businesses) Account - Update Account - Info Dashboard - Info Custom Fields Customer Field - Create Customer Fields - List Customer Field - Update Customer Field - Delete Transaction Field - Create Transaction Fields - List Transaction Field - Update Transaction Field - Delete Reward Custom Field - Create Reward Custom Fields - List Reward Custom Field - Update Reward Custom Field - Delete Users (Business Employees) User - New User - Update Users - List User - Info User - Delete Users - Add to Campaign Users - Rem. from Campaign Loyalty Programs Campaign - New Campaign Campaign - New Reward Campaign - New Promo Campaign - New BuyX Item Campaign - New Depreciation Campaign - New Fee Campaign - Update Campaign Campaign - Update Reward Campaign - Update Promo Campaign - Update BuyX Item Campaign - Update Depreciation Campaign - Update Fee Campaign - List Campaigns Campaign - List Deactivated Campaign - List Rewards Campaign - List Promotions Campaign - List Depreciations Campaign - List Fees Campaign - List BuyX Items Campaign - Delete Campaign Campaign - Delete Reward Campaign - Delete Promo Campaign - Delete BuyX Item Campaign - Delete Depreciation Campaign - Delete Fee Campaign - Deactivate Campaign - Reactivate Customers Customer - New/Register Customer - Update Customer - Generate Card # Customer - Batch Customer - Search Customer - Find Customer - Information Customer - Exists Customer - Balance & History Customer - Delete Customer - Validate Card Replace Transactions Transaction - Record Transaction - Redeem Transaction - Batch Transaction - Delete Misc. Calls: Token - Get Token - Validate Audit Reports All Transactions All Redeemed Transactions Campaign Totals Customer Balances Marketing Reports All Customers New Customers Frequent Customers Missing Customers Birthdays Custom Date Range Customer Search Reference Currency Codes Country Codes Timezones Available Languages User Permission Levels Replacement Codes Premium APIs Email Templates Email Template - New Email Template - Update Email Template - Information Email Templates - List Email Template - Delete SMS Templates SMS List Service Providers SMS Add Credentials SMS Update Credentials SMS Template - New SMS Template - Update SMS Template - Information SMS Templates - List SMS Template - Delete Memberships Membership Program - New Membership Program - Update Membership Program - Info Membership Programs - List Membership Program - Delete Membership Level - New Membership Level - Update Membership Level - Info Membership Levels - List Membership Level - Delete Boost Promos Fixed Boost - New Fixed Boost - Update Temporary Boost - New Temporary Boost - Update Recurring Boost - New Recurring Boost - Update Boost - Info Boost - List Boost - Delete

Manage Transaction Fields - Add New Field

Create a new field used when recording customer transactions:

Headers

		Key		Value		Note
		api_access_key		user_api_key		Optional

The data to be submitted to the API is composed of the following fields:

field	Example	Note
API	1.6	Required
user_id	john1970	Required
user_api_key	1959caadac9b13dcb3	Required if not included in the headers
type	transaction_fields	Required
action	add	Required
account_id	greatwidgets	Required
custom_field_#_label	Item SKU	optional
custom_field_#_show	Y	optional
custom_field_#_type	Text	Required
custom_field_#_choices	New\|Used\|Other	optional
custom_field_#_unique	Y	optional
custom_field_#_activity_type	record, redeem, all	optional

Output Format:
output	JSON or XML	Optional. If not provided, defaults to XML
callback	someFunctionName	Optional: JSONP format
condensed	yes	Optional (No white space) Applies only to JSON(P) output

NOTE:

Headers: the user_api_key value can be included in either the header section or the body of the request. If the key is provided in both locations, the API will process and validate only the value provided in the headers.
Only users with proper permissions can access this call.
Multiple fields can be added at the same time.
The type is required, and once set, cannot be changed.
If a field is received by the API and is missing some of its parameters, it will be created with any such missing values set to their default: Show=No
Field types are:
- Text (up to 255 characters)
- Number (max precision of 16 digits, with 5 decimal. ie: max value: 99,999,999,999.99999)
- Monetary (max precision of 14 digits, with 2 decimal. ie: max value: 999,999,999,999.99)
- Date ("datetime" stamp. Ex: 2012-01-01 14:45:04 )
- Pick (Requires [field_name]_choices )
- List (Requires [field_name]_choices )
Currently, the only field type that can be set to be "unique" is the Text type. "Unique" fields don't allow a content entry to be a duplicate of an existing one. An example might be an ID code, etc.
Additional fields MUST have the following field_name structure:
- "custom_field_#" where the "#" is any integer above 1
  (one of the default fields is "custom_field_1")
  Example:
  - custom_field_2
  - custom_field_14
  - ...

NEW: Field "activity" types
- record To use the field for accruals (positive transactions)
- redeem To use the field for redemtions (negative transactions)
- all To use the field for both, acrruals and redemptions.

Example PHP Request:

If you are using PHP, the $data array would look like this:

$data['API'] = '1.5';
$data['user_id'] = 'john1970';
$data['user_api_key'] = '1959caadac9b13dcb3';
$data['account_id'] = 'greatwidgets';
$data['type'] = 'transaction_fields';
$data['action'] = 'add';
$data['custom_field_1_label'] = 'Item SKU'
$data['custom_field_1_show'] = 'Y';
$data['custom_field_1_type'] = 'Text';
$data['custom_field_2_label'] = 'Tags';
$data['custom_field_2_show'] = 'Y';
$data['custom_field_2_type'] = 'List';
$data['custom_field_2_choices'] = 'Tag A|Tag B|Tag C|Tag D|...';
$data['custom_field_3_label'] = 'Condition';
$data['custom_field_3_show'] = 'Y';
$data['custom_field_3_type'] = 'Pick';
$data['custom_field_3_choices'] = 'New|Used|Other';
$data['custom_field_4_label'] = 'Expiration Date';
$data['custom_field_4_show'] = 'Y';
$data['custom_field_4_type'] = 'Date';
$data['custom_field_5_label'] = 'Kilograms';
$data['custom_field_5_show'] = 'Y';
$data['custom_field_5_type'] = 'Number';
$data['custom_field_5_activity_type'] = 'redeem';

Success XML Response (lists ONLY the custom fields added):

<response status="success">
<account>
<account_id>test2009050502</account_id>
<fields>
<field>
<name>custom_field_1</name>
<label>Item SKU</label>
<show>Y</show>
<type>Text</type>
</field>
<field>
<name>custom_field_2</name>
<label>Tags</label>
<show>Y</show>
<type>List</type>
<choices>
<choice>Tag A</choice>
<choice>Tag B</choice>
<choice>Tag C</choice>
</choice>
</field>
<field>
<name>custom_field_3</name>
<label>Condition</label>
<show>Y</show>
<type>Pick</type>
<choices>
<choice>New</choice>
<choice>Used</choice>
<choice>Other</choice>
</choice>
</field>
<field>
<name>custom_field_4</name>
<label>Expiration Date</label>
<show>Y</show>
<type>Date</type>
</field>
<field>
<name>custom_field_5</name>
<label>Kilograms</label>
<show>Y</show>
<type>Number</type>
<activity_type>redeem</activity_type>
</field>
</fields>
</account>
</response>

NOTE:

The <show> response indicates whether or not this field ought to be shown or not. Usually fields with "N" will have nothing in them. However, it is allowed to add content to any defined field through the API regardless of their <show> status.

Error XML Response:

<response status="error">
<error>Error message</error>
</response>