> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iblueprint.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Retrieve blueprint execution logs and run history
> Retrieve paginated execution log records for a specific iBlueprint blueprint, including step-level token usage, AI provider details, MCP server activity, and error summaries.
The `execution.getExecutionLogs` procedure returns the history of past execution runs for a single blueprint, most recent first. Each log record includes rich metadata about how nodes ran: tokens consumed, which AI providers were used, whether external data sources or MCP servers were contacted, and a summary of any errors. Use this data for auditing, debugging, and billing analysis.
## Request
**Procedure type:** query (HTTP `GET`)
**Endpoint:**
```
GET https://api.iblueprint.ai/api/trpc/execution.getExecutionLogs
```
### Parameters
A URL-encoded JSON object with a `json` key containing the parameters below.
UUID of the blueprint whose logs you want to retrieve.
Maximum number of log records to return. Defaults to `20`.
Number of records to skip before returning results, for pagination. Defaults to `0`.
## Response
Array of execution log records, ordered by `createdAt` descending.
Unique execution log ID.
Blueprint this execution belongs to.
Organization the execution ran under.
User who triggered the execution.
Final status: `running`, `completed`, or `failed`.
ISO 8601 start timestamp, or `null`.
ISO 8601 end timestamp, or `null`.
Total nodes in the run.
Nodes that completed successfully.
Nodes that failed.
Final progress percentage (0–100).
Raw step and log data from the runner.
ISO 8601 timestamp when the log record was created.
ISO 8601 timestamp of the last update.
Total LLM tokens consumed across all nodes.
`true` if any MCP server was contacted during the run.
Number of distinct MCP servers used.
Names of the MCP servers contacted.
`true` if any node fetched data from an external source.
Number of external data sources accessed.
Summary of each external data source accessed.
`true` if the run required OAuth authentication.
`true` if an OAuth flow was initiated.
List of authentication methods used (e.g. `oauth2`, `api_key`).
Connection ID of the primary AI provider used.
Number of distinct AI providers involved.
`true` if any errors occurred.
Total error count.
`true` if any critical (run-stopping) errors occurred.
Human-readable summary of errors, if any.
Variables passed to the execution at start time.
High-level summary of the execution output.
Additional metadata set by the runner.
Number of records returned in this response (not the total across all pages).
## Example
```bash curl theme={null}
curl -G "https://api.iblueprint.ai/api/trpc/execution.getExecutionLogs" \
--data-urlencode 'input={"json":{"blueprintId":"3fa85f64-5717-4562-b3fc-2c963f66afa6","limit":10,"offset":0}}' \
-H "Authorization: Bearer YOUR_API_KEY"
```
```javascript JavaScript theme={null}
const params = new URLSearchParams({
input: JSON.stringify({
json: {
blueprintId: '3fa85f64-5717-4562-b3fc-2c963f66afa6',
limit: 10,
offset: 0,
},
}),
});
const response = await fetch(
`https://api.iblueprint.ai/api/trpc/execution.getExecutionLogs?${params}`,
{ headers: { Authorization: 'Bearer YOUR_API_KEY' } }
);
const { result } = await response.json();
const { logs, total } = result.data.json;
console.log(`Retrieved ${total} execution logs`);
```
### Sample response
```json theme={null}
{
"result": {
"data": {
"json": {
"logs": [
{
"id": "log-uuid-1",
"blueprintId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"status": "completed",
"startTime": "2024-12-01T10:00:00Z",
"endTime": "2024-12-01T10:00:12Z",
"totalSteps": 4,
"completedSteps": 4,
"failedSteps": 0,
"progress": 100,
"totalTokensUsed": 1842,
"usedMcpServers": false,
"aiProvidersUsedCount": 1,
"hasErrors": false,
"inputVariables": { "email_body": "Hi team..." },
"outputSummary": { "summary": "..." }
}
],
"total": 1
}
}
}
}
```
## Cross-blueprint logs
To fetch logs across all blueprints for your account (or organization), use `execution.listRecentExecutions` instead. It accepts `limit`, `offset`, and an optional `organizationId` filter, and returns the same log record shape.
```bash theme={null}
curl -G "https://api.iblueprint.ai/api/trpc/execution.listRecentExecutions" \
--data-urlencode 'input={"json":{"limit":50,"offset":0}}' \
-H "Authorization: Bearer YOUR_API_KEY"
```