►
From YouTube: Intro to Taxonomy & Content Type REST APIs
Description
In this 16-minute demo, Microsoft SharePoint engineering managers - Ramesh Kasturi and Ravi Gopinath, deliver a developer focused preview of new SharePoint REST APIs for TermStore and Content Types services. 14 new Content Type REST APIs for creating content type columns, for publishing/unpublishing content types, and for setting doc templates on content types. The APIs support creating content types at site and at hub levels. Full CRUD operation (Create, Read, Update, Delete). Targeted ship date for the SharePoint REST APIs v2.1 and documentation is end of May, and related Graph APIs approximately one month later. This demo includes community discussion. This demo is extracted from the bi-weekly Microsoft 365 PnP community – General M365 Developer Special Interest Group (SIG) call recorded April 16, 2020.
Presenters: Ramesh Kasturi (Microsoft) | & Ravi Gopinath (Microsoft)
All SharePoint PnP Developer Community demos: https://www.youtube.com/playlist?list=PLR9nK3mnD-OWSbg0o9a7mx_E7s2u7h_o2
Learn more about the SharePoint developer community at: http://aka.ms/m365pnp
A
A
So
primarily
today
we
will
be
focusing
with
some
of
the
new
APA
support
that
we
are
bringing
into
both
these
services
and,
if
you
see
previously,
we
had
support
only
for
see
some
access
to
term
store
and
very
limited
contact,
ID
api's
that
were
previously
available
over
the
last
one
year
we
have
been
working
on
building.
Let's
take
a
access
to
the
taxonomy
term,
store
and
enterprise
content
items.
So
from
a
term
store
point
of
view
will
be
supporting
crud
operations
and
Poundstone.
A
Certain
term
groups
will
be
initially
supporting
most
of
the
properties
of
the
term
level
and
the
terms
that,
when
the
term
group
level
will
be
introducing
a
new
concept
of
relationships
to
support,
pinning
and
reuse
of
terms
and
I'll,
be
giving
a
quick
overview
of
some
of
these
in
the
following
slides
the
API
model.
Are
the
entities
in
the
term
store
are
groups
which
represent
the
term
group
sets
which
are
the
term
sets
and
terms
themselves,
and
each
of
them
have
an
ID
for
themselves
to
access
those
entities.
A
So
this
is
how
I'll
get
on
the
term
store.
Would
look
like
where
you
will
be
listing
all
the
term
groups
under
the
term
store.
It
will
return
you
the
first
level
list
of
term
row.
You
can
put
some
filters
and
do
pagination
also,
if
needed
on
this
one.
It
will
return
you,
the
ID
of
the
term
group,
the
description
of
the
term
group.
The
label
of
the
term
grew
and
some
additional
properties
like
type
of
the
town's
opposite,
a
regular
group.
Is
it
a
system,
town
group,
or
is
it
a
site,
collection,
town
group?
A
So
in
the
similar
way,
once
you
have
the
group
ID,
you
can
fetch
all
the
term
sets
under
that
group
and
at
the
term
set
level
it
will
return
you,
the
ID
of
the
terms
at
the
level
of
the
ID,
a
level
of
the
term
set.
What
are
the
different
translations
that
are
available
at
a
town
site
level,
and
you
can
further
drill
down
to
get
the
list
of
terms
under
that
particular
term
set
in
a
similar
fashion?
A
It
will
return
you
all
the
different
properties
of
the
terms
in
the
interest
of
time,
I'm
skipping
the
post
operations
for
most
of
this
I'm
just
listing
down
only
the
gate
operations
post
will
also
be
similar
for
this,
where
you
can
update
these
properties
or
change,
modify
these
properties.
So,
under
the
term
you
can
have
children
which
are
the
terms
that
are
created
under
a
given
term
and
the
numerating.
The
children
will
return
you
all
the
top-level
children
of
that
term.
A
You
can
further
drill
down
for
each
of
those
terms
to
get
the
descendant
3
for
Anita,
and
that
has
been
either
pinned
or
reused.
You
can
use
the
slash
relationships
operation
on
that
one
which
will
enumerate
where
all
is
this
particular
term
either
pinned
or
we
used-
and
we
also
support,
like
posting,
on
to
the
relationships
to
create
new
relationship
from
a
given
term
to
another
term
or
from
a
given
term
to
a
different
term
set.
So
that's
mostly
from
the
term
store
point
of
view.
B
You
yeah
so
content
types
there
haven't
been
any
reached
API.
So
far
there
was
only
one
duration,
API,
which
were
just
reached
the
content
type.
So
we
have
added
bunch
more
content
types
to
support
all
the
curtain
operation.
You
can
create
content
types
on
sites
or
at
least
level
remove
them
update,
delete
them.
You
can
also
create
content,
type
columns,
side
columns.
You
can
also
publish
and
publish
content
page
and
set
document
templates
on
content
types,
so
I'm
just
walking
you
through
couple
of
content,
type
examples
that
we
are
going
to
have.
B
For
example,
you
can
see
that
so
one
other
thing
that
I
would
like
to
mention
here
is
that,
instead
of
going
to
content
type
hub
and
creating
all
the
new
content
types
there
we
have.
Actually
we
are
actually
providing
new
UX
from
tenant
admin
wear
with
our
modern
UX
to
create
new
content
types.
So,
for
example,
you
can
create
a
new
content
type.
The
request
URL
would
be
of
this
type.
B
You
would
be
specifying
the
name
description,
the
group
to
which
the
content
type
needs
to
belong,
and
then
the
output
of
that
would
be
the
content
type
that
got
created
with
its
ID.
So,
similarly,
you
can
create
a
column,
also
a
sight
column
also
and
add
it
to
the
content
type.
So,
similarly,
you
can
create
a
sight
column
and
associated
by
a
content
type,
and
this
will
allow
you
to
create
content
types
of
either
a
content
type
of
level
or
at
a
specific
site
level.
So
the
API
supports
both
today.
B
So
these
are
just
a
few
of
the
api's
that
we
are
providing
shortly
so
like.
As
you
can
see,
you
can
list
all
the
content
types
at
the
site
level
or
at
a
particular
list
level.
You
can
update
content
types
at
a
particular
site
or
release
level,
but
you
can
delete
a
content
type
and
for
all
the
other
gates
at
the
bottom.
They
also
support
patch
and
delete.
You
can
publish
the
content
type,
you
can
add
columns,
remove
columns
from
the
content
type
you
can
reorder
columns
in
the
content
type.
B
C
Couch
we
have
plenty
of
time,
so,
let's
not
close
the
connection,
don't
don't
close,
sharing
it
and
let's
actually
go
back
just
recapping
things.
Let's
go
back
on
the
taxonomy
first
and
start
from
there
and
there's
good
set
of
questions,
and,
let's
recap,
because
not
all
of
the
people
can
see
the
chats.
So
will
it
support
setting
term
store
administrator
because
currently,
there's
no
API
for
that
when
I
think
Robbie
answered
on
the
chat
already
that
students
toward
the
new
API
does
support,
adding
the
store
administrator
in
the
in
the
store
so.
B
C
A
C
Yep-
and
that
was
Rob-
you
answered
on
that
one
as
well
now,
there's
a
there's,
a
good,
interesting
and
discussion
point,
and
let's
actually
do
that
right
away
in
here
and
then
talk
about
the
content
type
and
recap
some
of
those
things
as
well.
So
this
one
is
now
in
the
underscore
API
bv2
point
one.
C
If
we
have
a
look
on
the
URLs
and
that's
that's
actually
quite
important
to
realize
that
both
of
these
api
sets
are
in
the
underscore
API
v2
0.1
and
again
you
don't
want
to
do
you
kind
of
explain
for
the
audience.
What
does
it
mean
comparing
on
the
craft
API,
because
there
was
a
question
related
on
that
one
as
well?
Yes,.
A
C
Yeah,
that's
precisely
what
I
was
wanted
to
actually
get
from
you
as
well,
so
now
now
just
to
clarify
that
from
the
audience,
because
I,
obviously
Microsoft
internal
people
know
how
this
works,
but
just
to
clarify
for
those
who
are
on
this
call
and
do
not
understand
how
this
works
in
the
in
the
craft
perspective.
We're
not
going
to
duplicate
this
APRs
to
craft.
That's
not
what
it
means
and
the
graph
is
actually
an
abstraction
layer
or
a
wrapper
with
people
which
behind
if
the
scenes
are
actually
hitting
this
same
API.
C
C
C
Excellent
just
to
clarify
that
for
the
for
the
audience
as
well,
and
it's
good
to
understand
that
it
abstraction
layers
actually
work
and
dab.
Basically,
the
craft
is
an
abstraction
layer
which
then
provides
you,
the
unified
authentication
across
all
of
the
different
services
and
that's
an
applications,
one
who
have
in
much
the
greatest
file
and
and
other
things
as
well.
But
then,
behind
the
scenes,
the
specific
services
like
SharePoint
and
onedrive
owns
their
own
ABI,
including
the
graph
API.
C
Anything
which
you
want
to
add
on
that
one.
Or
should
we
talk
about
slightly
to
content
type
API
s'more?
Can
you
move
to
the
content
type?
Thank
you
by
the
way,
Ravi
for
being
super
active
on
the
chat.
That's
highly
helpful,
I'm
just
recapping
some
of
these
things,
because
not
all
of
the
people
can
say
that
Chet
always
now
they
will
say,
question
related.
Will
this
work
for
content
type,
hop
as
well
and
I?
C
Think
Robbie
you
answered
already
that,
yes,
you
can
create
content
types
in
a
Content
calm,
but
then
there's
a
follow-up
question
there,
which
I'm
not
sure
if
somebody
asks
it
already,
because
there's
so
many
things
happening
now
in
the
content
type
hub.
There's
this
feature
where
we
publish
the
content
types
to
the
site
collection.
Can
we
do
that
using
the
new
content
type
API
or
is
that
something
which
we're
still
planning
to
do
in
the
future?.
B
A
C
C
Excellent
excellent
and
then
there
was
did
I'm
just
double-checking.
That
was
the
content
type
question.
So
there
was
a
question.
Obviously
the
obvious
question:
when
is
this
out
when
I
come?
When
can
we
hit
this
API
is
right
now
it's
probably
not
yet
working
or
is
it
working
all
right
in
SharePoint
and
and
can
we
talk
about
any
timelines
or
is
it
too
early
for
that?
No.
A
I
think
we
can
talk
about
timelines.
We
are
looking
at
like
mid
to
end
of
me
for
some
of
this.
Yes,
we
available
and
I
mean
followed
by
the
graphic.
Yes,
so
I
think
there
was
a
question
on
the
documentation.
Also
I
think
like
once
a
aps
are
available
at
the
same
time,
we'll
make
the
documentation
also
available
for
this
one
yep.
C
And
that
will
mean
that
within
four
weeks,
so
this
is
preview
like
it
was
mentioned
in
Rama,
she's,
intro
page
as
well,
so
they're,
basically
an
introduction
on
what's
coming,
but
it's
very
important
that
partners
and
customers
do
know
beforehand
and
say
what's
coming
as
well,
so
you
don't
invest
for,
let's
say
a
wrong
API.
So
this
is
coming
and
like
set
ramp.
My
rubbish
plan
to
get
out
in
the
mid
May
and
then
right
about
the
same
time
frameworks
like
they
later.
The
graph
API
as
well
they're,
say
this
well
they're.
A
C
Yeah
and
end
of
q2
means
by
underbite
you
so
yeah
exactly
so
it's
not
a
massive
amount
of
time
so
one
month
later
or
four
weeks
time
but
I
think
it's
good
to
get.
Obviously
it
would
be
great
to
have
everything
ready
with
this
number
of
fingers
without
anybody
actually
working
on
and
using
a
tremendous
amount
of
resources
on
that,
but
if
we
can't
getting
something
out
first
in
the
in
the
v2
endpoint
and
then
through
the
craft
next
is
completely
understandable
as
well
and
I.
Think
everybody
will
be
super
happy
about
this
calendar.
A
C
C
Oh
that's!
A
good
corner
actually
come
buddy
Ravi
is
asking:
will
the
release
of
content-type
publishing
be
improved?
So
currently
it
takes
actually
quite
a
lot
of
time
to
get
the
content
by
prep
located
to
the
target
site
collection.
That's
a
really
good
question
actually
and
but
I
correct
me
if
I'm
wrong,
I'm,
just
assuming
I,
don't
have
to
fax,
but
this
is
using
the
existing
infrastructure
for
the
replication,
so
we're
basically
still
using
the
the
underlying
time
mature,
based
replication
of
the
content
times
cross
site
collection.
So
it's
not
correct.
Yes,.
B
We
are
using
the
existing
infrastructure
itself,
but
we
do
hear
the
pain.
We
know
that
multiple
customers
are
facing
the
issue
of
content
type,
sync,
taking
a
long
time
for
them
for
these
content
types
to
reach
the
sides
once
they
are
published,
we
are
seriously
looking
into
it
and
we
will
make
we
you
know,
because
we
are
looking
into
it
and
trying
to
make
sure
that
we
could
improve
the
performance.
We
are
aware
of
the
problem
and
we
are
looking
into
it.
Yeah.
C
C
So,
and
this
means
that,
as
part
of
the
as
an
example
classic
journalist
being
that's
going
to
create
a
new
site
collection,
those
content
types
are
not
immediately
available
in
that
size,
collection
it
takes
a
while
and
to
get
them
there
and
there's
multiple
ways
of
addressing
and
fixing
that
what
we
need
to
still
work
on
that
one
in
a
micro
design.
But
we
we
want
that,
and
we
are
aware
of
this
issue
and
that's
that's
good
example
of
a
really
powerful
and
an
important
feedback
which
we
want
from
the
community
and
so
keep
on.
C
You
need
to
keep
on
reminding
us
and
we
need
to
be
honest
on
our.
What
are
we
delivering
so
again?
Recapping,
the
the
v2
endpoint
API,
which
is
the
shipment
endpoint,
a
REST
API
coming
around
and
meet
the
may
or
end
of
May,
and
then
the
craft
API
is
which,
based
on
exactly
the
same
taxonomy,
which
are
saying,
for
example,
in
the
screen,
is
coming
then
by
end
of
June
this
year,
so
really
cool.
That's
we're!
Finally,
getting
this
one
out
and
then
I
can
I
can
close
to
user
voice
they
soon.