Interhyp Info API
provides basic info about service status and version of the submission API specs used
provides basic info about service status and version of the submission API specs used
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/interhyp-info-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
title: Interhyp Submission Info API
version: 6.10.0
contact:
name: Interhyp AG (Team Provider Excellence)
email: support_submission_api@interhyp.de
url: https://www.interhyp.de
license:
name: Interhyp AG
description: This document describes the RESTful API and resources provided by Interhyp AG.
servers:
- url: https://api-dev.ehyphome.de/submission/v2
description: Test-Staging
- url: https://api-acc.ehyphome.de/submission/v2
description: Acceptance-Staging
- url: https://api.interhyp.de/submission/v2
description: Production
security:
- ApiKey: []
BearerAuth: []
tags:
- name: Info
description: provides basic info about service status and version of the submission API specs used
paths:
/info:
get:
summary: Get Submission API service status and info
description: Delivers information about Submission API service status and basic information about the current version
operationId: getServiceInfo
tags:
- Info
responses:
'200':
description: Service Info is returned
content:
application/json:
schema:
$ref: '#/components/schemas/ServiceInfo'
example: ' { "apiSpecificationVersion" : "1.0.0" }'
'401':
description: Error indicates no access to the service.
content:
application/json:
schema:
$ref: '#/components/schemas/OAuthProblem'
example: '{ "error": "invalid token", "error_description": "Access token expired", }'
'500':
description: Unexpected Error
content:
application/json:
schema:
$ref: '#/components/schemas/RFC7807Problem'
example: '{ "timestamp": "2023-03-14T10:00:00.995Z", "title": "Internal Server Error", "status": 500, "traceId": "64077933c36912de13fb3cd7ae0c00c8", "instance": "/v2/info" }'
components:
schemas:
OAuthProblem:
type: object
description: Error while Authentication
required:
- error
- error_description
properties:
error:
type: string
description: Summary of the error type
example: invalid_token
error_description:
type: string
description: Detailed information about the error
example: Access token expired
Violation:
description: 'DE: Ein Verstoss gegen die Schnittstellenspezifikation. EN: A violation against the API schema.
'
type: object
title: Violation
properties:
field:
type: string
description: 'DE: Bezeichner des problematischen Felds. EN: Name of the problematic field.
'
example: address.city.numberOfInhabitants
message:
type: string
description: 'DE: Beschreibung des Verstosses. EN: Description of the violation.
'
example: Must be greater than or equal to 0.
RFC7807Problem:
type: object
title: RFC7807Problem
description: 'DE: Angaben zum zurueckgegebenen Fehler. EN: Holds information on the returned error.
'
required:
- timestamp
- traceId
- instance
- title
- status
properties:
timestamp:
type: string
format: date-time
description: 'DE: Ein UTC-Zeitstempel, der den Fehlerzeitpunkt angibt (https://de.wikipedia.org/wiki/Koordinierte_Weltzeit). EN: A UTC date-time indicating the error timestamp (https://en.wikipedia.org/wiki/Coordinated_Universal_Time).
'
example: 2024-06-29 19:22:50+00:00
type:
type: string
format: uri
description: 'DE: Verknuepfung zum Abruf von mehr Informationen zu dem Fehler. EN: URL referring to more information about the error.
'
default: about:blank
title:
type: string
description: 'DE: Kurzbeschreibung des Fehlers. EN: Error short description.
'
example: Bad Request
status:
type: integer
format: int32
description: 'DE: HTTP-Status-Code gemaess Konvention (https://tools.ietf.org/html/rfc2616#section-10). EN: HTTP status code following standared error codes (https://tools.ietf.org/html/rfc2616#section-10).
'
example: 400
minimum: 100
maximum: 599
detail:
type: string
description: 'DE: Detaillierte Beschreibung des Fehlers. EN: Detailed description for the returned error.
'
example: JSON parse error
traceId:
type: string
description: 'DE: Eindeutige Kennung zur Verfolgung der Anfrage. EN: Unique trace id for problematic request.
'
example: avx1234asd
instance:
type: string
format: uri
description: 'DE: Pfad zur betreffenden Resource. EN: Path of requested resource.
'
example: http://localhost/resources/123
violations:
type: array
description: 'DE: Abfolge der Verstoesse in der Anfrage. EN: Collection of the invalid content of the request.
'
items:
$ref: '#/components/schemas/Violation'
ServiceInfo:
type: object
description: 'DE: Informationen zum Dienst Submission API <br/> EN: Information about Submission API service
'
properties:
apiSpecificationVersion:
type: string
description: Currently used version of the Submission API specification
securitySchemes:
BearerAuth:
$ref: '#/components/securitySchemes/StandardBearerAuth'
ApiKey:
$ref: '#/components/securitySchemes/StandardApiKey'
StandardApiKey:
type: apiKey
in: header
name: Api-Key
description: API keys are unique codes issued by an API provider that allow partners to access specific API resources. By requiring an API key, the provider can ensure that only authorized clients are accessing the API and can prevent potential abuse or unauthorized access.
StandardBearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: JWT stands for JSON Web Token and is a type of bearer token that is commonly used for authentication and authorization purposes. Once retrieved, the token is sent with each request and grants access to the associated resource until it expires or is revoked. Thus, it is a compact, URL-safe means of representing a user's claims to access a resource without providing additional credentials.
x-guideline-version: v1