Api Interaction Diagram

Posted on by

APIs are the lifeblood of the web, pumping precious JSON to all of its distal servers. If you want your application to be a good, upstanding web citizen, you'll probably want it to associate with a few APIs. Your apps can't do everything themselves, you need to focus on what sets your app apart while delegating to other tools and services (often web APIs) when expedient.

  1. Api Interaction Diagram Tutorial
  2. Uml Interaction Diagram Example
  3. Api Interaction Diagram Tool

The sequence diagram is used primarily to show the interactions between objects in the sequential order that those interactions occur. Much like the class diagram, developers typically think sequence diagrams were meant exclusively for them. Understanding the interaction of process maps is key to the Process Approach. Companies typically have some type of flow diagram or map showing their interaction of processes. This is the most common method to demonstrate compliance with the process requirements in ISO 9001:2015 clause 4.4 or any of the other aerospace, automotive,. OOAD Interaction Diagram 2. Interaction Diagram. From the name Interaction it is clear that the diagram is used to describe some type of interactions among the different elements in the model. Interaction diagrams are models that describe how a group of objects interact / collaborate in some behavior - typically a single use-case. Interaction diagrams: Includes communication, sequence, timing, and interaction overview diagrams. These are a subset of behavior diagrams and describe the control flow between different components of the system. Not every diagram must be used during the development of a system.

Users can benefit from the versatile interaction capabilities of the library that allow them to easily create, edit, and handle diagrams with simple mouse, keyboard, and touch gestures. It also provides built-in support for fundamental interaction operations like zooming and panning, undo/redo, etc.

APIs are just interfaces that applications share so that your code can talk to theirs (in one important sense, any public method is an API), but what we're talking about here are third-party, HTTP-based services where you can request data from remote servers and get it packaged up the way you want for your own use.

We'll focus on the practical here because our goal is to get you on the right foot to perform more complex API integrations.


Almost all APIs will require you to register yourself and your application with the API provider. This allows them to track and monitor your usage.

There is typically a free tier of usage, and it will cost you if you're going over your limits. These limits are expressed in terms of total MB downloaded, number of requests, or number of transactions (for instance).

S3 storage and request pricing:

Usually, even if you're a user of the API provider's consumer-facing service, you will need to separately go to their developer portal and set up a developer account.

When you set up your account, you'll get an API key. This key uniquely identifies your application to the API provider, and you will usually send it along with every request. You'll typically also get a 'secret key' or something that functions like one. Whereas the API key is usually public, the secret key is an added layer of security that's required for the more secure APIs.

When authenticating with secure APIs, the secret key is used to generate a cryptographic token that authenticates any requests you make. While it doesn't matter much for the first assignment, in the future you will need to make sure you don't include this secret key in your Git repo! There are various approaches using libraries and environment variables you will later learn to keep that precious API key out of other people's hands.

Types of API Requests

Most APIs require a different type of 'security clearance' for different categories of requests. We'll cover a few of the more common high-level use cases here and what's involved with each.

Simple GET Requests

You can usually make innocuous requests (like asking Twitter for a few Tweets) with straightforward and unauthenticated GET requests. You can make these from any app, the command line or a browser tool like Chrome's Rest Client. These types of API requests are usually severely rate limited to incentivize you to sign up.

These requests are often behind the scenes when you make embedded API calls, for instance when you see a website displaying Tweets inside their posts. These hit the Twitter API, but aren't really considered traditional API calls and don't usually subject the hosting site to rate limitation.

API Key Requests

The next layer of complexity is making requests that include your API key. Some APIs require this for every request, while others allow you to use the previously-mentioned simple GET requests anonymously. Often, they'll allow very targeted GET requests (e.g. pulling a single photo or listing a user's Photo IDs) to pass anonymously but require that anything more complex (e.g. batches of photos or a full index of photos) be key-authenticated.

The whole point of using the API key is so the provider can link you to your usage, so expect these kinds of requests to be limited by the API's rate and sometimes pricing tiers. This also allows the provider to enforce their Terms of Use so you don't go building a competitive site based on their data.

CRUD-dy Requests

