adt-api-discovery

Investigate SAP ADT REST API endpoints to determine HTTP contracts and XML formats.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/LeON-W666/ABAP-Remote-FS-for-Codex --skill adt-api-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adt-api-discovery
Source: https://github.com/LeON-W666/ABAP-Remote-FS-for-Codex/tree/main/client/media/skills/adt-api-discovery
Command: npx skills add https://github.com/LeON-W666/ABAP-Remote-FS-for-Codex --skill adt-api-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you determine the exact HTTP contract for SAP ADT REST endpoints, including URL patterns, supported methods, and the precise XML request/response formats and content types.

Core Features & Use Cases

  • Discover endpoint wiring from discovery documents: Trace from discovery workspace files to the RES_APP class that registers resources and templates.
  • Resolve handler behavior and HTTP methods: Inspect handler classes to see which methods (GET/POST/PUT/DELETE) are actually supported.
  • Derive request/response XML schemas from Simple Transformations: Follow content handler factory usage to the Simple Transformation sources that define the XML structure and required XML namespaces.
  • Use case: When documentation is unclear for an ADT feature, you can identify the correct endpoint and content type version, then generate or validate matching XML payloads by reading the underlying transformations.

Quick Start

Ask: Investigate the SAP ADT REST endpoint for the ADT feature "[what ADT endpoint or feature to investigate]" and provide the full URL, supported HTTP methods, required content types, and the request/response XML structure derived from the relevant Simple Transformations.

Frequently Asked Questions about adt-api-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the exact HTTP contract for an SAP ADT REST API endpoint?

To find the SAP ADT REST API HTTP contract, you investigate discovery documents to trace RES_APP registrations, inspect handler class methods, and derive request/response XML schemas from Simple Transformations to get the full URL, methods, and content types.

How can I reverse-engineer undocumented ADT REST API behaviors when documentation is unclear?

You can reverse-engineer undocumented ADT REST API behaviors by inspecting ABAP source code across RES_APP registrations, handler class method overrides, and content-type constants to determine the exact supported HTTP methods and payload formats.

How do I derive the XML request and response schema for an SAP ADT endpoint?

To derive the XML request and response schema for an SAP ADT endpoint, follow content handler factory usage to the Simple Transformation sources, which define the required XML structure and namespaces for the API payloads.

What do I need to determine the supported HTTP methods and content types for an ADT feature?

To determine supported HTTP methods and content types for an ADT feature, you need prior export discovery outputs and must perform ABAP source inspection on handler classes and content handler factory constants.

Can I generate valid client payloads for specific SAP ADT features using Simple Transformations?

Yes, you can generate valid client payloads for specific SAP ADT features by reading the underlying Simple Transformations to identify the correct endpoint, content type version, and required XML structure.

Why does my ADT REST API request fail with an incorrect content type?

ADT REST API requests fail with incorrect content types when the payload does not match the XML structure and namespaces defined in the Simple Transformation sources, which you can verify by inspecting handler content-type constants.