Skip to main content
ChristinaZuniga
ChristinaZuniga
Level 9
Jan 10, 2017 9:37 PM UTC
Solved

Best Practices 1 or multiple API Accounts?

I'm building out integrations to my tech stack and a few of these companies want to connect via API users. So far I've created separate users and named them based on what part of the tech stack they relate to (ex: DOMO API user, Influitive API user, etc).

I have more integrations coming up and it seems like they all work the same way. In my CRM, we use 1 API user that connects onto many different integrations but that was originally due to pricing per user. In Marketo I can have lots of users without additional pricing. I was trying to keep these separate for auditing, but is it OK to just use 1 API user and connect to different technologies rather than 1 user per technology?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
SanfordWhiteman
SanfordWhitemanAccepted solution
User Group Leader
Jan 10, 2017 9:41 PM UTC

Always use dedicated API users. This is the only way you can audit & remove access.

View in thread

7 replies

SanfordWhiteman
User Group Leader
SanfordWhitemanUser Group LeaderAccepted solution
User Group Leader
Jan 10, 2017 9:41 PM UTC

Always use dedicated API users. This is the only way you can audit & remove access.

Translate
ChristinaZuniga
ChristinaZunigaAuthor
Level 9
Jan 10, 2017 9:45 PM UTC

How do you come up with other email addresses when IT doesn't want to deploy more? So far I've been using my old emails (since API users can't log in, it's secure after I leave), but now Gmail and Yahoo, etc. require phone numbers with new accounts. I just want a few throwaway ones...

Translate
SanfordWhiteman
User Group Leader
SanfordWhitemanUser Group Leader
User Group Leader
Jan 10, 2017 9:50 PM UTC

You can use Gmail submailboxes, e.g. czuniga+domo@gmail.com, czuniga+influitive@gmail.com.

Translate
    Terms & ConditionsAccessibility statement

    Loading footer...