InfoCert Rfc3161 API

apply a timestamp using protocol https://tools.ietf.org/html/rfc3161

Operations 1

POST /timestamp/v1/apply Apply timestamp to the current .tsq #

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/infocert:infocert-rfc3161-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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

infocert-rfc3161-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Infocert Rfc3161 API
  version: '1.0'
  description: 'Operations tagged rfc3161 across 2 of this provider''s published API definitions: infocert-timestamp-openapi.yml, infocert-timestamp-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://apitest.infocert.digital/
  description: Test server
- url: https://apistage.infocert.digital/
  description: Staging/UAT server
- url: https://api.infocert.digital/
  description: Production server
basePath: /identification/afm/v1
security:
- oauth2: []
tags:
- name: rfc3161
  description: apply a timestamp using protocol https://tools.ietf.org/html/rfc3161
paths:
  /timestamp/v1/apply:
    post:
      tags:
      - rfc3161
      summary: Apply timestamp to the current .tsq
      description: to create a .tsq 'openssl ts -query -data -no_nonce -sha512 -cert -out .tsq'
      requestBody:
        content:
          application/timestamp-query:
            schema:
              type: string
              format: binary
      responses:
        '200':
          description: a .tsr file to verify the file 'openssl ts -verify -in <response>.tsr -queryfile <request>.tsq'
          content:
            application/timestamp-reply:
              schema:
                type: string
                format: binary
      operationId: postTimestampV1Apply
      x-operation-id-source: derived
    servers:
    - url: https://apitest.infocert.digital/
      description: Test server
    - url: https://apistage.infocert.digital/
      description: Staging/UAT server
    - url: https://api.infocert.digital/
      description: Production server
components:
  securitySchemes:
    oauth2:
      type: oauth2
      flows:
        clientCredentials:
          tokenUrl: https://idpstage.infocert.digital/auth/realms/delivery/protocol/openid-connect/token
          scopes:
            timestamp: timestamp scope
            signature: signature scope to perform both signature and timestamp
x-refined-from:
- infocert-timestamp-openapi.yml
- infocert-timestamp-openapi.yml