<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Outdated Documentation on CrefoTrust Docs</title>
    <link>https://docs.crefotrust.de/historic-documents/</link>
    <description>Recent content in Outdated Documentation on CrefoTrust Docs</description>
    <generator>Hugo</generator>
    <language>en-en</language>
    <atom:link href="https://docs.crefotrust.de/historic-documents/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DEPRECATED: V3 CrefoTrust API</title>
      <link>https://docs.crefotrust.de/historic-documents/v3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.crefotrust.de/historic-documents/v3/</guid>
      <description>&lt;h2 id=&#34;1-first-things-first&#34;&gt;1) First things first&lt;/h2&gt;&#xA;&lt;p&gt;To integrate with CrefoTrust you need to get authentication information: a &lt;em&gt;verifier ID&lt;/em&gt; and an &lt;em&gt;API key&lt;/em&gt;. To acquire those, please contact: &lt;a href=&#34;mailto:support@crefotrust.de&#34;&gt;support@crefotrust.de&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;2-placing-orders&#34;&gt;2) Placing Orders&lt;/h2&gt;&#xA;&lt;p&gt;The process starts with placing an order with the CrefoTrust order service. To do this you call the API endpoint: &lt;em&gt;/orders&lt;/em&gt; with the &lt;em&gt;POST&lt;/em&gt; method.&lt;/p&gt;&#xA;&lt;p&gt;We have different environments with different URLs. For development and integration purposes use:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;https://api-demo.crefotrust.de/api/orders&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;For production use:&lt;/p&gt;</description>
    </item>
    <item>
      <title>V2 to V3 API Changes</title>
      <link>https://docs.crefotrust.de/historic-documents/v2tov3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.crefotrust.de/historic-documents/v2tov3/</guid>
      <description>&lt;h2 id=&#34;benefits-of-the-new-version--changes&#34;&gt;Benefits of the new version / Changes&lt;/h2&gt;&#xA;&lt;h3 id=&#34;new-accepted-id-methods-nect&#34;&gt;New Accepted ID Methods: Nect&lt;/h3&gt;&#xA;&lt;p&gt;Nect is a state-of-the-art AI-based technology, with which your end-users can identify themselves in minutes. Used by insurance companies, banks and the German government, the solution is very well received by customers thanks to its user-friendliness and cost-efficiency. Contact us for additional information: &lt;a href=&#34;mailto:kontakt@crefotrust.de&#34;&gt;kontakt@crefotrust.de&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;verifier-id&#34;&gt;Verifier ID&lt;/h3&gt;&#xA;&lt;p&gt;When interacting with the CrefoTrust API the &lt;em&gt;verifierId&lt;/em&gt; can be provided as an HTTP header (key: &lt;em&gt;x-verifier-id&lt;/em&gt;) instead as part of the request body.&lt;/p&gt;</description>
    </item>
    <item>
      <title>DEPRECATED: V2 CrefoTrust API</title>
      <link>https://docs.crefotrust.de/historic-documents/v2/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.crefotrust.de/historic-documents/v2/</guid>
      <description>&lt;h2 id=&#34;1-first-things-first&#34;&gt;1) First things first&lt;/h2&gt;&#xA;&lt;p&gt;To integrate with CrefoTrust you need to get login information: a &lt;em&gt;verifier ID&lt;/em&gt; as well as an &lt;em&gt;API key&lt;/em&gt;. To get those, please contact: &lt;a href=&#34;mailto:support@crefotrust.de&#34;&gt;support@crefotrust.de&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;2-placing-orders&#34;&gt;2) Placing Orders&lt;/h2&gt;&#xA;&lt;p&gt;The process starts with placing an order with the CrefoTrust order service. To do this you call the API endpoint: &lt;em&gt;/orders&lt;/em&gt; with the &lt;em&gt;POST&lt;/em&gt; method.&lt;/p&gt;&#xA;&lt;p&gt;We have different environments with different URLs. For development and integration purposes use:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;https://api-demo.crefotrust.de/api/orders&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;For production use:&lt;/p&gt;</description>
    </item>
    <item>
      <title>DEPRECATED: V1 CrefoTrust API</title>
      <link>https://docs.crefotrust.de/historic-documents/v1/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.crefotrust.de/historic-documents/v1/</guid>
      <description>&lt;p&gt;CrefoTrust enables the verification of people and companies.&lt;/p&gt;&#xA;&lt;h2 id=&#34;features&#34;&gt;Features&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Request multiple Credentials in one call&lt;/li&gt;&#xA;&lt;li&gt;Automatic verification with W3C Standards&lt;/li&gt;&#xA;&lt;li&gt;Destructuring of Verifiable Presentations and Credentials&lt;/li&gt;&#xA;&lt;li&gt;Fully written in Typescript&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;install&#34;&gt;Install&lt;/h2&gt;&#xA;&lt;h3 id=&#34;npm&#34;&gt;npm&lt;/h3&gt;&#xA;&lt;pre&gt;&lt;code&gt;npm install @crefotrust/sdk&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;h3 id=&#34;yarn&#34;&gt;yarn&lt;/h3&gt;&#xA;&lt;pre&gt;&lt;code&gt;yarn add @crefotrust/sdk&#xA;&lt;/code&gt;&lt;/pre&gt;&#xA;&lt;h2 id=&#34;interaction-between-sdk-and-crefotrust-overview&#34;&gt;Interaction between SDK and CrefoTrust Overview&lt;/h2&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://docs.crefotrust.de/SDK-FLOW.jpg&#34; alt=&#34;Placeholder&#34;&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;frontend-usage&#34;&gt;Frontend Usage&lt;/h2&gt;&#xA;&lt;p&gt;In the frontend the call to CrefoTrust is created and executed.&#xA;Afterwards the response gets verified as an initial feedback for the User.&#xA;The correct usage also requires an additional verification of the response in a trusted environment such as a backend, because the frontend can of course compromise the verification result.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
