Amazon Web Services Signing Platforms API

The Signing Platforms API from Amazon Web Services — 2 operation(s) for signing platforms.

GitHub OpenAPI

Operations 2

GET /signing-platforms/{platformId} Amazon Web Services Getsigningplatform #
GET /signing-platforms Amazon Web Services Listsigningplatforms #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/amazon-web-services:amazon-web-services-signing-platforms-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

amazon-web-services-signing-platforms-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Amazon Web Services signer Signing Platforms API
  description: "AWS Signer is a fully managed code-signing service to help you ensure the trust and integrity of your code.\n\nSigner supports the following applications:\n\nWith code signing for AWS Lambda, you can sign AWS Lambda deployment packages. Integrated support is provided for Amazon S3, Amazon CloudWatch, and AWS CloudTrail. In order to sign code, you create a signing profile and then use Signer to sign Lambda zip files in S3.\n\nWith code signing for IoT, you can sign code for any IoT device that is supported by AWS. IoT code signing is available for Amazon FreeRTOS and AWS IoT Device Management, and is integrated with AWS Certificate Manager (ACM). In order to sign code, you import a third-party code-signing certificate using ACM, and use that to sign updates in Amazon FreeRTOS and AWS IoT Device Management.\n\nWith Signer and the Notation CLI from the Notary\L Project, you can sign container images stored in a container registry such as Amazon Elastic Container Registry (ECR). The signatures are stored in the registry alongside the images, where they are available for verifying image authenticity and integrity.\n\nFor more information about Signer, see the AWS Signer Developer Guide."
tags:
- name: Signing Platforms
paths:
  /signing-platforms/{platformId}:
    GET:
      summary: Amazon Web Services Getsigningplatform
      description: Returns information on a specific signing platform.
      operationId: amazonWebServicesGetSigningPlatform
      tags:
      - Signing Platforms
  /signing-platforms:
    GET:
      summary: Amazon Web Services Listsigningplatforms
      description: Lists all signing platforms available in AWS Signer that match the request parameters. If additional jobs remain to be listed, Signer returns a nextToken value. Use this value in subsequent calls to ListSigningJobs to fetch the remaining values. You can continue calling ListSigningJobs with your maxResults parameter and with new values that Signer returns in the nextToken parameter until all of your signing jobs have been returned.
      operationId: amazonWebServicesListSigningPlatforms
      tags:
      - Signing Platforms