PrismaLife services - Metadata

<back to all web services

ConfigFile

Übertragung von Konfigurationsdateien

The following routes are available for this service:
POST/api/ConfigFileConfigFile-ServiceÜbertragung von Konfigurationsdateien
Parameters:
NameParameterData TypeRequiredDescription
LoginbodyCredentialYesLogin (Benutzername und Passwort)
FileNamebodystringYesFileName
FileContentbodystringYesFileContent in Base64
BIBOnlypathBooleanYesCreate BIB Document only
OmitDocumentpathBooleanNoOmit document, true = gets result without PDF attached.
DocFieldListbodyListNoList of DocFieldValue (key, value). FileName and Filecontent is not needed if this is filled. This must be NULL if FileContent should be used. List
IsTestClientpathBooleanNoPrismaLife Internal only. Flag for TestClient
CreateValidDocumentInTestClientpathBooleanNoPrismaLife Internal only. Flag to create valid Documents in TestClient

To override the Content-type in your clients HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /json/reply/ConfigFile HTTP/1.1 
Host: services.prismalife.com 
Content-Type: application/json
Content-Length: length

{"login":{"username":"String","password":"String"},"fileName":"String","fileContent":"String","options":{"rules":[{"key":"String","value":"String"}]},"bibOnly":false,"omitDocument":false,"docFieldList":[{"key":"String","value":"String"}],"isTestClient":false,"createValidDocumentInTestClient":false}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"report":{"pdf":"AA==","fileKey":"String","allPages":0},"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String"}]},"warnings":["String"],"id":"String","premTotal":0,"performance":0,"payOutEnd":0,"productName":"String"}