<turbo-stream action="update" target="wiki_3611_subpage_3633_info"><template>
<p>In order to get access to the API, the Account Administrator needs to create a new API User, that only has access to MyRapidi through the API. Please follow the steps under <a href="/wiki/create_user">Create User </a>and <a href="/wiki/manage_users">Manage Users </a> to create this new API User. After a new API User has been created, the Administrator needs to generate an API Access Token for this API user, which the API uses as the authentication/login method.&nbsp;</p>

<p>The API Access Token generated on the Manage Users page is then used with the "Authorization" Header like below:</p>
<pre class="card">Authorization: Bearer [API SECURITY TOKEN]</pre>
<p>The API Access Token generated will expire in the same way as normal user passwords - depending on the Account - Password Policies. The expire date will be indicated when you generate the Token. When a new Token is generated, the old token will expire after 24 hours - i.e. you have 24 hours to get the new Token into your production system.</p>

<p>This API is authenticated using&nbsp;<a href="http://en.wikipedia.org/wiki/Basic_access_authentication">HTTP Basic Auth</a>&nbsp;over&nbsp;<a href="http://en.wikipedia.org/wiki/HTTP_Secure">HTTPS</a>. Any requests over plain HTTP will fail with an HTTP 307 Temporary Redirect error message.</p>

<p>All requests are associated with a specific API user in MyRapidi and permissions are limited to that user's capabilities.&nbsp;</p>
</template></turbo-stream>
<turbo-stream action="prepend" target="flash"><template></template></turbo-stream>
