Retrieve a list of all incomplete backfills for your team. This endpoint returns only backfills that are not yet finished.
What are "incomplete" backfills?
- Included: Backfills with status
CREATED,SCHEDULED,RUNNING, orFAILED - Excluded: Backfills with status
COMPLETEDorCANCELLED
Returns: Array of backfill objects sorted by creation time (newest first).
Important Notes:
- You must have
dwh.transfer.viewpermission - Only backfills belonging to your team are returned
- The list includes backfills for all transfers in your team
- Each backfill includes real-time progress tracking for running backfills
Rate limited: calls to this endpoint within 200ms of the team's previous call return 429. Every call that passes authentication and access checks and isn't itself rate-limited starts the window, even if it then fails (e.g. 404). The window is shared by all API keys and access tokens of the team, and does not depend on resource IDs in the path.
API key authentication. Create API keys in the Supermetrics Hub and send
them in the Authorization header:
Authorization: Bearer <your-api-key>
ID of the team
List of incomplete backfills retrieved successfully
Multiple incomplete backfills
{
"meta": {
"request_id": "01892A4D-7586-7000-8000-000000000000"
},
"data": [
{
"transfer_backfill_id": 12347,
"transfer_id": 456790,
"range_start_date": "2024-02-01",
"range_end_date": "2024-02-28",
"created_time": "2024-03-01T14:00:00Z",
"created_user_id": 789,
"start_time": "2024-03-01T14:30:00Z",
"end_time": null,
"status": "RUNNING",
"transfer_runs_total": 28,
"transfer_runs_created": 28,
"transfer_runs_completed": 15,
"transfer_runs_failed": 0,
"error_report": []
},
{
"transfer_backfill_id": 12346,
"transfer_id": 456789,
"range_start_date": "2024-01-15",
"range_end_date": "2024-01-31",
"created_time": "2024-02-15T09:30:00Z",
"created_user_id": 790,
"start_time": "2024-02-15T10:00:00Z",
"end_time": null,
"status": "RUNNING",
"transfer_runs_total": 17,
"transfer_runs_created": 17,
"transfer_runs_completed": 10,
"transfer_runs_failed": 0,
"error_report": []
},
{
"transfer_backfill_id": 12345,
"transfer_id": 456788,
"range_start_date": "2024-01-01",
"range_end_date": "2024-01-14",
"created_time": "2024-02-01T08:00:00Z",
"created_user_id": 789,
"start_time": null,
"end_time": null,
"status": "SCHEDULED",
"transfer_runs_total": 14,
"transfer_runs_created": 14,
"transfer_runs_completed": 0,
"transfer_runs_failed": 0,
"error_report": []
}
]
}No incomplete backfills
{
"meta": {
"request_id": "01892A4D-7586-7000-8000-000000000000"
},
"data": []
}Response envelope containing a list of incomplete backfills.
Metadata included in every API response.
Unique identifier for the request, for tracking and debugging.
Array of incomplete backfill objects
Unique identifier of the backfill
ID of the transfer this backfill belongs to
Start date of the backfill range
End date of the backfill range
Timestamp when the backfill was created (ISO 8601 format)
ID of the user who created the backfill
Timestamp when the backfill was cancelled/removed (ISO 8601 format)
ID of the user who cancelled/removed the backfill
Timestamp when the backfill processing started (ISO 8601 format)
Timestamp when the backfill processing completed (ISO 8601 format)
Current status of the backfill
Total number of transfer runs created for this backfill
Number of transfer runs that have been created
Number of transfer runs that have completed successfully
Number of transfer runs that have failed
List of errors that occurred during backfill processing (empty array if no errors)
The date of the transfer run that failed
Error message describing what went wrong
Unauthorized
{
"meta": {
"request_id": "BXaEFVtjc7TXaJxgZhmFgSUD9edqq_CN"
},
"error": {
"code": "UNAUTHORIZED",
"message": "Authentication is required."
}
}Standard envelope returned by all error (4xx/5xx) responses.
Metadata included in every API response.
Unique identifier for the request, for tracking and debugging.
Machine- and human-readable detail for a failed request.
Stable, screaming-snake-case identifier for the error condition. Clients should branch on this, not on message. Common values include BAD_REQUEST, UNAUTHORIZED, FORBIDDEN, NOT_FOUND, CONFLICT_ERROR, PERMISSION_ERROR, UNPROCESSABLE_ENTITY, UNPROCESSABLE_CONTENT, TOO_MANY_REQUESTS, INTERNAL_SERVER_ERROR, DUPLICATION_FAILED, SERVICE_UNAVAILABLE; domains may define additional codes.
Short, human-readable summary of the error.
Optional longer explanation specific to this occurrence.
Access forbidden
{
"meta": {
"request_id": "BXaEFVtjc7TXaJxgZhmFgSUD9edqq_CN"
},
"error": {
"code": "FORBIDDEN",
"message": "You do not have access to this resource."
}
}Standard envelope returned by all error (4xx/5xx) responses.
Metadata included in every API response.
Unique identifier for the request, for tracking and debugging.
Machine- and human-readable detail for a failed request.
Stable, screaming-snake-case identifier for the error condition. Clients should branch on this, not on message. Common values include BAD_REQUEST, UNAUTHORIZED, FORBIDDEN, NOT_FOUND, CONFLICT_ERROR, PERMISSION_ERROR, UNPROCESSABLE_ENTITY, UNPROCESSABLE_CONTENT, TOO_MANY_REQUESTS, INTERNAL_SERVER_ERROR, DUPLICATION_FAILED, SERVICE_UNAVAILABLE; domains may define additional codes.
Short, human-readable summary of the error.
Optional longer explanation specific to this occurrence.
Too Many Requests
{
"meta": {
"request_id": "BXaEFVtjc7TXaJxgZhmFgSUD9edqq_CN"
},
"error": {
"code": "TOO_MANY_REQUESTS",
"message": "Rate limit exceeded. Retry later."
}
}Standard envelope returned by all error (4xx/5xx) responses.
Metadata included in every API response.
Unique identifier for the request, for tracking and debugging.
Machine- and human-readable detail for a failed request.
Stable, screaming-snake-case identifier for the error condition. Clients should branch on this, not on message. Common values include BAD_REQUEST, UNAUTHORIZED, FORBIDDEN, NOT_FOUND, CONFLICT_ERROR, PERMISSION_ERROR, UNPROCESSABLE_ENTITY, UNPROCESSABLE_CONTENT, TOO_MANY_REQUESTS, INTERNAL_SERVER_ERROR, DUPLICATION_FAILED, SERVICE_UNAVAILABLE; domains may define additional codes.
Short, human-readable summary of the error.
Optional longer explanation specific to this occurrence.
Internal server error
{
"meta": {
"request_id": "BXaEFVtjc7TXaJxgZhmFgSUD9edqq_CN"
},
"error": {
"code": "INTERNAL_SERVER_ERROR",
"message": "An unexpected error occurred."
}
}Standard envelope returned by all error (4xx/5xx) responses.
Metadata included in every API response.
Unique identifier for the request, for tracking and debugging.
Machine- and human-readable detail for a failed request.
Stable, screaming-snake-case identifier for the error condition. Clients should branch on this, not on message. Common values include BAD_REQUEST, UNAUTHORIZED, FORBIDDEN, NOT_FOUND, CONFLICT_ERROR, PERMISSION_ERROR, UNPROCESSABLE_ENTITY, UNPROCESSABLE_CONTENT, TOO_MANY_REQUESTS, INTERNAL_SERVER_ERROR, DUPLICATION_FAILED, SERVICE_UNAVAILABLE; domains may define additional codes.
Short, human-readable summary of the error.
Optional longer explanation specific to this occurrence.