Are you encoding your request body as a JSON object?

Hi,

With a console.log(httpOptions) :

body: {access_token: "my-access-token"}

In my Network I see a Request Payload

access_token: "my-access-token"

Which is the same one that I get when I create the token

Regards,

Hi. This has been an issue to me as well, I'm trying it out from https://developers.themoviedb.org/4/auth/delete-access-token and get the same message error. Could you figure it out @Araes ?

hi did any of you figure this out ??

I'm in the process of building a Delphi (Pascal) implementation of The Movie DB API. Here is the code I'm prototyping to DELETE a v4 Access Token:

procedure TFormJSONMain.ButtonMovieDB_V4AuthSessionIDClick(Sender: TObject);
var
  AHTTPResponse:TStringStream;
  HTTP:TNetHTTPClient;
  FUrl: string;
begin
  AHTTPResponse := TStringStream.Create;
  HTTP := TNetHTTPClient.Create(nil);
  try
    HTTP.Asynchronous := False;
    HTTP.ConnectionTimeout := 10000;
    HTTP.ResponseTimeout := 10000;
    HTTP.AllowCookies := True;
    HTTP.HandleRedirects := False;
    HTTP.UserAgent := 'Embarcadero URI Client/1.0';

    HTTP.ContentType := 'application/json;charset=utf-8';
    HTTP.AcceptLanguage := 'en-US';
    HTTP.CustomHeaders['Authorization'] := Format('Bearer %s', [MOVIEDB_API4_READ_ACCESS_TOKEN]);

    FUrl := CreateAccessTokenV4_URL+Format('&access_token=%s', [USER_ACCESS_TOKEN]);
    HTTP.Delete(FUrl, AHTTPResponse);
  finally
    HTTP.Free;
    AHTTPResponse.Free;
  end;
end;

Here is the JSON Response that I get from the above:

{
"status_code":37,
"status_message":"The requested session could not be found.",
"success":false
}

The TNetHTTPClient.Delete method only has the means to receive data, and not send anything, which is why I added the Access Token to FUrl. The MovieDB v4 API documentation isn't very clear as to how an access token is actually to be deleted

Hey guys,

I just pushed a small bugfix which should fix the issues you're seeing. If you need any more guidance, you can take a look at the following scripts. These are purely frontend HTML & JS so you can inspect the source code to see what's happening.

• http://dev.travisbell.com/play/v4_auth.html
• http://dev.travisbell.com/play/v4_auth_delete.html

Cheers.

@travisbell said:

Hey guys,

I just pushed a small bugfix which should fix the issues you're seeing. If you need any more guidance, you can take a look at the following scripts. These are purely frontend HTML & JS so you can inspect the source code to see what's happening.

• http://dev.travisbell.com/play/v4_auth.html
• http://dev.travisbell.com/play/v4_auth_delete.html

Cheers.

Thanks, Travis. I figured about as much that a fix was applied, because it started working as expected.

I still wish that there was a way using the v4 API to get a required Access Token in a similar manner that v3 can with Create Session with Login.