Support Home > Analytics, Reports & API > Premium Publisher API Postback Triggers

Premium Publisher API Postback Triggers

As a Premium Publisher API user, you can manage your Kochava apps, campaigns, segments, trackers, and postback triggers without ever logging into the Kochava UI. This powerful API offers the same functionality as the UI and is designed to be used in lieu of the Kochava UI.

NOTE: The Premium Publisher API documentation refers to the trigger for a postback as opposed to the postback, itself. The postback is the payload of data sent, the trigger is the event which causes a postback to be fired.

NOTE: The Premium Publisher API and the Kochava Dashboard function independently.


Creating Triggers

  1. Use the Get Template call to retrieve valid postback templates for your app.
  2.  

    Returns a list of Postback Templates that are available for the given appId.

 

Get:

 

 

Header:

FieldTypeDescription
Authentication-KeyStringYour Publisher api key.

 

Success 200:

FieldTypeDescription
dataObject[]A list of Template objects.
successBooleanIndicates if the request was successful.
errorsString[]A list of errors that occurred while processing the request.
messagesString[]A list of information messages about the request.
warningsString[]A list of warnings that occurred while processing the request.
nextTokenStringA token that is used to retrieve the next page of results, null if not applicable to the request.
previousTokenStringA token that is used to retrieve the previous page of results, null if not applicable to the request.
metaObjectCurrently not used.

 

Sample Response:

 

HTTP Status Codes:

FieldDescription
401The Authentication Key sent with the request is invalid.
403The Authentication Key is not authorized to access the requested resource.

 

  1. Create the Trigger.
  2.  

    Creates a new Postback Trigger for the app in the request body.

 

Post:

 

NOTE: The Trigger is the event which causes a postback to be fired.

 

 

Header:

FieldTypeDescription
Authentication-KeyStringYour Publisher api key.

 

Success 200:

FieldTypeDescription
dataObject[]A list with a single Trigger object.
successBooleanIndicates if the request was successful.
errorsString[]A list of errors that occurred while processing the request.
messagesString[]A list of information messages about the request.
warningsString[]A list of warnings that occurred while processing the request.
nextTokenStringA token that is used to retrieve the next page of results, null if not applicable to the request.
previousTokenStringA token that is used to retrieve the previous page of results, null if not applicable to the request.
metaObjectCurrently not used.

 

Sample Response:

 

HTTP Status Codes:

FieldDescription
401The Authentication Key sent with the request is invalid.
400The request data has malformed syntax. The request should not be repeated without modifications. A common cause of this is invalid JSON in the request body.
500An unexpected server side condition occurred that prevented the request from being fulfilled. This issue is on us so you should try your request again shortly to see if the problem has been resolved.

 

  1. Use the Get Trigger method to verify the Trigger.
  2.  

    Returns a single Postback Trigger with the given id.

 

Get:

 

 

Header:

FieldTypeDescription
Authentication-KeyStringYour Publisher api key.

 

Success 200:

FieldTypeDescription
dataObject[]A list with a Trigger object.
successBooleanIndicates if the request was successful.
errorsString[]A list of errors that occurred while processing the request.
messagesString[]A list of information messages about the request.
warningsString[]A list of warnings that occurred while processing the request.
nextTokenStringA token that is used to retrieve the next page of results, null if not applicable to the request.
previousTokenStringA token that is used to retrieve the previous page of results, null if not applicable to the request.
metaObjectCurrently not used.

 

Sample Response:

 

HTTP Status Codes:

FieldDescription
401The Authentication Key sent with the request is invalid.
403The Authentication Key is not authorized to access the requested resource.
404The requested resource/entity was not found.

Updating Triggers

  1. Use the Get Pending Setup call to retrieve any incomplete Triggers.
  2.  

    Returns a list of Postback Templates that need to be setup for the given appId.

 

Get:

 

 

Header:

FieldTypeDescription
Authentication-KeyStringYour Publisher api key.

 

Success 200:

FieldTypeDescription
dataObject[]A list with Postback Template objects.
successBooleanIndicates if the request was successful.
errorsString[]A list of errors that occurred while processing the request.
messagesString[]A list of information messages about the request.
warningsString[]A list of warnings that occurred while processing the request.
nextTokenStringA token that is used to retrieve the next page of results, null if not applicable to the request.
previousTokenStringA token that is used to retrieve the previous page of results, null if not applicable to the request.
metaObjectCurrently not used.

 

Sample Response:

 

HTTP Status Codes:

FieldDescription
401The Authentication Key sent with the request is invalid.
403The Authentication Key is not authorized to access the requested resource.

 

  1. Using the list of incomplete Triggers, update as needed.
  2. NOTE: The Trigger is the event which causes a postback to be fired.

  3. Use the Get Trigger method to verify the Trigger.

Deleting Triggers

Deletes a Postback Trigger with the given ID.

 

Delete:

 

 

Header:

FieldTypeDescription
Authentication-KeyStringYour Publisher API key.

 

Sample Response:

 

HTTP Status Codes:

FieldDescription
401The Authentication Key sent with the request is invalid.
404The requested resource/entity was not found.
400The request data has malformed syntax. The request should not be repeated without modifications. A common cause of this is invalid JSON in the request body.
500An unexpected server side condition occurred that prevented the request from being fulfilled. This issue is on us so you should try your request again shortly to see if the problem has been resolved.

 
 

Last Modified: Jul 19, 2023 at 10:17 am