apic docs
  • About APIC
  • Installing APIC
  • Getting started with APIC
  • Designer
    • Getting Started With APIC designer
    • Working with API project
    • Creating a Folder
    • Creating a Model or Definitions
    • Creating a Trait
    • Creating an Endpoint
    • Write API Tests starting from Design Phase
    • API Security Definitions
    • Export and view Docs
  • Tester
    • Make an API call
    • Sending Forbidden request headers with APIC
    • Viewing API Response
    • Managing Environments
    • Using Environments
    • Using the Test Builder
    • Writing Test Cases
    • Response Schema validation
    • Creating Test Suites
    • Test Websocket
  • Test Real User Sessions
  • APIC Command line interface (apic-cli)
  • APIC Web Agent (apic-cli)
  • APIC CI/CD Integration (with Jenkins)
  • API Documentation
  • Simulator
  • Dashboard
    • Team Management
    • Published Docs
  • Sharing
Powered by GitBook
On this page
  • Endpoint fields
  • Example
  • What's next?

Was this helpful?

  1. Designer

Creating an Endpoint

PreviousCreating a TraitNextWrite API Tests starting from Design Phase

Last updated 5 years ago

Was this helpful?

Endpoints are your actual APIs or Paths as specified by Swagger.You can define your API endpoints in your project with request, response types, response schemas etc.

You can create an API Endpoint by clicking on the Endpoints option in your Project Home page which will open a view as shown below to fill in the details and create your Endpoint. You can specify http method, schemes, endpoint url, content type (Consumes, Produces), tags, summary, description, multiple response codes and their respective response schema as shown below.

You can import headers or query parameters or response code and their schema from a trait by selecting that trait in the traits field.

You can add a path parameter by putting that in the URL as /api/path/{para-param}. Now yo can specify the details of this path param under the path params section.

Endpoint fields

  • Name/Summary

  • Path

  • HTTP method

  • Folder

  • Operation Id

  • Consumes/produces: Eg: appication/json

  • Schemes

  • traits

  • tags

  • Description

  • Path parameters

  • Query parameters

  • Headers

  • Body

Example

Lets create 3 endpoints for our ToDo applicaion for creating ToDo, getting list of ToDo and getting detail of specific ToDo by its id. We can use path params for getting the ToDo detail by id. Our endpoint URL will look like /todo/{todoid}

What's next?

Well we have a basic design ready. Let's see how we can from this and with other developers.

Security
Responses
Pre/Post script
generate beautiful documentation
share