CRUD (Create/Read/Update/Destroy) operations that involve anything beyond simple READs will require a more advanced form of authentication. Usually, instead of just submitting single one-off requests like before, you'll need to authenticate each request individually. We'll cover this more during later lessons, but essentially you negotiate with the API provider and create a temporary access token based on your secret key. That token is used to validate the request before it goes through.

Obviously, these requests are subject to their rate and pricing tiers.

Requests on Behalf of Users

Applications aren't always just mindlessly pulling and pushing data. A use case that has greatly expanded over the past several years is making requests on behalf of a User. You've seen this if you've ever clicked 'ok' on 'Allow this application to make requests on our behalf' or 'Allow this application to post to your Facebook timeline' or 'This application requests access to your contact list' form.

In all of these cases, your application negotiates with the API provider (e.g. Facebook or Google) so it can submit requests on behalf of the user. This starts when the user successfully authenticates with the API (e.g. signs in with their Facebook account). When that happens, your app is given an access token specifically for that User. You can use that token (along with your own secret key) to make requests on that user's behalf.

These requests will often fall under a different usage tier (e.g. a per-user tier) instead of being bucketed along with your normal application. If you can imagine, a large consumer app serving as a middleman for millions of Photos or Tweets or Posts wouldn't be viable if their API usage was all bucketed to the application provider. By spreading it out on a per-user basis, developers have a much greater flexibility to use these APIs in a widespread fashion.

'Sign In with Facebook' Authentication

Many applications have skipped implementing sign-ups of their own and instead rely on their users authenticating using third-party services like Facebook or Google or Github. You've no doubt seen these in the form of 'Sign up with Facebook' buttons. The whole idea is that the user only needs to remember their Facebook password and doesn't have to entrust your application with it.

When you click here..

..it connects via 'OAuth' to Facebook:

You can consider this a special case of the previous example. The basic flow is essentially the same — the user signs in with Facebook and then Facebook provides you with an access token for that user. Your authentication system will then essentially use this authentication token in place of a user password. When the user needs to sign in again, Facebook will ask for their password again and provide you with the token. If the user is already signed in with Facebook in their browser, this is often a one-click process.

Front End vs Back End APIs

APIs don't ultimately care whether you are querying them from deep within your Express app or by using JavaScript code in the browser. Certain types of requests should only be made from the server because they involve passing secure data around. Many APIs are accessed from the backend for this reason.

In this section, we're focusing on the back-end code you already know, but be aware that front-end JavaScript has its own set of approaches to accessing APIs and is a fast-maturing field. We will return to this when you get to the appropriate units.

API Restrictions

Every site, in addition to rate limiting their API, will have terms of use. This usually covers what you're allowed to do with the data you gather. For instance, they probably aren't going to allow you to store a whole bunch of their data in your own database (harvesting). They also probably won't allow you to do anything SPAMmy or which will hurt their user's experience (posting constantly to their Facebook). Common sense should be your initial guide, but consult the TOU documentation for specifics. Basically, if you'll be hurting their user's experience or taking their precious data, you can't do it.

It should be noted that any time you develop using someone else's API, you're putting yourself at their mercy. If you're using it to the point where you pay for data, they'll love you. If you get too successful and become competitive with them, they've got you by the neck and will cut you off or demand exorbitant fees. Just be cognizant of those long-term risks.


