For Application Development & Delivery Professionals

API Design, Part 3: Make Transactions And Error Handling Clear In Your API Designs

Ensure That Your Choice Of Messaging Style Does Not Interfere With The Design Clarity Of Your API

    Why Read This Report

    To fully exploit the business opportunity available through application programming interfaces (APIs), your designers must consider each API's purpose and audience as they answer a wide range of technical design questions. Beyond choice of messaging type (e.g., REST and SOAP), it's important to foster API acceptance by ensuring that your designers know how to meet an API's functional requirements with clear designs that appropriately consider the nuances of transaction processing, error handling, and related concerns. As part of a series on API design practices, this report examines best practices for ensuring that detailed API designs are readily understandable and support robust solutions.
    US $ 499
    Become A Client

    Get objective, pragmatic guidance that helps you make tough decisions and succeed in a complex world. Contact us to learn more.

    Already A Client?
    Log in to read this document.

    TABLE OF CONTENTS

    • Let Business Opportunity Drive Technical Design Of Your APIs
    • Ensure You Reach All Your API Design Goals Through Design Clarity
    • RECOMMENDATIONS

      Use Your API Design Strategy To Meet Your Design Goals With Clarity
    • Supplemental Material
    • Related Research Documents