Through this endpoint, users can synchronize a specific address with Crypto APIs. Once the synchronization is complete, users will have access to the full historical data associated with the address.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId
is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
API Key
{
"context": "yourExampleString",
"data": {
"item": {
"address": "0x3d0b25fe09e2cd92f06ba776391a122519936e90",
"callbackUrl": "https://example.com"
}
}
}
{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"address": "0x3d0b25fe09e2cd92f06ba776391a122519936e90",
"blockchain": "ethereum",
"callcackUrl": "https://example.com",
"isActive": true,
"network": "sepolia",
"syncStatus": "completed"
}
}
}