Skip to main content
Solved

How can I set header values when using HTTP Request in FME Automations?

  • December 17, 2019
  • 2 replies
  • 94 views

ld
Participant
Forum|alt.badge.img+1
  • Participant

Is there a way to set headers for the HTTP call? Ironically I am trying to call the FME Server API, so I need to set, for example,

 

Authorization: token fmetoken=YourTokenHere

 

Best answer by nathanatsafe

Hi @ld,

 

Thanks for your question. I don't believe 'custom' headers are supported at this time. But I will check in with our development team and also find out if we have plans to add this in the future.

 

 

In the meantime are you able to use those HTTP Authentication parameters for authorization instead? There are also a couple of other options documented: https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html. Notably you could attach the token as a query string parameter (eg. http://myhost.com/fmerest/v3/repositories?fmetoken=XXXXXXXXXXXXXXX).

Hope this helps,

Nathan

 

 

View original
Did this help you find an answer to your question?

2 replies

nathanatsafe
Safer
Forum|alt.badge.img+7
  • Safer
  • Best Answer
  • December 19, 2019

Hi @ld,

 

Thanks for your question. I don't believe 'custom' headers are supported at this time. But I will check in with our development team and also find out if we have plans to add this in the future.

 

 

In the meantime are you able to use those HTTP Authentication parameters for authorization instead? There are also a couple of other options documented: https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html. Notably you could attach the token as a query string parameter (eg. http://myhost.com/fmerest/v3/repositories?fmetoken=XXXXXXXXXXXXXXX).

Hope this helps,

Nathan

 

 


ld
Participant
Forum|alt.badge.img+1
  • Author
  • Participant
  • December 20, 2019
nathanatsafe wrote:

Hi @ld,

 

Thanks for your question. I don't believe 'custom' headers are supported at this time. But I will check in with our development team and also find out if we have plans to add this in the future.

 

 

In the meantime are you able to use those HTTP Authentication parameters for authorization instead? There are also a couple of other options documented: https://docs.safe.com/fme/html/FME_REST/apidoc/v3/index.html. Notably you could attach the token as a query string parameter (eg. http://myhost.com/fmerest/v3/repositories?fmetoken=XXXXXXXXXXXXXXX).

Hope this helps,

Nathan

 

 

Thanks @nathanatsafe, I do also need to set the Content-Type so would need these headers. I'll make the call in a scheduled workspace instead.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings