Convert API for Experiences Serving (1.1.0)

Download OpenAPI specification:Download

Serve and track experiences to your users using Convert APIs and tools

SDK Key Authentication

In order to authenticate requests to the Convert Tracking/Config API, you need to provide the SDK key secret inside the Authorization header.

Note:

  • For the Projects that have settings.disable_default_config=true , access will work only through the use of SDK Key Authentication method with the associated endpoints.
  • For the Projects that have settings.disable_default_config=false , access will work through the use of SDK Key Authentication method with the associated endpoints or without authentication, through the default endpoints.
  • An SDK key could have a secret associated or not. If it has a secret, it should be provided in the Authorization header. If it doesn't have a secret, the Authorization header should be empty and the request would be authorized if the provided SDK key is found.

Project Config

Api endpoint which returns all the configuration of one project inside an account. This can be consumed inside various fullstack sdks

Default Get Project Config

This is the default endpoint that does not need SDK Keys to returns the project's config to be consumed in various sdks

path Parameters
account_id
required
integer

ID of the account that owns the retrieved/saved data

project_id
required
integer

ID of the project to be retrieved

Responses

Response samples

Content type
application/json
{
  • "account_id": "string",
  • "project": {
    },
  • "goals": [
    ],
  • "locations": [
    ],
  • "audiences": [
    ],
  • "segments": [
    ],
  • "experiences": [
    ],
  • "archived_experiences": [
    ],
  • "features": [
    ]
}

Sdk-Key Get Project Config

This endpoint returns the project's config to be consumed in various sdks using the SDK Key

Authorizations:
sdkKeyAuth
path Parameters
sdk_key
required
string

The SDK key used to retrieve the project's config

Responses

Response samples

Content type
application/json
{
  • "account_id": "string",
  • "project": {
    },
  • "goals": [
    ],
  • "locations": [
    ],
  • "audiences": [
    ],
  • "segments": [
    ],
  • "experiences": [
    ],
  • "archived_experiences": [
    ],
  • "features": [
    ]
}

Experiences Tracking

Endpoint which allows tracking events to be sending to Convert's tracking backend

Sdk-Key Send Tracking

This endpoint allows sending of tracking events to the Convert tracking server via SDK Key authentication

Authorizations:
sdkKeyAuth
path Parameters
sdk_key
required
string

The SDK key used to identify the project where that the data belongs to

Request Body schema: application/json

A JSON object containing the tracking events sent to the Convert tracking servers.

accountId
string

ID of the account under which the project is setup

projectId
string

ID of the project under which the tracking occurs

enrichData
boolean

Flag to determine whether the data is gonna be enriched before the events are stored for reporting. For example, in case of a conversion event, if this flag is on and bucketing is not provided, the bucketing stored on the backend datastore for the given visitor ID would be used. Same applies for segments.

Note: this flag is only available for some plans

Array of objects

List of visitors tracked. Each visitor can have multiple events.

Responses

Request samples

Content type
application/json
{
  • "accountId": "string",
  • "projectId": "string",
  • "enrichData": true,
  • "visitors": [
    ]
}

Response samples

Content type
application/json
{
  • "code": 0,
  • "message": "string"
}

Send Tracking

This endpoint allows sending of tracking events to the Convert tracking server

path Parameters
account_id
required
integer

ID of the account that owns the given project

project_id
required
integer

ID of the project to which the events belong to

Request Body schema: application/json

A JSON object containing the tracking events sent to the Convert tracking servers.

accountId
string

ID of the account under which the project is setup

projectId
string

ID of the project under which the tracking occurs

enrichData
boolean

Flag to determine whether the data is gonna be enriched before the events are stored for reporting. For example, in case of a conversion event, if this flag is on and bucketing is not provided, the bucketing stored on the backend datastore for the given visitor ID would be used. Same applies for segments.

Note: this flag is only available for some plans

Array of objects

List of visitors tracked. Each visitor can have multiple events.

Responses

Request samples

Content type
application/json
{
  • "accountId": "string",
  • "projectId": "string",
  • "enrichData": true,
  • "visitors": [
    ]
}

Response samples

Content type
application/json
{
  • "code": 0,
  • "message": "string"
}