Trying to use point and click

External Services

but unsuccessful with

Named Credential authorization.

A 3rd party service just requires the Authorization Token be sent with request. Not seeing any options in Named Credentials to use this? Before being pointed to creating an Apex Class or Connected App I want to confirm that the point and click approach for this is NOT possible today.

Saw this post a few years ago here which seems to confirm the above but not clearly.

API I'm trying to use is pretty basic RealValidation. Seems like rest of External Service piece may be working when used in a Flow.

  • Not dup as Im trying to create Named Credential, not using URL endpoint. This is starting with a Named Credential.
    – ddeve
    May 30, 2019 at 17:58

1 Answer 1


Based on RealValidation doc in your question, this 3rd party service doesn't appear to use a standardized authentication protocol, it wants a token (which they equate to a password) to be sent in as one of the query parameters in the request

RealValidation API

Named Credentials won't do much for you in this case. Stick the value of their token into a protected custom setting or protected custom metadata type then have your Apex code dynamically build the request URL.

  • Its an auth token for the API. They dont allow name and password for API.
    – ddeve
    May 30, 2019 at 17:48
  • @user2451 It's still their own, proprietary (and hilariously bad) token scheme so Named Credentials won't help you.
    – identigral
    May 30, 2019 at 17:55
  • 1
    The point is, if you can only merge these parameters into the URI, you can't use NamedCredential. If you could merge them into headers or request body, you'd be good to go. As such, you'll need to use some other tool (e.g. Hierarchy Custom Setting).
    – Adrian Larson
    May 30, 2019 at 17:59

Not the answer you're looking for? Browse other questions tagged .