When Does It Make Sense to Move Beyond Postman for ServiceNow APIs?

[Erics37]

Postman is still a solid choice for testing ServiceNow REST APIs. But as API workflows become more integrated with CI/CD and team collaboration, I’ve started wondering whether an API client alone is enough.

For larger API projects, we also need to:

• Run API tests automatically
• Manage different environments
• Reuse test scenarios in CI/CD
• Keep API documentation updated
• Collaborate between developers and QA
• Handle API design and testing in the same workflow

That’s what led me to look at Apidog as a possible Postman alternative.

What I find interesting is that it combines API design, documentation, testing, mocking, and automation instead of requiring separate tools for each part of the workflow.

I’m curious how other ServiceNow developers approach this.

Are you still using Postman for ServiceNow API testing?

Have you tried alternatives like Apidog, Insomnia, or Bruno?

And when your API testing becomes part of CI/CD, what tool or workflow has worked best for you?

[boteeuwen]

For ServiceNow API work, I think the tool matters less once the tests become part of CI/CD. At that point, having the API tests stored in Git and being able to run them from a CLI becomes much more important.

Bruno is interesting for that reason because the collections are easy to version alongside the project. Apidog makes more sense when API design, mocking and documentation are also part of the same workflow. I’d still keep ATF in the picture for ServiceNow specific regression testing rather than trying to move everything into an external API tool.