The Complete API Development Guide

  1. Design the API

    1. Analyze business requirements

    2. Identify affordances

      e.g.: Create user, Submit order, Search for an article

    3. Identify resources

      e.g.: User, Order, Article

    4. Identify relations

      e.g.: User has many Orders via order relation, all of the required affordances should be mapped to relations.

    5. Formalize the design in the Open API Specification (OAS, formerly known as "Swagger") format

    6. Follow the adidas API guidelines

    7. Put the OAS file into Apiary adidas group

    8. Make sure the OAS file passes all adidas API Apiary style guide checks

    9. Verify the design using Apiary Documentation and Apiary Mock Service

    10. Review the API Design

    11. Put the OAS file in a version control system (VCS) repository

    12. Set up a CD pipeline to push OAS file from VCS to Apiary, whenever the file is changed

  2. Develop the API

    1. Check out the VCS repository with the OAS file

    2. Set up the Dredd API testing tool locally

    3. Configure the Dredd for your project

       $ dredd init
    4. Run the Dredd test locally

      Against locally running API implementation, Every test should fail.

    5. Implement the API

      Keep running the Dredd locally to see the progress.

    6. Set up a CI/CD pipeline to execute the Dredd tests automatically

      NOTE: Both TeamCity and Jenkins environments are available, contact adidas API evangelist for details.

  3. Deploy the API

    1. Deploy the service

    2. Update the OAS file to add the deployment HOST

      basePath: /demo-approval-api
    3. Verify the deployment with Dredd

      Use Dredd pointed towards the deployment host, be careful NOT to run it against the production OR using real production credentials.

    4. Monitor the API usage "From performance and technical standpoint."

  4. Expose the API using Mashery

    1. API

      1. Create new API Definition in Mashery

      2. Create a new API Endpoint the API Definition

        Set the "Your Endpoint Address" to the internal deployment HOST.

      3. Create a new API Package in Mashery

      4. Create a new API Plan within the API Package

      5. Use Mashery API Designer to add the newly created API Definitions' API Endpoint to the API Plan

      6. Revisit the API Plan's API key default settings

      7. Revisit the API Plan's API default rate limits

      8. Revisit the API Plan's access policy/authorization

      1. API Documentation

        1. Create new adidas API developer's portal page in the Mashery

          Manage > Content > Documentation > APIs

        2. Embed Apiary documentation on the newly created API Page

        3. Revisit the API documentation access policy/authorization

  5. Use the API

    This step can be done at the same time as "Develop the API" thank Apiary hosted Mock, Inspector, and Documentation.

    1. Read API documentation at Apiary

    2. Use API mock service provided by Apiary

    3. Use API call inspector provided by Apiary

    4. Obtain your API key

      The key is part of the API Plan created in Mashery and can be requested from your dashboard in the adidas API developer's portal.

    5. When available use API implementation via Apiary proxy to debug the API calls

    6. Use production deployment

  6. Analyze the API

    1. Examine the use of production API Using Mashery

    2. Analyze the technical performance metrics

    3. Collect the feedback from users

  7. Update API Design

    Based on the analysis, new or changing business requirements

    1. Create a new branch in the VCS repository with OAS file

    2. Create a new project (alternative) in Apiary

    3. Make sure the CI/CD pipeline is:

      1. Set to push the OAS file to Apiary but make sure to modify the Apiary project name

      2. Set to run Dredd test in the CI/CD

    4. Modify the design (OAS file) accordingly, follow the "Design API" step

    5. Follow the rules for extending and adidas API guidelines versioning policies

    6. Use VCS pull request (PR) to propose the change to review

    7. After the API Design change is verified, reviewed and approved, continue with the "Develop the API" phase

    8. Eventually, when the updated design is ready to be deployed for production, merge the branch into the production branch

    9. Follow this guide from "Expose the API using Mashery" step

results matching ""

    No results matching ""