PUT - Replace

The Custom Audience API 1.1 only accepts install IDs for the moment. For audiences with custom user IDs or advertising IDs, the version 1.0 should be used.

The Custom Audience API enables you to create, update, delete and list custom audiences. A custom audience can contain a list of custom user IDs, advertising IDs (GAID or IDFA) or install IDs.

This is useful to target segments with push notifications or In-App messages, either they are coming from your userbase or created by third-party tools.

Custom audiences created using the API can be targeted from Batch’s dashboard or the Campaigns API.

NOTE: Custom Audiences with install IDs are only supported from the 1.1 version of the Custom Audience API. Also note that this version doesn't support custom user IDs and advertising IDs for the moment.

Request structure

Route

The Custom Audience API exposes a PUT endpoint that allows to replace all custom audience users. It removes all previously added users and adds the given ones :

https://api.batch.com/1.1/BATCH_API_KEY/custom-audience/AUDIENCE_NAME

Here is a valid cURL example:

curl -H "Content-Type: application/json" -H "X-Authorization: BATCH_REST_API_KEY" -X PUT -d "@payload.json" "https://api.batch.com/1.1/BATCH_API_KEY/custom-audience/AUDIENCE_NAME"

The AUDIENCE_NAME value must be a string that only contains letters, numbers or the following characters : _, -.

The BATCH_API_KEY value is either your Live or Dev Batch API key from the settings page of your app within the dashboard (⚙ Settings → General).

Headers

In order to authenticate with the API, you need to provide your company REST API Key as the value of the X-Authorization header. You can find it in ⚙ Settings → General.

Put data

The body of the request must contain a valid JSON payload describing the operations to be executed on the custom audience.

Here is a how a complete JSON payload looks like:

{
  "ids":
  [
    {
      "id": "INSTALL-ID-1",
      "attributes": {
         "att1": 3,
         "att2": "string",
         "date(att15)": "2012-08-12T22:30:05",
      },
      "tags": ["value-1", "value-2"]
    },
    {
      "id": "INSTALL-ID-2",
      "attributes": {
         "att1": 2,
         "att2": "string",
         "date(att15)": "2013-08-12T22:30:05",
      },
      "tags": ["value-3", "value-4"]
    }
  ]
}

Let's see the parameters in detail.

IdDescription
idsArray of Objects - Required
An array of objects describing ids to be added to the custom audience.
Supports up to 10,000 elements.

E.g.[{"id":"USER_CUSTOM_ID1"}]
idString -
The ID that will be added to the audience.
E.g.{"id":"USER_CUSTOM_ID"}
attributesObject - Optional.
An object containing attributes to be attached to the id.
Supports up to 15 elements.
tagsArray - Optional.
An object containing tag values to be attached to the id

NOTE: If multiple actions are given for the same ID, only the last one will be taken into account.

Responses

Success

If the POST to the API endpoint is successful you will receive an HTTP 200 confirmation and a token.

{ "indexing_token": "a0082dc6860938a26280bd3ba927303b" }

Once you get your token, you can use it to check the indexing state of this update with the API.

Failure

If the POST data does not meet the API requirements you will receive an actionable error message. Contact us at support@batch.com if you need further support.

  • AUTHENTICATION_INVALID (Http status code: 401, Error code: 10)
  • ROUTE_NOT_FOUND (Http status code: 404, Error code: 20)
  • MISSING_PARAMETER (Http status code: 400, Error code: 30)
  • MALFORMED_PARAMETER (Http status code: 400, Error code: 31)
  • MALFORMED_JSON_BODY (Http status code: 400, Error code: 32)
  • SERVER_ERROR (Http status code: 500, Error code: 1)
  • MAINTENANCE_ERROR (Http status code: 503, Error code: 2)

Processing time

While the indexation of IDs is usually done in realtime, we offer no garanties. If you send a campaign right after the custom audience creation, you might end up with a campaign targeting nobody.