HTTP Methods
Last updated
Metrics can be received on demand via this call or by getting full job information. Also you can defined metrics web hook callback when creating job.
44
Successful response
Run time in seconds of all CPU cores assigned
A Job run time in seconds.
Delete backfilling job.
44
Successful response
The name of job.
Range to scan, block id's or timestamps can be used
An array of filters to apply. Check the Transaction Filter for details.
Batch webhook calls. Specify the number of transactions to be batched in one call. Defaults to 1
Limit CPU for JOB, one CPU does ~20 000 transaction rescans. Speed can vary based on how many records are picked up and sent back. You can look at it as concurrency or threads, one CPU will always send one hook at the moment. Defaults to 1
Updates job params.
44
Successful response
The name of job.
Range to scan, block id's or timestamps can be used
An array of filters to apply. Check the Transaction Filter for details.
Batch webhook calls. Specify the number of transactions to be batched in one call. Defaults to 1
Limit CPU for JOB, one CPU does ~20 000 transaction rescans. Speed can vary based on how many records are picked up and sent back. You can look at it as concurrency or threads, one CPU will always send one hook at the moment. Defaults to 1
Starts a backfilling process. If the time range is big, it could take up to a few minutes to start.
44
Successful response
The name of job.
Range to scan, block id's or timestamps can be used
An array of filters to apply. Check the Transaction Filter for details.
Batch webhook calls. Specify the number of transactions to be batched in one call. Defaults to 1
Limit CPU for JOB, one CPU does ~20 000 transaction rescans. Speed can vary based on how many records are picked up and sent back. You can look at it as concurrency or threads, one CPU will always send one hook at the moment. Defaults to 1
Stops backfilling process. After that job will have PAUSE status.
44
Successful response
The name of job.
Range to scan, block id's or timestamps can be used
An array of filters to apply. Check the Transaction Filter for details.
Batch webhook calls. Specify the number of transactions to be batched in one call. Defaults to 1
Limit CPU for JOB, one CPU does ~20 000 transaction rescans. Speed can vary based on how many records are picked up and sent back. You can look at it as concurrency or threads, one CPU will always send one hook at the moment. Defaults to 1
Retrieves the list of backfilling jobs.
Successful response
The name of job.
Range to scan, block id's or timestamps can be used
An array of filters to apply. Check the Transaction Filter for details.
Batch webhook calls. Specify the number of transactions to be batched in one call. Defaults to 1
Limit CPU for JOB, one CPU does ~20 000 transaction rescans. Speed can vary based on how many records are picked up and sent back. You can look at it as concurrency or threads, one CPU will always send one hook at the moment. Defaults to 1
Retrieves full job information
44
Successful response
The name of job.
Range to scan, block id's or timestamps can be used
An array of filters to apply. Check the Transaction Filter for details.
Batch webhook calls. Specify the number of transactions to be batched in one call. Defaults to 1
Limit CPU for JOB, one CPU does ~20 000 transaction rescans. Speed can vary based on how many records are picked up and sent back. You can look at it as concurrency or threads, one CPU will always send one hook at the moment. Defaults to 1
Creates a backfilling task that retrieves transactions based on specified filters and subsequently submits them to a predefined URL in the hook's data field.
The name of job.
Range to scan, block id's or timestamps can be used
An array of filters to apply. Check the Transaction Filter for details.
Batch webhook calls. Specify the number of transactions to be batched in one call. Defaults to 1
Limit CPU for JOB, one CPU does ~20 000 transaction rescans. Speed can vary based on how many records are picked up and sent back. You can look at it as concurrency or threads, one CPU will always send one hook at the moment. Defaults to 1
Successful response
After success job creation, it will return it's ID.