So now we've talked about the north and southbound APIs.
And if you're following along, intending
to go for the score exam, you may
be thinking to yourself, wait, east and westbound,
those aren't even on the blueprint.
But here's the kicker.
East and westbound, in my opinion,
is where the real magic happens.
In fact, the API that we're about to talk about--
the eastbound API is by far my most favorite one to work with,
and the one that I end up writing the most code for.
But what we're talking about now is integrating our application, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
integrating our network in with other applications.
This is going to be really, really cool.
Trust me.
By the end of this night, you're going to go,
there is a lot of possibilities right there.
Let's have some fun talking about the eastbound API.
Let's go.
Now the eastbound API, like I said before, this really
is the fun one.
This is where you get to have some real fun.
I'm going to clean up the screen a little bit here.
Let me erase some space.
We do need to leave some of this information here.
Let me just release this.
Because now we need some more space
to go in the eastbound direction.
And for this, I'm going to use the color green. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And for this, I'm going to use the color green.
So in the eastbound direction, we're
now sending data out of our software defined networking
solution because we want to integrate this network
with another application.
One of the best scenarios to use this is when a alert comes up.
Something bad or something critical
happens within Firepower Management Center.
Maybe while it was trying to push a southbound configuration
change, one of the devices went offline and the configuration
failed.
That would obviously create an error and an alert, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
That would obviously create an error and an alert,
and we would want to be notified by it.
So consider for a moment now that maybe you're
on vacation on a beach in Hawaii,
and you don't want to be notified
by anything first of all.
But you have your phone on you, and it's
ready to receive alerts.
Maybe you use a tool like Slack, or Microsoft
Teams, or of course, in the Cisco platform,
there is WebEx Teams.
Whatever the case may be, when an alert occurs,
we can send this data-- this alert data
in the eastbound direction out to other applications WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
in the eastbound direction out to other applications
or other platforms.
This could even be something as simple as a database.
So that's really the key to the eastbound API,
and this is where really starts to come into the situation.
Is that we can now integrate applications
that weren't necessarily designed to talk to each other.
We can now make them talk to each other.
Because at the end of the day, it's just an API.
We're just sending data from one application to the next.
And these tools like Slack, MS Teams, or WebEx Teams, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And these tools like Slack, MS Teams, or WebEx Teams,
they have APIs that are ready to receive this data.
They have tools that are ready to receive information.
So we can absolutely tell it, hey, when an alert occurs,
send it to this endpoint here with
these additional parameters.
That way it can say things like this message
needs to go into this specific Slack channel.
That way everybody who's on call gets
alerted to what's happened.
And don't stop with just ChatOps here.
Think about the Cloud.
Think about ways that we can ingest data WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Think about ways that we can ingest data
into other applications.
Think about ways that we could really work
with this type of alert data.
That's what the eastbound API is.
The eastbound API is limited to your imagination
because this guy--
Firepower Management Center has this data.
What do you want to do with it, that's
what the eastbound API does, and that's
why it's my favorite API.
So that's been setting up what the eastbound API is.
In the next slide, we're going to wrap this up,
talking about the westbound API.
I hope this has been informative for you, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I hope this has been informative for you,
and I'd like to thank you for viewing.