Your first step after deciding to integrate with an API is to read through their documentation. It will (if it's decent) tell you everything you need to know about how to set up your account, how to authenticate, and what methods are available to you.

Reading through API docs is a crucial skill for a web developer, so we're going to leave you some leeway here to really figure this stuff out.


We've also discussed versions before but it's worth noting again — many APIs have gone through several versions so make sure you're referencing the correct documentation. Blog posts or Stack Overflow posts may also reference the older version, so check the date and be a bit suspicious of everything you read.

You can see the version (2.2), for instance, in the URL for this call to Stack Overflow's API:

API Data

You often have a choice of which type of data to return from an API. The de-facto standard these days is JSON, so you'll commonly see JSON APIs. These are usually RESTful, which means that for a particular resource (like a Tweet) you'll have structured ways to ask for particular pieces of data or collections of data (like all Tweets from you in the last 3 days) back. They might also directly return JavaScript objects, XML objects, or (between web services) SOAP objects. In any case, you or the library you're using will need to deserialize these objects to make them useful.

Handling the Response Object

Let's say you've made a request to a third-party API. Now what?

You've officially interfaced with the Wild West, and any number of things could happen. This is where your nice, neat, perfectly executing web app has to start handling the reality of dealing with network requests.

The request might have timed out. Or your API key may be expired. Or you might get back a strange error ('Oh sorry, the callback you specified doesn't match the domain you're on..'), or the response could contain partial data, etc. Unfortunately, your user doesn't care about this potential variability. You'll need to build logic which can handle all possible outcomes from these APIs.

If connecting to and authenticating with the API is the first pain-in-the-butt (PITA) problem, handling all the possible outcomes of this connection is definitely the second. We'll cover some things here, but this is one of those areas where you'll often just need to go plunging through error messages to diagnose the issue.

'Sandbox' Connections

Many of the more established APIs will provide you with a 'Sandbox' environment that you can make development requests of. It can be useful for avoiding real user data while you're developing. Sometimes these can be as much of a pain to connect to as the production area, so your mileage may vary.

Wrapping Up

Hopefully, this high-level API overview has you thinking about all the right components so we can begin diving into actual API use cases. We'll cover some simple ways to access web APIs in pure JavaScript. You'll definitely get a good taste of the range of ways that APIs can be both useful and challenging.

In addition to the API documentation, the following documentation topics are provided to explain concepts and help get started using the Web Service API more quickly and easily.


The Releases section includes highlights of the ICWS API for each release of the Interaction Center on which it is supported. This includes features that have been added, improved, and changed as well as the supported feature versions for each release.

2020 R4

Details the release of ICWS for the 2020 R4 release of the Interaction Center.

2020 R3

Details the release of ICWS for the 2020 R3 release of the Interaction Center.

2020 R2

Details the release of ICWS for the 2020 R2 release of the Interaction Center.

2020 R1

Details the release of ICWS for the 2020 R1 release of the Interaction Center.

2019 R4

Details the release of ICWS for the 2019 R4 release of the Interaction Center.

2019 R3

Details the release of ICWS for the 2019 R3 release of the Interaction Center.

2019 R2

Details the release of ICWS for the 2019 R2 release of the Interaction Center.

2019 R1

Details the release of ICWS for the 2019 R1 release of the Interaction Center.

2018 R5

Details the release of ICWS for the 2018 R5 release of the Interaction Center.

2018 R4

Details the release of ICWS for the 2018 R4 release of the Interaction Center.

Api Interaction Diagram Tutorial

2018 R3

Details the release of ICWS for the 2018 R3 release of the Interaction Center.

2018 R2

Details the release of ICWS for the 2018 R2 release of the Interaction Center.

2018 R1

Details the release of ICWS for the 2018 R1 release of the Interaction Center.

2017 R4

Details the release of ICWS for the 2017 R4 release of the Interaction Center.

2017 R3

Details the release of ICWS for the 2017 R3 release of the Interaction Center.

2017 R2

Details the release of ICWS for the 2017 R2 release of the Interaction Center.

2017 R1

Details the release of ICWS for the 2017 R1 release of the Interaction Center.

2016 R4

Details the release of ICWS for the 2016 R4 release of the Interaction Center.

2016 R3

Details the release of ICWS for the 2016 R3 release of the Interaction Center.

Uml Interaction Diagram Example

2016 R2

Details the release of ICWS for the 2016 R2 release of the Interaction Center.

2016 R1

Details the release of ICWS for the 2016 R1 release of the Interaction Center.

2015 R4

Details the release of ICWS for the 2015 R4 release of the Interaction Center.

2015 R3

Details the release of ICWS for the 2015 R3 release of the Interaction Center.

2015 R2

Details the release of ICWS for the 2015 R2 release of the Interaction Center.

2015 R1

Details the release of ICWS for the 2015 R1 release of the Interaction Center.

4.0 SU 6

Details the initial release of ICWS for the 4.0 SU 6 release of the Interaction Center.

Getting Started

The Getting Started section includes documentation on some key areas of the ICWS API, such as overview information and examples for common use cases. It can be challenging for a new developer to determine where to get started with the elements of a namespace.

These topics are meant to 'jump start' that effort, providing some important aspects to be aware of for a particular API area. Additionally, by providing focused example snippets around common tasks, these topics provide quicker understanding of what's possible and how to make those possibilities into reality. Then, the more full-featured example applications extend the core concepts and API usages into the context of developing real applications that allow users to perform larger tasks.

Making Requests

In order to work with the ICWS API, consumer code must make requests to retrieve data or perform operations.


This topic describes how to get started with connecting to an IC server.

Event Subscriptions and Messaging

The ICWS API provides access to real time information, including support for subscribing for changes that are delivered as 'messages' to the API consumer.

Language-specific Libraries

The ICWS SDK includes helper libraries to simplify common API usages in several languages, including JavaScript, C#, Objective-C, and others.

JavaScript Language-Specific Library

Explains the JavaScript Language-Specific Library and how to get started using it.

Objective-C Language-Specific Library

Explains the Objective-C Language-Specific Library and how to get started using it.

Api Interaction Diagram Tool

C# Language-Specific Library

Explains the C# Language-Specific Library and how to get started using it.

Example Applications

The ICWS SDK includes example applications that demonstrate usage of various parts of the API for 3rd party developers. These example applications are implemented using various technologies, to provide examples for a wider variety of languages.

Going Further

Explains some more advanced usage scenarios, with details and examples of how to get started with them. This includes topics such as getting/setting configuration values for the Interaction Center server, working with Interactions and Queues, monitoring statistics and alerts, and details about the available information in the statistics catalog.


Discusses concepts and provides examples of getting and setting configuration information for the Interaction Center server. This includes retrieving settings for Users, Roles, Workgroups, and so on and support for administrative integrations to configure those objects.


Discusses concepts and provides examples of managing directories for the Interaction Center server. This includes managing subscriptions for directory metadata, directories, as well as performing directory lookups via the directory lookup entries API.

Interactions and Queues

Details how to work with Interactions and Queues. This includes initiating and monitoring Calls, Chats, Emails, etc. and Queues of those interactions.

Statistics and Alerts

ICWS provides access to real-time statistics for the Interaction Center server. It also provides support for creating and monitoring for alerts on those statistics.

The Statistics Catalog

The Statistics namespace does not include an API element for each available statistic. Instead, it is 'metadata based', where the catalog of available statistics can be retrieved from the IC server through the ICWS statistics API. The statistics catalog contains the display name, description, type, units, required statistic parameters (if any), etc. for each available statistic.

Interaction Dialer

Contains supplemental information useful in understanding the Interaction Dialer-specific resource methods, responses, and event messages.

IPA Product Information

Contains supplemental information useful in understanding the IPA-specific resource methods, responses and event messages.

IPA Resource Paths

Contains links to various parts of the ICWS API that related to IPA.

IPA Page and Data Definitions File

Provides details about the file that contains the page definition and data definitions.

Communicating with Handlers

This topic discusses concepts and provides examples of communicating with handlers published on the Interaction Center server.


The Concepts section includes documentation on some fundamental concepts which are common to many different areas of the ICWS API. Some concepts are simple, while others contain nuances that can trip up developers. These topics strive to clarify these general points, providing conceptual context for utilizing elements throughout the ICWS API.

Learn how to create an informative speech that will provide your audience with new knowledge regarding a given topic. Informative speech outlines for free.

Design Principles

Discusses some of the ICWS API design principles and protocol details, such as date / time formatting and support for enumerations.

Representation Object Format

Details the format for representation objects, including advanced cases such as derived complex types and dictionaries.

Api Interaction Diagram
Documentation Conventions

Explains the conventions used in the ICWS API documentation and provides tips for how to read it. Also explains how to interpret the associated JSON that the web service consumer code would use.


Describes ICWS API security concepts and best practices.

Web Proxies

Explains how to utilize the ICWS API with reverse proxies.


Over time, the ICWS API will be extended with additional API elements. As this occurs, newer API consumers might need to work with versioning in order to correctly operate against older Interaction Center servers that do not have support for the newer API. This section describes how to work with versioning and how to read the ICWS API documentation to determine the required version for a specified API element.

Coverage of IceLib APIs

Describes the coverage of IceLib APIs that is provided by the ICWS API. Custom application developers can use this information when planning a migration from an IceLib-based application to an ICWS-based one.