Quick question for teams here 
How do you handle API collaboration when the backend isn’t ready yet?
I’ve tried using mock servers with Swagger, but it’s clunky.Would love to know if there’s a smoother way.
1 Like
Hi Iuc,
Excellent question. Manually keeping mocks in sync is indeed clunky and prone to error.
Maybe your team can shift from simple mocking to CCD (Contract-Driven Development) approach.
As I understand the basic idea is instead of the backend team building an API and then “throwing it over the wall”, agree on an API contract first. This contract is a formal description of the API where everything is defined: endpoints, requests, responses, data schemas, status codes, authentication methods, etc.
Now instead of manually creating mock data, you use tools that generate dynamic mock server from the .yaml or .json API contract file.
Stoplight Prism or Postman can help you achieve this.
How This Applies Directly to Your SailPoint ISC Use Case?
This is a perfect scenario for developing a WebService Connector. Configure, develop and test(Test Connection, Account Aggregation, Entitlement Aggregation, Create Account) within ISC. ISC will send its API calls to your mock server, which will respond with the exact data you defined in the contract.
This allows you to work on your connector’s configuration without waiting for the backend system to be available.
Note: Contract testing is required to prevent “drift” where the real backend implementation mismatches the contract. There are tools for that as well I believe.
Good luck
1 Like
For me I think that Apidog is good for that, since it includes mock APIs and auto‑generated docs.
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.