GHi @Jlagdam You can modify the code like this to include more headers eg: Adding Additional Headers to API Call node
JHello goodday, I mean on this block because its an outside api and as i observe that they use api_key inside the header exmple : curl --request POST \
--url https://api.tokenmetrics.com/tmai \
--header 'accept: application/json' \
--header 'api_key: tm-**----**' \
--header 'content-type: application/json'
--url https://api.tokenmetrics.com/tmai \
--header 'accept: application/json' \
--header 'api_key: tm-**----**' \
--header 'content-type: application/json'
GOkay, for this you can simply add the API key inside the Authorization field, you can check if it requires Bearer or not. As the Authorization go to headers.
Jauthorization can be blank . however it needs api_key parameter on header.
Jive test it on hoppscotch.io it only works when i put api_key on headers
J
GAs mentioned above, you'll require to modify the header to accept api_key.
GUse the AI node generator to create a node which you can use, paste the curl request in additional context and provide required prompt to the it - https://docs.buildship.com/ai-nodes.
JI understand, but its not a trigger block. as you can see it was below a telegram send message block.
Jso basically there is no option to hard code the headers
Jbecause the hard code option will show only when the API call block is the trigger, but not when the API call block was under the trigger.
JSo maybe workaround i think is I should create a new workflow so that the API call block will be the on the trigger and fetch the data. tho its too inefficient to do because its making a double call .