Skip to main content
Best answer

Invalid Token

  • Aug 23, 2020 10:25 PM UTC
  • 7 replies
  • 1566 views

Hello,

I’m creating a custom webhook zap with Spotify and I believe I put in a valid token, but I am receiving this error -  “Only valid bearer authentication supported".

 

Best answer by Troy Tessalone

The API Key needs to be placed after Bearer, not in the Basic Auth field.

View original
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

7 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • Aug 24, 2020 2:29 AM UTC

Share screenshots of your Zap step that’s resulting in an error.


  • Author
  • Beginner
  • Aug 24, 2020 2:42 AM UTC

@Troy Tessalone 

 


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • Aug 24, 2020 2:54 AM UTC

There are 2 required header fields: Authorization & Content-Type.

Add “Authorization” as a field below Content-Type in your Zap step.

Then make sure the value has “Bearer ” before the API Key.

You can test the Spotify API here: https://developer.spotify.com/console/delete-playlist-tracks/

 

 

 


  • Author
  • Beginner
  • Aug 24, 2020 3:10 AM UTC

@Troy Tessalone I’m getting the same error with this update. 

 

 


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • Answer
  • Aug 24, 2020 3:23 AM UTC

The API Key needs to be placed after Bearer, not in the Basic Auth field.


  • Author
  • Beginner
  • Aug 24, 2020 4:35 AM UTC

Thanks that almost worked, but I’m getting a “The app returned "JSON body doesn't conform to specification" error now. 

 

 


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • Aug 24, 2020 4:51 AM UTC

I suggest referencing the DEVELOPER link included previously.

Looks like there is an extra space before and maybe after the dynamic URL in the JSON.