There is no replacement planned for this endpoint. To create a source schema, you will need to either manually build the schema in the user interface or use the create schema API to upload a schema.
Would be nice if it gets back later. In my opinion everything a developer should be able to do with the UI should be do-able via API. Assuming the discover schema operation through the UI stays supported.
Discover Schema isn’t the same as Create Schema.
We used it to find the target attributes directly instead of having to manually create them one by one by looking at the connector/target source.
Is there any plan to work on it later, past the March 31 deadline?
I added an idea here: https://ideas.sailpoint.com/ideas/GOV-I-3270
happy to edit/clarify.
2 Likes
This endpoint was previously in progress, but due to high priority items there will not be a replacement available before March 31st.
What is the API replacement for this deprecated API?
How can we still use the API to discover the schema?
And will this only involve account schema or also entitlement schemas?
Any update on the replacement API for this end point?
It’s in the backlog. I will move this to the deprecated column once a replacement is public.
2 Likes
Is this one the same as POST https://tenant.api.identitynow-demo.com/diana/sources/schema/:id/discoverSchema ?
I assume we don’t have a replacement for either of these discover schema APIs yet.