Page Comparison

...

To access the specific document, consumers must initiate an HTTP POST request to the /api/docipn/getdocuments/{:tokendocumentId} endpoint. The token documentId parameter represents the security token acquired during the Authentication process on the APIan unique identifier of the document in question. As essential components of the JSON payload within the body of the request, consumers are required to include the hash (serving as the document identifier) and bToken (functioning as the broker identifier).

Attributes of the HTTP request

Attributes of the HTTP response

...

This section shows examples of different HTTP requests and responses associated with the endpoint /api/docipn/getdocuments/{:tokendocuementId}.

# HTTP POST
# https://ipn.dev.thinksurance.de/api/docipn/get/{:token}documents/<some ID>
#
# HTTP headers
# 'Content-Type': 'application/json'
# 'Accept': 'application/json'
# 'Authorization': 'Bearer {<some long  "hash": "some encrypted string",string value>'
# 
{doc
  "bToken": "some encrypted string"
}

# HTTP 200 status code
# 'Content-Type': 'text/pdf'
Base64 encoded payload

# HTTP 200 status code
# 'Content-Type': 'application/json'
{
  "error": "API User is not existing or deactivated."
}

...