When you send a request to the Adsroid API, the response always contains the agent’s answer along with optional metadata such as status and credit usage.
Adsroid responses are designed to be simple, predictable and easy to parse in any automation tool (Make, Zapier, n8n) or backend environment.
Successful Response
A successful request returns an object with at least one field:
Example
{
"message": "Here is your Google Ads performance analysis...",
"status": 200
}
Fields
| Field | Type | Description |
|---|---|---|
| message | string | The agent’s response text. Equivalent to what you would receive inside the Adsroid interface. |
| status | number | HTTP-like status code (e.g. 200 for success). |
Message Field
The message field contains the full AI-generated output.
It may include:
- rich text
- bullet points
- recommendations
- analysis of advertising accounts
- automatic reporting
- strategic insights
Example:
{
"message": "📊 You spent €540 this month for 128 conversions (CPA €4.21)..."
}
You can return this directly to:
- Slack
- Make modules
- Databases
- CRM systems
Error Response
If something is wrong in your request, the API returns a structured error:
Example
{
"error": "invalid_api_key",
"message": "Your API key is not valid.",
"status": 401
}
Common error fields
| Field | Type | Description |
|---|---|---|
| error | string | Machine-readable error code. |
| message | string | Human-readable explanation. |
| status | number | Error HTTP-like code (e.g. 400, 401, 403, 429). |
Response Format Summary
- Always JSON
- Always contains
message - Consistent structure for success and errors
- Perfectly compatible with automation platforms
- Reliable for real-time streaming via Actions, Workflows, or cron jobs