API User Best Practices | Community
Skip to main content
Ric_Kolibar
Ric_Kolibar
New Participant
April 18, 2023
Solved

API User Best Practices

  • April 18, 2023
  • 1 reply
  • 1607 views

I'm looking at my API integrations and so far I've created separate users and named them based on what part of the tech stack they relate to (ex: Facebook API user, Knak API user, etc).

 

I have more integrations coming up and it seems like they all work the same way, that will make about 50. 

 

Marketo is charging for each user. 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?

In my CRM, we use 1 API user that connects onto many different integrations.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

1. Marketo shouldn’t be charging for API-only users. Push back on that if it’s being enforced.

2. You should definitely not be using one API user. It makes debugging absolute madness, and requires that you grant everybody the same permissions.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
April 18, 2023

1. Marketo shouldn’t be charging for API-only users. Push back on that if it’s being enforced.

2. You should definitely not be using one API user. It makes debugging absolute madness, and requires that you grant everybody the same permissions.

    Ric_Kolibar
    Ric_KolibarAuthor
    New Participant
    June 5, 2023

    Pushed back as best as I could, Marketo policy is to charge for every user API included

    ric kolibar
    Terms & ConditionsAccessibility statement

    Loading footer...