How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Cisco Identity Services Engine Restidstore API

The restidstore API from Cisco Identity Services Engine — 7 operation(s) for restidstore.

Cisco Identity Services Engine Restidstore API is one of 197 APIs that Cisco Identity Services Engine publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include restidstore. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 21 operations across 7 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://{server}:{port}/ers/config.

21 operations 7 paths 22 schemas 4 DELETE7 GET4 PATCH2 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{server}:{port}/ers/config
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Cisco Identity Services Engine Restidstore API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (HTTPBasicAuthentication).

Paths & Operations 21

Across 7 paths, the API surfaces 21 operations — 4 DELETE, 7 GET, 4 PATCH, 2 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

restidstore 21
GET
/restidstore/
Get-All
5 params → 200400401403404406415
POST
/restidstore/
Create
body → 201400401403404406415500
GET
/restidstore/name/{name}
Get-By-Name
1 param → 200400401403404406415
PUT
/restidstore/name/{name}
Update-By-Name
1 param body → 200400401403404406415500
DELETE
/restidstore/name/{name}
Delete-By-Name
1 param → 204400401403404406415
PATCH
/restidstore/name/{name}
Patch-By-Name
1 param body → 200400401403404406415500
GET
/restidstore/{id}
Get-By-Id
1 param → 200400401403404406415
PUT
/restidstore/{id}
Update
1 param body → 200400401403404406415500
DELETE
/restidstore/{id}
Delete
1 param → 204400401403404406415
PATCH
/restidstore/{id}
Patch
1 param body → 200400401403404406415500
GET
/ers/config/restidstore/name/{name}
Get REST ID store by name
3 params → 200
PATCH
/ers/config/restidstore/name/{name}
Update part of the REST ID Store by name
2 params body → 200
PUT
/ers/config/restidstore/name/{name}
Update REST ID store by name
3 params body → 200
DELETE
/ers/config/restidstore/name/{name}
Delete REST ID store by name
3 params → 204
GET
/ers/config/restidstore/{id}
Get REST ID store by ID
3 params → 200
PATCH
/ers/config/restidstore/{id}
Update part of the REST ID Store by ID
2 params body → 200
PUT
/ers/config/restidstore/{id}
Update REST ID store
4 params body → 200
DELETE
/ers/config/restidstore/{id}
Delete REST ID store
3 params → 204
GET
/ers/config/restidstore
Get all REST ID stores
2 params → 200
POST
/ers/config/restidstore
Create REST ID store
2 params body → 201
GET
/ers/config/restidstore/versioninfo
Get REST ID store version information
→ 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are restidstoreResponseEntity (9 properties), ERSRestIDStore (8 properties), ERSRestIDStore_2 (5 properties), UpdatedFieldsList (4 properties). Each schema is shown below with its type and property counts.

UpdatedField
object
3 properties
UpdatedFieldsResponse
object
1 property
restidstoreResponse
object
1 property
Link
object
3 properties
Update
object
1 property
patchRequest
object
1 property
version
object
3 properties
UpdatedFieldsList
object
4 properties
restidstoreListResponse
object
1 property
updatedField
object
3 properties
restidstoreResponseEntity
object
9 properties
link1
object
3 properties
ERSRestIDStore_2
object
5 properties
restidstoreListResponseEntity
object
4 properties
VersionInfo
object
1 property
rest
object
1 property
patchRequestBody
object
2 properties
ERSResponse
object
2 properties
SearchResult
object
2 properties
ERSRestIDStore
object
8 properties 1 required
identitystores.restidstore
object
1 property 1 required
search
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-ise-restidstore-api-openapi.yml Raw ↑

Other APIs Cisco Identity Services Engine publishes across the network.

Cisco Identity Services Engine Acct Status API
Cisco Identity Services Engine Acct Status TT API
Cisco Identity Services Engine ACI Connection API
Cisco Identity Services Engine ACI Data API
Cisco Identity Services Engine Acibindings API
Cisco Identity Services Engine Acisettings API
Cisco Identity Services Engine Active Directories API
Cisco Identity Services Engine Activedirectory API
Cisco Identity Services Engine AD Groups API
Cisco Identity Services Engine Admin Groups API
Cisco Identity Services Engine Admin Users API
Cisco Identity Services Engine Adminuser API
Where this information came from

This is an independent, third-party profile of Cisco Identity Services Engine Restidstore API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.