Evrotrust · OpenAPI Overlay 1.0.0

Evrotrust API enhancements

49 actions 49 updates update extends openapi/evrotrust-api-openapi.yml
Authorship not recorded No authorship marker is recorded for this file. It is not presented as the provider's.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-notex-variant-ofx-callbackx-directionx-api-evangelist

Targets 49 · first 16 shown; the file carries all of them

$.info
$.paths['/document/ready'].post
$.paths['/document/group/ready'].post
$.paths['/document/offline/ready'].post
$.paths['/document/group/offline/ready'].post
$.paths['/certificate/hash/offline/ready'].post
$.paths['/document/doc/offline/activate-1'].post
$.paths['/document/doc/offline/activate/resend-1'].post
$.paths['/document/download-1'].post
$.paths['/document/download-2'].post
$.paths['/document/download-3'].post
$.paths['/document/group/download-1'].post
$.paths['/document/group/download-2'].post
$.paths['/document/group/download-3'].post
$.paths['/document/group/download-3-1'].post
$.paths['/document/group/offline/activate-1'].post

OpenAPI Overlay

Raw ↑ 
overlay: 1.0.0
info:
  title: Evrotrust API enhancements
  version: 1.0.0
extends: openapi/evrotrust-api-openapi.yml
actions:
- target: $.info
  update:
    x-api-evangelist:
      provider: evrotrust
      docs: https://docs.evrotrust.com/reference/overview
      llms_txt: https://docs.evrotrust.com/llms.txt
      sandbox_server: https://api.sandbox.evrotrust.com/vendor
- target: $.paths['/document/ready'].post
  update:
    x-callback: true
    x-direction: evrotrust-to-vendor
    x-note: Per its own description this is a status callback Evrotrust sends to the vendor's callback URL, not an endpoint the vendor calls.
- target: $.paths['/document/group/ready'].post
  update:
    x-callback: true
    x-direction: evrotrust-to-vendor
    x-note: Per its own description this is a status callback Evrotrust sends to the vendor's callback URL, not an endpoint the vendor calls.
- target: $.paths['/document/offline/ready'].post
  update:
    x-callback: true
    x-direction: evrotrust-to-vendor
    x-note: Per its own description this is a status callback Evrotrust sends to the vendor's callback URL, not an endpoint the vendor calls.
- target: $.paths['/document/group/offline/ready'].post
  update:
    x-callback: true
    x-direction: evrotrust-to-vendor
    x-note: Per its own description this is a status callback Evrotrust sends to the vendor's callback URL, not an endpoint the vendor calls.
- target: $.paths['/certificate/hash/offline/ready'].post
  update:
    x-callback: true
    x-direction: evrotrust-to-vendor
    x-note: Per its own description this is a status callback Evrotrust sends to the vendor's callback URL, not an endpoint the vendor calls.
- target: $.paths['/document/doc/offline/activate-1'].post
  update:
    x-variant-of: /document/doc/offline/activate
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/doc/offline/activate/resend-1'].post
  update:
    x-variant-of: /document/doc/offline/activate/resend
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/download-1'].post
  update:
    x-variant-of: /document/download
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/download-2'].post
  update:
    x-variant-of: /document/download
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/download-3'].post
  update:
    x-variant-of: /document/download
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/group/download-1'].post
  update:
    x-variant-of: /document/group/download
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/group/download-2'].post
  update:
    x-variant-of: /document/group/download
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/group/download-3'].post
  update:
    x-variant-of: /document/group/download
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/group/download-3-1'].post
  update:
    x-variant-of: /document/group/download
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/group/offline/activate-1'].post
  update:
    x-variant-of: /document/group/offline/activate
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/group/offline/activate/resend-1'].post
  update:
    x-variant-of: /document/group/offline/activate/resend
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/group/status-1'].post
  update:
    x-variant-of: /document/group/status
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/group/status-2'].post
  update:
    x-variant-of: /document/group/status
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/group/status-3'].post
  update:
    x-variant-of: /document/group/status
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/group/status-4'].post
  update:
    x-variant-of: /document/group/status
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/group/status-5'].post
  update:
    x-variant-of: /document/group/status
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/offline/withdraw-1'].post
  update:
    x-variant-of: /document/offline/withdraw
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/offline/withdraw-1-1'].post
  update:
    x-variant-of: /document/offline/withdraw
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/offline/withdraw-1-1-1'].post
  update:
    x-variant-of: /document/offline/withdraw
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/offline/withdraw-1-1-1-1'].post
  update:
    x-variant-of: /document/offline/withdraw
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/offline/withdraw-1-1-1-1-1'].post
  update:
    x-variant-of: /document/offline/withdraw
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/status-1'].post
  update:
    x-variant-of: /document/status
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/status-2'].post
  update:
    x-variant-of: /document/status
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/status-3'].post
  update:
    x-variant-of: /document/status
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/status-4'].post
  update:
    x-variant-of: /document/status
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/document/status-5'].post
  update:
    x-variant-of: /document/status
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/certificate/check-1'].post
  update:
    x-variant-of: /hash/certificate/check
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/certificate/get-1'].post
  update:
    x-variant-of: /hash/certificate/get
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/group/certificate/check-1'].post
  update:
    x-variant-of: /hash/group/certificate/check
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/group/certificate/get-1'].post
  update:
    x-variant-of: /hash/group/certificate/get
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/group/offline/activate-1'].post
  update:
    x-variant-of: /hash/group/offline/activate
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/group/offline/activate/resend-1'].post
  update:
    x-variant-of: /hash/group/offline/activate/resend
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/group/offline/check-1'].post
  update:
    x-variant-of: /hash/group/offline/check
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/group/offline/download-1'].post
  update:
    x-variant-of: /hash/group/offline/download
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/group/offline/download-2'].post
  update:
    x-variant-of: /hash/group/offline/download
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/group/offline/download-2-1'].post
  update:
    x-variant-of: /hash/group/offline/download
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/group/offline/send-1'].post
  update:
    x-variant-of: /hash/group/offline/send
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/offline/activate-1'].post
  update:
    x-variant-of: /hash/offline/activate
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/offline/activate/resend-1'].post
  update:
    x-variant-of: /hash/offline/activate/resend
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/offline/check-1'].post
  update:
    x-variant-of: /hash/offline/check
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/offline/download-1'].post
  update:
    x-variant-of: /hash/offline/download
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/offline/download-1-1'].post
  update:
    x-variant-of: /hash/offline/download
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.
- target: $.paths['/hash/offline/send-1'].post
  update:
    x-variant-of: /hash/offline/send
    x-note: Path suffix comes from the ReadMe reference page slug (one page per documented variant); the real request path is the base path.

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • 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 overlay 
curl "https://apis.io/api/v1/overlays/evrotrust-api-overlay"
All openapi overlays 
curl "https://apis.io/api/v1/overlays?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.

GitHub Google LinkedIn

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