IBM Targetprocess

Hello TargetProcess team/community,

We are working on integrating with TargetProcess to support OKR functionality, but we’ve hit a critical documentation gap regarding Extendable Domain (ExD) entities. Specifically, OKRs (Objectives and Key Results) appear to be implemented as ExD items, and we haven’t been able to find definitive API documentation for them.

Could you please help clarify the following?

1. API Endpoints for OKR ExD entities once the solution is installed:

   • Objective entity endpoint(s)

   • Key Result entity endpoint

   • Any hierarchy-specific endpoints (Ultimate/Strategic/Tactical Objectives)

2. • Required vs. optional fields

   • Field data types and formats

   • Relationship field structures

     Field Specifications for these entities:

3. • Is there a way to programmatically discover ExD entity schemas?

   • Is configuration-specific API documentation accessible via a meta endpoint?

     Discoverability of ExD Entities:

4. • Do you have JavaScript code samples or best practices for setting up automation rules to trigger HTTP POSTs when relationships are added or updated (as a replacement for deprecated webhooks)?

     Automation Rules for Notifications:

For reference, our provisional API patterns are based on the standard POST /api/v1/[EntityName] and POST /api/v1/[EntityName]/[EntityId] approach, but we need confirmation of the correct entity names and field structures before we proceed.

Any documentation, examples, or guidance you can share would be greatly appreciated.

Thanks in advance!