Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

API Poller POST method - Content Types

We're trying to use an API Poller with a POST method.

From our testing it looks like even though we're specifying a Content-Type header, it's not being forwarded with the request.

Specifically we need to use application/www-form-urlencoded rather than JSON etc.

Any ideas on whether this is supported in the API Pollers?

Find more posts tagged with

Accepted answers

benatarc

We've done further testing on this and can confirm that the Content-Type header is not forwarded with the request.

All comments

adam.beedell

Should be fine in the headers section. There's a few other workarounds available if needed

benatarc

Our testing with the headers doesn't seem to be working... would love to hear any workarounds you know of

adam.beedell

Workaround 1 - You can usually swap a header into the URL
Workaround 2 - Generate the equivalent in a SAM script monitor (or maybe a https monitor), there's a few templates around for this

I'd be really surprised if it wasnt being transferred in the first place, feels more like there's a JSON contenttype coming in as default and getting processed first, or something like that. The content-type stuff can be case sensitive sometimes so worth checking in case

benatarc

We've done further testing on this and can confirm that the Content-Type header is not forwarded with the request.

benatarc

Thanks for all your help... We tried including it in the URL and some other workarounds but nothing worked.

We set up header logging for the destination API and found that although we had the Content-Type header specified in the poller, it was never sent through.

Postman tests to the same API with the same Content-Type header worked without a problem.