The Opteo API allows you to retrieve and modify your Opteo account data programmatically, for example listing improvements or updating the budget of an account. The API is based on REST principles.
⚠️ The Opteo API is currently invite only and still a work in progress
Base URL: https://api.opteo.dev
You must specify the API version and base customer resource when building request URLs for your desired endpoint. For example:
https://api.opteo.dev/v0/customers/{customer-id}/{resource}
Note: the customer id refers to the Google Ads customer id. This is found in Google Ads, not Opteo.
To start using the API you will need to correctly authenticate all requests.
As the API is still invite only, authentication tokens are provided by the team upon request. If you don't have an API key and want to start using the Opteo API, please contact our support team.
To authenticate a request, you must use bearer auth and set a Authorization header on your HTTP request.
cURL
curl -i \
-H "Accept: application/json" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer {TOKEN}" \
https://api.opteo.dev/v0/...JavaScript
const rawResponse = await fetch("https://api.opteo.dev/v0/...", {
method: "POST",
headers: {
Accept: "application/json",
"Content-Type": "application/json",
Authorization: "Bearer {TOKEN}"
},
body: JSON.stringify(...),
});
const content = await rawResponse.json();All API requests must be made over HTTPS. Calls made over plain HTTP will fail.
The Opteo API uses standard HTTP response codes. All successful requests will return a 200 status code and any errors will be in the range 400 (client) to 500 (server).
All failing requests will return the status code and a descriptive error message. For example, if you attempt to access resources for a non-active customer:
{
"status": 403,
"message": "Forbidden - Client not active in Opteo, this may be due to a billing problem, or because it isn't selected in Linked Accounts"
}Get the list of customers (aka google ads accounts) that are accessible using the supplied API token. These customers must be linked in Opteo.
URL
GET https://api.opteo.dev/v0/customers
Response
{
"status": 200,
"data": [
{
"customerId": "123-456-7890",
"name": "Plumbers United"
},
{
"customerId": "098-765-4321",
"name": "Electricians Online"
}
]
}Get the set Opteo budget for a connected Google Ads account. No ID is required to get the budget.
URL
GET https://api.opteo.dev/v0/customers/{customer-id}/budget
Response
{
"status": 200,
"data": {
"lastUpdated": "2021-09-09T15:02:24.000Z",
"budget": 100
}
}In the case where no budget has ever been set in Opteo, the budget will be 0 and lastUpdated will be null.
Update the Opteo budget for a connected Google Ads account. You must specify the new budget in the JSON request body.
URL
POST https://api.opteo.dev/v0/customers/{customer-id}/budget
Parameters
{
"budget": 123.45
}Response
{
"status": 200,
"data": {
"lastUpdated": "2021-09-09T15:02:30.000Z",
"budget": 123.45
}
}Get a list of improvements that are currently available for a linked Google Ads account. This list will reflect the contents of the "Active" tab in the Opteo interface, and will be sorted by "priority", which is a rough measure of an improvement's impact to the account.
Improvements that are completed or dismissed will not be returned.
URL
GET https://api.opteo.dev/v0/customers/{customer-id}/improvements
Response
{
"status": 200,
"data": [
{
"improvement_id": 1234,
"url": "https://app.opteo.com/user/:user_id/account/4567/improvements/active/1234",
"title": "Write New Ad", // Title of the improvement. Is sometimes dynamic based on the contents of the improvement.
"type": "ad_comparison_v2", // Type of the improvement, as an enum.
"rec_action": "write_ad_v2", // The action that we're recommending, as an enum.
"created_ts": "2022-03-15T04:44:35.000Z", // When the improvement was created.
"last_updated_ts": "2022-04-12T09:30:35.000Z", // When the improvement was last updated with new data.
"location": [
// The location in the Google Ads account that the improvement is concerned with.
{
"entity": "campaign",
"label": "My Campaign Name"
},
{
"entity": "adgroup",
"label": "My Adgroup Name"
},
// The "text_description" and "text_variables" are designed to help surface key
// information about an improvement.
"text_description": "The ad group My Ad Group only contains one ad. Create a new ad for this ad group so you can test for the best-performing creative approach.",
"text_variables": {
"Campaign": "My Campaign",
"Ad Group": "My Ad Group",
},
]
},
...
]
}Get a list of improvements that have been completed for a linked Google Ads account.
This list will reflect the contents of the "Completed" tab in the Opteo interface.
It is sorted by completed_ts, which is the time when the improvement was pushed (descending).
URL
GET https://api.opteo.dev/v0/customers/{customer-id}/improvements/completed
Response
{
"status": 200,
"data": [
{
"improvement_id": 5678,
"url": "https://app.opteo.com/user/:user_id/account/1234/improvements/completed/5678",
"title": "Add New Keyword", // Title of the improvement. Is sometimes dynamic based on the contents of the improvement.
"type": "sqr", // Type of the improvement, as an enum.
"rec_action": "check_query_relevance", // The action that we're recommending, as an enum.
"completed_ts": "2021-09-07T14:00:50.000Z", // When the improvement was pushed.
// The location in the Google Ads account that the improvement is concerned with.
"location": [
{
"entity": "search-query",
"label": "hotels near me"
}
],
// The "text_description" and "text_variables" are designed to help surface key
// information about an improvement.
"text_description": "The search term `hotels near me` is triggering your ads, but has not been added to your account as a keyword. You may want to add `hotels near me` as a new keyword or a negative keyword.",
"text_variables": {
"Cost": "$12.00",
"Conversions": "2",
"CPA": "$6.00"
},
"completed_by_email": "steven@agency.com"
},
...
]
}Get a list of all reports for all linked accounts.
Each item in the list will include a pdfPath, which
can be used to fetch the report's PDF export.
Archived or deleted reports will not be returned.
URL
GET https://api.opteo.dev/v0/reports
Response
{
"status": 200,
"data": [
{
"accountId": 1234,
"accountName": "Plumbers Ltd",
"title": "Google Ads Report",
"fromDate": "2023-04-01",
"toDate": "2023-04-30",
"pdfPath": "/v0/reports/pdf/09440bbe-1638-4084-4378-c0d20e3ffefe"
},
{
"accountId": 1234,
"accountName": "Plumbers Ltd",
"title": "Google Ads Report",
"fromDate": "2023-03-01",
"toDate": "2023-03-30",
"pdfPath": "/v0/reports/pdf/daf46eb4-4901-45c4-9e75-de58db6effff"
},
{
"accountId": 3456,
"accountName": "Electricians Online",
"title": "Google Ads Report",
"fromDate": "2023-04-01",
"toDate": "2023-04-30",
"pdfPath": "/v0/reports/pdf/f1be9043-17a0-4a3d-8689-91d40deeffff"
}
]
}Get the rendered PDF for a single report.
URL
GET https://api.opteo.dev/v0/reports/pdf/{report-uuid}
Response
The PDF will be returned as a binary response with the `Content-Type` header set to `application/pdf`.
This API supports making GAQL queries to retrieve arbitrary data from Google Ads. GAQL queries are similar to SQL queries, but are specific to the Google Ads API.
- For details on how to write GAQL queries, see the GAQL reference.
- For a complete list of what can be fetched via GAQL, see the Google Ads API reference.
- In the example below, we use the
campaignresource.
URL
GET https://api.opteo.dev/v0/customers/{customer-id}/gaql?query={YOUR_GAQL_QUERY}
Parameters
The query parameter is required and should be a valid GAQL query. The query should be URL encoded.
For example:
query: SELECT campaign.name, campaign.id, metrics.impressions FROM campaign
GET request: https://api.opteo.dev/v0/customers/1234567890/gaql?query=SELECT%20campaign.name,%20campaign.id,%20metrics.impressions%20FROM%20campaign
Response
{
"status": 200,
"data": [
{
"campaign": {
"name": "First Campaign",
"id": 685312434,
"resource_name": "customers/1234567890/campaigns/685312434"
},
"metrics": {
"impressions": 5951
}
},
{
"campaign": {
"name": "Second Campaign",
"id": 685608890,
"resource_name": "customers/1234567890/campaigns/685608890"
},
"metrics": {
"impressions": 68004
}
},
]
}