Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

APIs.io Engineering Platform #Action=UpdateServiceSpecificCredential API

The #Action=UpdateServiceSpecificCredential API from APIs.io Engineering Platform — 1 operation(s) for #action=updateservicespecificcredential.

This API exposes 2 operations across 1 path, and defines 5 schemas. It is described by OpenAPI 3.0.0, at version 2015-07-09.

Requests are made against 4 base URLs: http://apigateway.{region}.amazonaws.com, https://apigateway.{region}.amazonaws.com, http://apigateway.{region}.amazonaws.com.cn, https://apigateway.{region}.amazonaws.com.cn.

2 operations 1 paths 5 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
2015-07-09
Base URL
https://{bucketname}.s3.amazonaws.com
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

APIs.io Engineering Platform #Action=UpdateServiceSpecificCredential API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (hmac). By default, every request must be authenticated.

  • hmac — Amazon Signature authorization v4

Paths & Operations 2

Across 1 path, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

#Action=UpdateServiceSpecificCredential 2
GET
/#Action=UpdateServiceSpecificCredential
Sets the status of a service-specific credential to Active or Inactive . Service-specific credentials that are inactive cannot be used for authentication to the service. This operation can be used to…
GET_UpdateServiceSpecificCredential 12 params → 200480
POST
/#Action=UpdateServiceSpecificCredential
Sets the status of a service-specific credential to Active or Inactive . Service-specific credentials that are inactive cannot be used for authentication to the service. This operation can be used to…
POST_UpdateServiceSpecificCredential 9 params body → 200480

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed is UpdateServiceSpecificCredentialRequest (3 properties). Each schema is shown below with its type and property counts.

statusType
string
NoSuchEntityException
userNameType
string
UpdateServiceSpecificCredentialRequest
object
3 properties 2 required
serviceSpecificCredentialId
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

engineering-platform-action-updateservicespecificcredential-api-openapi.yml Raw ↑