Try to use that link that I posted. You will get all the info.
Only when there are errors you can see them in history.
You mean this: https://api.moralis-streams.com/api-docs/? No it’s not help me. Because if I see the errors I need find out what the problem: my endpoint not working, problem somewhere and so on.
Yep, but what about details?
on what type of details you are referring?
if it is a webhook send error then we were not able to send that webhook request, either the webhook url is not working or it didn’t return a 200 http error code
1 Like
Yep. I am talking about the same ) So let me catch the error and I came back to discuss it.
Thanks.
For now you can try to use the swagger interface in order to see more info about them.
1 Like
That is in my CP I still can’t see detailed logs? Which one the swagger interface? Please provide more details.
Thanks.
You have all the access with the swagger interface.
You add your api key and look in history after that. You click on try for an endpoint and then provide the parameters and then click on execute.
1 Like
Ok. I am asking not about it but … So how I can get details about fails which I showed at the screenshot above?
I see this one - https://api.moralis-streams.com/api-docs/#/History/ReplayHistory. Which I think equivalent this:
But it’s still not the same which I need. I need details of fails. For example my endpoint is not working, stream got error while trying to delivery info and so on … I need details of these logs.
you mean that you want to know the reason why it failed a particular stream?
that reason is found in the stream status, you can get that stream status from the swagger interface or with the SDK or with a CURL request
1 Like
YES!!! At last!!!
Where? )
here
https://api.moralis-streams.com/api-docs/#/EVM%20Streams/GetStream
you will also get the status of a stream when you get a stream config
1 Like
I don’t see any logs:
{
"id": "9b4ae7cc-25fb-4e06-9b40-4090f81fbbb0",
"webhookUrl": "",
"description": "PairCreated / Mint events for for Ethereum / Bsc Mainnet.",
"tag": "test, bsc mainnet, eth mainnet",
"demo": false,
"topic0": [
"PairCreated(address,address,address,uint256)",
"Mint(address,uint256,uint256)"
],
"allAddresses": true,
"includeNativeTxs": false,
"includeContractLogs": true,
"includeInternalTxs": false,
"abi": [
{
"anonymous": false,
"inputs": [
{
"indexed": true,
"internalType": "address",
"name": "token0",
"type": "address"
},
{
"indexed": true,
"internalType": "address",
"name": "token1",
"type": "address"
},
{
"indexed": false,
"internalType": "address",
"name": "pair",
"type": "address"
},
{
"indexed": false,
"internalType": "uint256",
"name": "",
"type": "uint256"
}
],
"name": "PairCreated",
"type": "event"
},
{
"anonymous": false,
"inputs": [
{
"indexed": true,
"internalType": "address",
"name": "sender",
"type": "address"
},
{
"indexed": false,
"internalType": "uint256",
"name": "amount0",
"type": "uint256"
},
{
"indexed": false,
"internalType": "uint256",
"name": "amount1",
"type": "uint256"
}
],
"name": "Mint",
"type": "event"
}
],
"advancedOptions": null,
"chainIds": [
"0x38"
],
"status": "active",
"statusMessage": "Stream is active"
}
I was referring to this info, when the stream is in error state there will be a reason
what do you see in history if you try it with limit 2?
1 Like
