# Shotgun\_api3 authentication

**URL:** <https://community.shotgridsoftware.com/t/shotgun-api3-authentication/12328>\
**Category:** Pipeline Integrations\
**Created:** [May 6, 2021, 3:58pm UTC](https://community.shotgridsoftware.com/t/shotgun-api3-authentication/12328 "2021-05-06T15:58:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dietmar.kreider](https://avatars.discourse-cdn.com/v4/letter/d/90ced4/32.png) [@dietmar.kreider](https://community.shotgridsoftware.com/u/dietmar.kreider)\
**Post date:** [May 6, 2021, 3:58pm UTC](https://community.shotgridsoftware.com/t/shotgun-api3-authentication/12328/1 "2021-05-06T15:58:21Z")

</div>

Hi, community!

While fiddling with `shotgun_api3` I found multiple ways to authenticate a user.  
`Shotgun()` class has arguments for a user login: `login` and `password`.  
And then there is a method called `Shotgun.authenticate_human_user()`, which requires an initialized `Shotgun` instance.

What’s the point for having both of them? Init `Shotgun` with an API-key and than “reauth” as user? Is the `authenticate_human_user()` method mandatory, or can I just stick to the ` __init__ ()` method?

So long DD
