POST Leads using Publisher API v2
- Adam Carter
- Sebastian Grabowski (Unlicensed)
Publisher API v2
- 1 Publisher API v2
- 1.1 1.0 Scope
- 1.2 2.0 Enterprise URL
- 1.2.1 3.1 Prerequisites
- 1.2.2 3.2 Authentication Token
- 1.2.2.1 GET Request
- 1.2.2.2 Response
- 1.2.3 3.3 Form Fields Endpoint
- 1.2.3.1 GET Request
- 1.2.3.2 Response
- 1.2.4 3.4 Campaign Links Endpoint
- 1.2.4.1 GET Request
- 1.2.4.2 Response
- 1.2.5 3.5 Campaign Lead Endpoint
- 1.2.5.1 POST REQUEST
- 1.2.5.2 Example Request Body
- 1.2.5.3 Response
1.0 Scope
This document contains the technical information required for accessing the RESTful API offered by Convertr. Currently, the main goal of this API is to feedback live stats to our network and facilitate the delivery of new customer records.
It should be noted that all reporting information gathered from the use of this API is unconfirmed and should be used merely as an awareness tool while running a campaign with us.
2.0 Enterprise URL
This version of the API is accessible from the following URL, at this point there is a single entry point for all requests.
https://{enterprise}.cvtr.io/api/v2/3.0 Usage & Examples3.1 Prerequisites
All Publisher users by default have access to the Convertr Publisher API. Your access credentials are supplied with your campaign assets after you have been assigned to a campaign, but are also available from the Convertr Dashboard.
3.2 Authentication Token
In order for you to query the API, all requests must be sent with an authentication token.
This needs to be requested from the following URL using a GET request. Once the token has been returned, it will expire after 60 minutes.
GET Request
https://{enterprise}.cvtr.io/oauth/v2/token?grant_type=https://convertr.cvtr.io/grants/api_key&client_id={CLIENT_ID}&client_secret={CLIENT_SECRET}&api_key={API_KEY}Parameter | Required | Description | |
|---|---|---|---|
| 1 | client_id | Yes | Client ID which is supplied on a platform wide bases |
| 2 | client_secret | Yes | Client Secret which is supplied on a platform wide bases |
| 3 | api_key | Yes | API Key that is unique to each user |
Response
{
access_token: "ODM5NTIwNjk1MjdhNTMzMzk0MTY2Y2ZkYjg2OWFlN2Y5YzZlNTk1NmUwZmVjOGRkMDhhMzllYTA2ZTA0MDI3Zg"
expires_in: 3600
token_type: "bearer"
scope: null
refresh_token: "YTQzODk3MDdiM2FhMGYzODYyOTcyOTBkYWZiZWI3YzJmNmEwYmJkYWJiM2I0NzU1Y2Q5OTcwZDA0YzhiZGNjYQ"
}Additionally, a token can be requested using user credentials. In order to do that, you need to send a POST request to
Parameter | Required | Description | |
|---|---|---|---|
| 1 | client_id | Yes | Client ID which is supplied on a platform wide bases |
| 2 | client_secret | Yes | Client Secret which is supplied on a platform wide bases |
| 3 | api_key | Yes | API Key that is unique to each user |
| 4 | grant_type | Yes | Must be set to "password" |
| 5 | username | Yes | Your username |
| 6 | password | Yes | Your password |
3.3 Form Fields Endpoint
This API call will supply an array of forms which are available to `POST` leads to (see section 3.5) on a given campaign.
The response will allow you to see which form fields are available to populate per form (each campaign can have multiple forms).
GET Request
Parameter | Required | Description | |
|---|---|---|---|
| 1 | CAMPAIGN_ID | Yes | ID for the campaign you are wishing to see a list of available forms |
| 2 | ACCESS_TOKEN | Yes | Access token acquired in 3.2 |
Response
3.4 Campaign Links Endpoint
This API method will return an array of available links for the given campaign. Links are required as it provides insight into which channel a lead entered the Convertr Platform or was captured.
GET Request
Parameter | Required | Description | |
|---|---|---|---|
| 1 | CAMPAIGN_ID | Yes | ID for the campaign you are wishing to see a list of available links |
| 2 | ACCESS_TOKEN | Yes | Access token acquired in 3.2 |
Response
3.5 Campaign Lead Endpoint
POST REQUEST
Parameter | Required | Description | |
|---|---|---|---|
| 1 | PUBLISHER_ID | Yes | Publisher id sending the request |
| 2 | LINK_ID | Yes | Link to associate lead with (see section 3.2 or Publisher Media Kit email) |
| 3 | FORM_ID | Yes | Form Id to match body to (see section 3.3 or Publisher Media Kit email) |
| 4 | ACCESS_TOKEN | Yes | Access token acquired in 3.2 |
Example Request Body
Response
4.0 Error Responses
Errors will be returned with a status `code` and `message`. Where applicable additional information will be provided in an `errors` array.
Error Code | Error Body | Description | |
|---|---|---|---|
| 1 | 400 |
| Invalid post data, check your request maps to the form fields in section 3.4 |
| 2 | 401 |
| Your access token has expired and you must request a new token, see section 3.2 |
| 3 | 403 |
| The requested campaign hasn't started yet. Enquire with your campaign manager as to when it will be available |
| 4 | 403 |
| The requested campaign has already been successfully fulfilled and no more leads are being accepted |